Errors on x86_64 (broken c++ headers?)
Ralf Corsepius
rc040203 at freenet.de
Thu May 12 15:45:11 UTC 2005
On Thu, 2005-05-12 at 10:03 -0500, Quentin Spencer wrote:
> Panu Matilainen wrote:
>
> > On Thu, 12 May 2005, Quentin Spencer wrote:
> >
> >> ...
> >> So, the errors appear to be caused by the c++ header files. How is it
> >> possible that the header files are broken on one arch and not
> >> another? Any other insights into what might have caused this and how
> >> to fix it?
> >
> > There's something weird about mach and C++, I've seen this and some
> > other weirdness just recently myself. The above can be worked around
> > by setting
> > a suitable CPPFLAGS=-I/usr/include/c++ ... before %configure.
> >
> > Another oddity I found is that for Wine to build within mach I had to use
> > LDFLAGS="-lstdc++" %configure - which doesn't make any sense to me
> > either.
>
> Thanks for the tips.
Sorry, these are work-arounds to bugs. They should be inacceptable to be
added to rpm specs.
g++ is supposed to find its internal headers and libraries without any
manual assistance.
> So, this is a bug in mach then?
Dunno.
> Why only on x86_64?
Probably multilibs.
> I'd like to get this thing to build finally, so I'm inclined to add this
> change to configure and submit a rebuild. However, it seems wrong to
> have to change the spec file because of a bug in something external.
It doesn't seem wrong, it is wrong!
Ralf
More information about the fedora-extras-list
mailing list