This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: value of $CXX when building libraries
- To: Gabriel Dos Reis <gdr at codesourcery dot com>
- Subject: Re: value of $CXX when building libraries
- From: Phil Edwards <pedwards at disaster dot jaj dot com>
- Date: Wed, 10 Jan 2001 03:15:47 -0500
- Cc: Per Bothner <per at bothner dot com>, gcc at gcc dot gnu dot org
- References: <m21yucv74j.fsf@kelso.bothner.com> <flzogzu9yg.fsf@sel.cmla.ens-cachan.fr>
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? 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.
Phil
--
pedwards at disaster dot jaj dot com | pme at sources dot redhat dot com
devphil at several other less interesting addresses in various dot domains
The gods do not protect fools. Fools are protected by more capable fools.