This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: value of $CXX when building libraries
- To: Phil Edwards <pedwards at disaster dot jaj dot com>
- Subject: Re: value of $CXX when building libraries
- From: Gabriel Dos Reis <gdr at codesourcery dot com>
- Date: 10 Jan 2001 20:05:46 +0100
- Cc: Gabriel Dos Reis <gdr at codesourcery dot com>, Per Bothner <per at bothner dot com>, gcc at gcc dot gnu dot org, libstdc++ at gcc dot gnu dot org
- Organization: CodeSourcery, LLC
- References: <m21yucv74j.fsf@kelso.bothner.com> <flzogzu9yg.fsf@sel.cmla.ens-cachan.fr> <20010110031547.A6142@disaster.jaj.com> <fl8zoju88v.fsf@sel.cmla.ens-cachan.fr> <20010110034345.A6414@disaster.jaj.com> <flzogzk53w.fsf@sel.cmla.ens-cachan.fr> <20010110073915.C7556@disaster.jaj.com>
Phil Edwards <pedwards@disaster.jaj.com> writes:
[...]
| The output from --built-library could be split up like we're currently doing
| to provide all the libtool/compiler invocations. (The things you can do
| after twiddling IFS never cease to amaze me, even after all this time.)
I wish I didn't need to go through that contorsion :-)
| > Per could you try that option?
|
| BTW, Per, be sure to look at the comments at the start of tests_flags[.in]
| if you try --built-library or --installed-library. The results were driving
| me loony until I read that they're /supposed/ to be colon-separated. :-)
Maybe 'test_flags --help' need to be more verbose in that respect.
-- Gaby
CodeSourcery, LLC http://www.codesourcery.com