This is the mail archive of the
mailing list for the libstdc++ project.
Re: V3 and cross-compiler (AIX 4.3 64-bit mode)
- To: Mark Mitchell <mark at codesourcery dot com>
- Subject: Re: V3 and cross-compiler (AIX 4.3 64-bit mode)
- From: David Edelsohn <dje at watson dot ibm dot com>
- Date: Fri, 08 Jun 2001 15:29:52 -0400
- cc: bkoz at redhat dot com, ro at TechFak dot Uni-Bielefeld dot DE, rboehne at ricardo-us dot com, pedwards at disaster dot jaj dot com, libstdc++ at gcc dot gnu dot org, Alexandre Oliva <aoliva at redhat dot com>
>>>>> Mark Mitchell writes:
Mark> I think that limits.h and friends should actually live in CVS and be
Mark> specified by the target configury. Then, we just rebuild 'em all when
Mark> the gen* program changes, and check in a new version.
Mark> In other words, I think having the ability to generate them
Mark> automagically is very useful, but we shouldn't be doing it every time
Mark> we build the compiler and libraries.
I would much prefer to define these parameters in
libstdc++-v3/config/os/aix/bits/std_limits.h depending on __64BIT__ macro
and not worry about inquiring at build-time.
I am not sure what to do for the GCC 3.0 release. The current fix
now prevents creating a bogus file, but the ppc64 multilib fails and
building all libraries exits. The failure is sort of artificial because,
unlike the link failure on Irix, everything can be built on the 32-bit AIX
While src/limitsMEMBERS.cc is the same, include/bits/std_limits.h
presumably is not (for "long int" in LP64 mode). Any suggestions on how
to work around this for the GCC 3.0 release?