This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: config-ml.in AIX multilibs and documentation
- To: David Edelsohn <dje at watson dot ibm dot com>
- Subject: Re: config-ml.in AIX multilibs and documentation
- From: Alexandre Oliva <aoliva at redhat dot com>
- Date: 14 Jun 2001 03:02:06 -0300
- Cc: gcc-patches at gcc dot gnu dot org, libstdc++ at gcc dot gnu dot org
- Organization: GCC Team, Red Hat
- References: <200106140324.XAA28986@makai.watson.ibm.com>
On Jun 14, 2001, David Edelsohn <dje@watson.ibm.com> wrote:
> I mainly would like to find a way for the V3 configuration failure
> to skip that particular multilib instead of crashing the build. Any
> suggestions on how to accomplish that?
How about modifying libstdc++-v3/mknumeric_limits so as to mask the
failure if target and CC match certain patterns? We'd have to pass
target down to mknumeric_limits, but this might even be a good idea:
we could then have pre-built limits files created for each
architecture/OS/multilib, so that cross-builds wouldn't have to
guess.
Short term, we could have mknumeric_limits use the ``default values
for cross compiles'' if the test program fails to compile or to link.
I'm not sure these defaults would be appropriate for AIX64, though. I
was under the impression those defaults would be correctly computed at
run-time in case of cross compiles, but now I realize that's not the
case.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me