Re: gcc-3.0 and libstdc++: More interesting configure problems

[Andreas Schwab <schwab at suse dot de>]

Daniel Jacobowitz <dmj+@andrew.cmu.edu> writes:

|> Using the version of configure shipped in the gcc 3.0 tarball (I didn't
|> regenerate it with a local autoconf, so that's not the problem...) I
|> first configured with /bin/sh = /bin/bash, and I got lines like this in
|> config.cache:
|> 
|> ac_cv_prog_CXXCPP=${ac_cv_prog_CXXCPP=$'\'mips_fp_le-g++ -E\''}
|> 
|> I only had CC, CXX, and CPP in the environment (which got the same
|> treatment).  Configure fabricated the above out of thin air.
|> Now, I'm not entirely sure where that's coming from, or what it's
|> supposed to mean.  It evaluates roughly right in bash:
|> 
|> bash$ echo $ac_cv_prog_CXXCPP
|> 'mips_fp_le-g++ -E'
|> 
|> (is that really what's supposed to come out of it?)

Yes.

|> But not in other shells.

$'...' is a bash extension.  Remove config.cache when switching shells.

Andreas.

-- 
Andreas Schwab                                  "And now for something
SuSE Labs                                        completely different."
Andreas.Schwab@suse.de
SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5