This is the mail archive of the cygwin@cygwin.com mailing list for the Cygwin project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Solving the "relink exe's" libtool problem

From: Alexandre Duret-Lutz <duret_g at lrde dot epita dot fr>
To: Charles Wilson <cwilson at ece dot gatech dot edu>
Cc: automake-patches at gnu dot org, libtool-patches at gnu dot org,cygwin at cygwin dot com, mingw-users at lists dot sourceforge dot net
Date: Thu, 09 Jan 2003 23:01:50 +0100
Subject: Re: Solving the "relink exe's" libtool problem
References: <3E19C657.1040904@ece.gatech.edu><2003-01-09-17-11-09+16471+duret_g@lrde.epita.fr><3E1DE146.8030901@ece.gatech.edu>

>>> "Chuck" == Charles Wilson <cwilson@ece.gatech.edu> writes:

[...]

 Chuck> 'Course, there's the whole cross-compiler issue (running
 Chuck> on linux, building stuff intended for cygwin).

Yes.  Sigh.

[...]

 Chuck> Said "stub" executable would have to do ALL of the
 Chuck> things the script does, and then pass that environment
 Chuck> to its exec'ed target in .libs/ --

Maybe it could just exec() something like `/bin/sh .libs/foo.sh',
where `.libs/foo.sh' is the script wrapper.

[...]

-- 
Alexandre Duret-Lutz

Follow-Ups:
- Re: Solving the "relink exe's" libtool problem [take 2]
  - From: Charles Wilson

References:
- Solving the "relink exe's" libtool problem
  - From: Charles Wilson
- Re: Solving the "relink exe's" libtool problem
  - From: Alexandre Duret-Lutz
- Re: Solving the "relink exe's" libtool problem
  - From: Charles Wilson

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]