delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2003/01/20/20:40:45

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
Message-ID: <3E2CA496.8050201@ece.gatech.edu>
Date: Mon, 20 Jan 2003 20:38:30 -0500
From: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: bkorb AT veritas DOT com
CC: automake-patches AT gnu DOT org, libtool-patches AT gnu DOT org,
mingw-users AT lists DOT sourceforge DOT net, cygwin AT cygwin DOT com
Subject: Re: [Mingw-users] Re: Solving the "relink exe's" libtool problem[take3]
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> <2003-01-09-23-01-51+2104+duret_g AT lrde DOT epita DOT fr> <3E20BF9A DOT 4080400 AT ece DOT gatech DOT edu> <2003-01-13-00-19-29+30521+duret_g AT lrde DOT epita DOT fr> <3E224479 DOT 8030604 AT ece DOT gatech DOT edu> <3E227106 DOT 5000706 AT ece DOT gatech DOT edu> <3E2C4478 DOT 3040507 AT yahoo DOT com> <3E2C4E93 DOT 144C5B40 AT gnu DOT org> <3E2C7C08 DOT 5030005 AT ece DOT gatech DOT edu> <3E2C802D DOT 645726C9 AT veritas DOT com>

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

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019