Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <3E2CA496.8050201@ece.gatech.edu>
Date: Mon, 20 Jan 2003 20:38:30 -0500
From: Charles Wilson <cwilson@ece.gatech.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0
MIME-Version: 1.0
To: bkorb@veritas.com
CC: automake-patches@gnu.org, libtool-patches@gnu.org,
   mingw-users@lists.sourceforge.net, cygwin@cygwin.com
Subject: Re: [Mingw-users] Re: Solving the "relink exe's" libtool problem[take3]
References: <3E19C657.1040904@ece.gatech.edu>		<2003-01-09-17-11-09+16471+duret_g@lrde.epita.fr>		<3E1DE146.8030901@ece.gatech.edu>		<2003-01-09-23-01-51+2104+duret_g@lrde.epita.fr>		<3E20BF9A.4080400@ece.gatech.edu>		<2003-01-13-00-19-29+30521+duret_g@lrde.epita.fr>		<3E224479.8030604@ece.gatech.edu> <3E227106.5000706@ece.gatech.edu> <3E2C4478.3040507@yahoo.com> <3E2C4E93.144C5B40@gnu.org> <3E2C7C08.5030005@ece.gatech.edu> <3E2C802D.645726C9@veritas.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit


>>easy enough.  But what's the best way to use "the shell"?  Do a unquoted
>>replacement (<<EOF, not <<"EOF") e.g.
> 
> Yes.
> 
> Somewhere, buried in the configury stuff is an environment
> variable named something like, "CONFIG_SHELL".  That's what
> you want.  If it is not available, then imitating the techniques
> used to obtain it by configure should be used.

But lt-foo.c is created by the libtool script itself -- and libtool 
already knows that $SHELL == /bin/sh or /bin/bash or whatever.  libtool 
uses the same method I described when creating the shell wrapper:

         $echo > $output "\
#! $SHELL
# $output - temporary wrapper script for $objdir/$outputname
...

So I really don't need to worry about $CONFIG_SHELL or imitating 
configure, do I?  I can just use $SHELL.

--Chuck


--
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/