This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
RE: rfc: new libgcc build mechanism
- To: "'pausmith at nortelnetworks dot com'" <pausmith at nortelnetworks dot com>
- Subject: RE: rfc: new libgcc build mechanism
- From: Donn Terry <donnte at microsoft dot com>
- Date: Wed, 10 May 2000 12:57:13 -0700
- Cc: 'Felix Lee' <flee at teleport dot com>, 'Robert Lipe' <robertlipe at usa dot net>, 'Russ Allbery ' <rra at stanford dot edu>, "'autoconf at gnu dot org '" <autoconf at gnu dot org>, "'gcc at gcc dot gnu dot org '" <gcc at gcc dot gnu dot org>
Oops... pressed the wrong reply button (I miss mh!).
The idea of $(BACKQUOTE) would allow it to also be null,
so substitution marks would only be present when needed.
(That wasn't clear... sorry.) (It would also help with
the plethora of \\\\\\\\\\ sequences in configure.)
That does have nested `` in it (without eval), but it
broke with Jason's addition of the new pipeline step.
Yeah... a script would work, but introduce the maintenance
hassle of maintaining it (or synthesizing it in the Makefile
or configure). Maintenace in this area is already very hard.
Donn
P.S. 2d reply (on Solaris) coming.
%% Donn Terry <donnte@microsoft.com> writes:
This only went to me?
dt> That's close, except that @cc_set_by_configure@ or
dt> @quoted_cc_set_by_configure@ already contains the `` pair, but
dt> *only sometimes*. Sometimes it's simply (in effect) a literal,
dt> and sometimes it needs substitution. Given that @...@ are used
dt> elsewhere in the script, and that it's only sometimes needed,
dt> using a single enclosing `` pair in the Makefile doesn't work.
Ugh.
dt> (It also occurs to me that we could do something truly awful such as
dt> BACKQUOTE=`
dt> $(BACKQUOTE)<stuff>$(BACKQUOTE)
dt> when a substitution was needed. I haven't tried this... it's too
dt> close after lunch :-) . Anyone else care to comment?)
I don't see how this would do anything? You're just hiding the ` from
make, but make doesn't expand ` anyway. It would just substitute in the
` and invoke the shell with nested ``.
Anyway, you always have the option of writing a small shell script and
encapsulating the case, etc. statements in there and invoking that,
instead of doing it inline.
And, I believe you _can_ get nested `` but you need to use eval and it's
a huge PITA to get the quoting right.
--
----------------------------------------------------------------------------
---
Paul D. Smith <psmith@baynetworks.com> Network Management
Development
"Please remain calm...I may be mad, but I am a professional." --Mad
Scientist
----------------------------------------------------------------------------
---
These are my opinions---Nortel Networks takes no responsibility for them.