Message-ID: <20030512052934.47066.qmail@web41008.mail.yahoo.com>
Date: Sun, 11 May 2003 22:29:34 -0700 (PDT)
From: Daniel Borca <dborca AT yahoo DOT com>
Subject: Re: DXE3 in DJGPP CVS breaks cross-compiling
To: Charles Sandmann <sandmann AT clio DOT rice DOT edu>, eliz AT elta DOT co DOT il
Cc: djgpp-workers AT delorie DOT com, dborca AT yahoo DOT com
In-Reply-To: <10305120346.AA12303@clio.rice.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

Hello!

--- Charles Sandmann <sandmann AT clio DOT rice DOT edu> wrote:

> The original dxegen code used system, didn't quote,
> and was compatible
> with non-DJGPP platforms.
> 
> The new dxe3gen code uses spawn, which is NOT
> compatible for cross
> compiles.

Right! Could "myspawn" be instructed to automagically
quote slicky args?

> I'm willing to either make it cross compile
> compatible with a quick
> conversion to system, or leave it as it is with
> spawn and then we 
> just don't support cross builds.  

I'd go for portability. So cross builds are an option.

> > An alternative would be to rewrite the portability
> layer for spawn*
> > that uses exec*, not `system'.  exec* and spawn*
> share the wayt hey
> > treat their arguments: they both don't require
> quoting.
> 
> Feel free to do so, but it's not in the library
> right now, and I don't 
> have time to do it and test it.

Uhmmm... If you were meaning cross-building the DXE
modules, be aware that "exec" is somehow tricky on
Linux platforms. It never returns to the caller. That
could be worked around using "fork", but then again,
it will stop working under DOS (DJGPP has "fork" --
but it fails, as we all know).


=====
Regards,
Borca Daniel

http://www.geocities.com/dborca/

__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com