I'm using that as an unambiguous representation of the current text
which is full of `` and unbalanced ) so that it's very difficult to
get right. That's what I said (not quite so explicitly) in my
prior message. (Start, as I said in prior mail, with
@quoted_cc_set_by_configure@ in the non-symlink case... this
is a lot easier to understand at least.)
What's currently in the distribution does not work on ANY system
(where configure determines there are no symbolic links) because
the `` get balanced improperly. Let's either:
1) Find the equivalent sequence using `` that does work everywhere
(which I'm not sure is possible, but I'd be happy to be wrong).
2) Admit it's not possible (or far too impractical), and look
at the alternative of finding a shell that supports $() or
some other alternative.
Donn
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, May 10, 2000 10:07 AM
> To: Donn Terry
> Cc: 'Felix Lee'; 'Robert Lipe'; 'Russ Allbery '; '[EMAIL PROTECTED] ';
> '[EMAIL PROTECTED] '
> Subject: Re: rfc: new libgcc build mechanism
>
>
> %% Donn Terry <[EMAIL PROTECTED]> 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. /bin/sh on Solaris (2.5.1 and 2.6 at least)
> can't handle either of these constructs (either $() or () in
> case match
> items), for example. Since make always uses /bin/sh, installing this
> construct will make gcc unbuildable on Solaris (at least).
>
> --
> --------------------------------------------------------------
> -----------------
> Paul D. Smith <[EMAIL PROTECTED]> 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.
>
