Summary: | aiksaurus fails to link with gcc 3.4, linktool somehow messes up | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Mikko Tiihonen <mikko.tiihonen> |
Component: | Current packages | Assignee: | Please assign to toolchain <gcc-porting> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 54837 | ||
Bug Blocks: | 48528 | ||
Attachments: | Full log when compiled with empty CFLAGS and CXXFLAGS |
Description
Mikko Tiihonen
2004-04-22 22:30:31 UTC
The linking is successfull when I change the "g++" to "gcc" on the libtool line: /bin/sh ../libtool --mode=link gcc -march=..... I do not know if the problem is in libtool that cannot handle g++ correctly or does the configure script just mess up the Makefiles. mine didn't have any problems emerging.. maybe it's your CFLAGS? I tried emerging with both CFLAGS and CXXFLAGS empty, but the error message is exactly the same. Also re-emerging linktool did not help. This is how far I got when I started emerge --emptytree world with gcc 3.4 so I do not think that the compiler is the problem either. It could be that the libtool that aiksaurus uses (1.5a) just doesn't handle x86_64 linking correctly. Created attachment 30058 [details]
Full log when compiled with empty CFLAGS and CXXFLAGS
aiksaurus-1.2.1 should fix this as well. |