This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [libstdc++] Add --disable-hosted-libstdcxx, clean up conditionals
On Thu, Aug 28, 2003 at 10:24:17PM +0200, Gabriel Dos Reis wrote:
> Phil Edwards <phil@jaj.com> writes:
> |
> | That's not a bad idea, but it still won't work. The variable names are
> | generated by autoconf, not by us. Specifically, the problem cases of
> |
> | if test ${foo_libstdc+++set} = set; then
> |
> | are all done by autoconf.
>
> ah, now it is not bourne shell limitation, but autoconf limitations :-/
It is both. We can't name them ++ because of the shell. We can't transform
them from ++ because of autoconf.
Phil
--
Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it.
- Brian W. Kernighan
- References:
- [libstdc++] Add --disable-hosted-libstdcxx, clean up conditionals
- Re: [libstdc++] Add --disable-hosted-libstdcxx, clean up conditionals
- Re: [libstdc++] Add --disable-hosted-libstdcxx, clean up conditionals
- Re: [libstdc++] Add --disable-hosted-libstdcxx, clean up conditionals
- Re: [libstdc++] Add --disable-hosted-libstdcxx, clean upconditionals
- Re: [libstdc++] Add --disable-hosted-libstdcxx, clean up conditionals
- Re: [libstdc++] Add --disable-hosted-libstdcxx, clean up conditionals
- Re: [libstdc++] Add --disable-hosted-libstdcxx, clean up conditionals
- Re: [libstdc++] Add --disable-hosted-libstdcxx, clean up conditionals
- Re: [libstdc++] Add --disable-hosted-libstdcxx, clean up conditionals