This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: rfc: new libgcc build mechanism
- To: Phil Edwards <pedwards at jaj dot com>
- Subject: Re: rfc: new libgcc build mechanism
- From: pausmith at nortelnetworks dot com (Paul D. Smith)
- Date: 10 May 2000 15:27:55 -0400
- Cc: "Smith, Paul " <pausmith at BayNetworks dot COM>, autoconf at gnu dot org, gcc at gcc dot gnu dot org
- References: <200005101826.OAA05377@jaj.com>
- Reply-To: pausmith at nortelnetworks dot com
%% Phil Edwards <pedwards@jaj.com> writes:
>> I haven't looked closely at this, but I will note right off that this:
dt> "CC=$$(echo $$(case '$(CC)' in (stage*) echo '$(CC)' | sed -e
>> is very non-portable.
pe> I have looked at this even less closely than you; perhaps I have
pe> missed something. If you are constructing the makefile via
pe> autoconf, why not detect a shell that will do such expansions and
pe> set SHELL in the output makefile accordingly?
If you can find one, that's fine. First you are assuming that every
platform you want to build GCC on _will_ have such a shell. Since ksh
isn't free, and certainly not every UNIX includes bash, some versions of
UNIX might not have one anywhere (is this the same thread
pe> Also, just FYI, the default make on Solaris (from the development
pe> tools package, sitting in /usr/ccs/bin) is the same make as the
pe> POSIX-complaint make, so it would pay attention to the SHELL
pe> setting:
Sure, that's not the problem. I've never heard of _ANY_ make that
didn't obey the SHELL variable.