This is the mail archive of the
mailing list for the GCC project.
Re: value of $CXX when building libraries
Phil Edwards <email@example.com> writes:
| On Wed, Jan 10, 2001 at 08:45:27AM +0100, Gabriel Dos Reis wrote:
| > | (a) Create a temporary shell script or binary to be used solely for
| > | compiling target libraries:
| > | #!/bin/sh
| > | exec /home/bothner/GNU/linux-gcc/gcc/g++ -B... -L.. -I.. "$@"
| > | This could be called "new-g++" by analogy with "new-as" and "new-ld".
| > | I don't know which directory to put it in; either libstdc++-v3 or
| > | some new "target-bin" directory, possible i686-pc-linux-gnu/bin.
| > | In that case we could just call the script "g++" and have to option
| > | of just setting $PATH to include i686-pc-linux-gnu/bin.
| > I'm leaning toward a binary target/bin/ which knows by itself which -I
| > and -L flags ae right.
| So, the targetdir/tooldir would contain a 'bin' dir as well as all the
| target library dirs?
Yes, mainly for tools like Java which need special handling.
| ... We could do that... could probably start with the
| value of ac_cv_prog_CXX_libstdcxx in the targetdir/tooldir's config.cache,
| and then add all the -I's.
Well, now I'm wondering: which value should be used to compiler and
library tests? libstdc++/tests_flags.in is already doing flags
computations; maybe we could start from there...