Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
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
Subject: Re: Solving the "relink exe's" libtool problem
From: Alexandre Duret-Lutz <duret_g AT lrde DOT epita DOT fr>
X-Home-Page: http://gadl.free.fr/
X-GPG-Keyserver: http://pgp.mit.edu/
X-GPG-Fingerprint: FCA0 8615 0211 941A 2AB9  FA66 3859 C03B 2E23 6E47
Date: Thu, 09 Jan 2003 23:01:50 +0100
In-Reply-To: <3E1DE146.8030901@ece.gatech.edu> (Charles Wilson's message of
 "Thu, 09 Jan 2003 15:53:26 -0500")
User-Agent: Gnus/5.090008 (Oort Gnus v0.08) Emacs/21.2 (i386-pc-linux-gnu)
References: <3E19C657 DOT 1040904 AT ece DOT gatech DOT edu>
	<2003-01-09-17-11-09+16471+duret_g AT lrde DOT epita DOT fr>
	<3E1DE146 DOT 8030901 AT ece DOT gatech DOT edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Message-ID: <2003-01-09-23-01-51+2104+duret_g@lrde.epita.fr>
X-Attribution: adl

>>> "Chuck" == Charles Wilson <cwilson AT ece DOT gatech DOT 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


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/