Bug 219675 - sys-cluster/lam-mpi-7.1.4 fails w/ gcc-4.3.0
|
Bug#:
219675
|
Product: Gentoo Linux
|
Version: 2007.0
|
Platform: All
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: normal
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: hp-cluster@gentoo.org
|
Reported By: loki_val@gentoo.org
|
|
Component: GCC Porting
|
|
|
URL:
|
|
Summary: sys-cluster/lam-mpi-7.1.4 fails w/ gcc-4.3.0
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2008-04-28 22:37 0000
|
*** C++ compiler and preprocessor
checking for i686-pc-linux-gnu-g++... i686-pc-linux-gnu-g++
checking whether we are using the GNU C++ compiler... yes
checking whether i686-pc-linux-gnu-g++ accepts -g... yes
checking dependency style of i686-pc-linux-gnu-g++... gcc3
checking how to run the C++ preprocessor... i686-pc-linux-gnu-g++ -E
checking if want C++ exception handling... no
checking whether i686-pc-linux-gnu-g++ has new(std::nothrow)... no
checking for C++ template repository directory... templates not supported?
not used
checking for C++ compiler template parameters... none needed
checking for C++ optimization flags... -O2 -march=i686 -mtune=athlon-xp -msse
-mmmx -pipe -ggdb3
checking map usability... yes
checking map presence... yes
checking for map... yes
checking for type bool... no
checking for true/false... no
configure: WARNING: *** Your C++ compiler does not support the bool data type.
configure: WARNING: *** LAM requires a C++ compiler with support for the bool
configure: WARNING: *** data type.
configure: error: cannot continue
Created an attachment (id=151289) [details]
config.log
The specific error messages. I'll mail upstream and point them at this bug.
Debian are just patching $S/configure, but that's not the Correct and
Authorized way to do it. Especially when we're doing eautoreconf.
The patch is valid and work. Only, I seem to have stepped in some libtool foo.
Hrmmph...
This is the problem I ran into.
*** [Gentoo] sanity check failed! ***
*** libtool.m4 and ltmain.sh have a version mismatch! ***
*** (libtool.m4 = 1.5.26, ltmain.sh = 1.5.22) ***
I solved it by adding these lines to the ebuild, right after eautoreconf:
for oldltmain in $(grep -l 1.5.22 `find ./ -name 'ltmain.sh'`) ;do
cp config/ltmain.sh ${oldltmain}
done
Not pretty, but it works.
Just added the fixes to cvs for this, should hit the mirrors soon. I don't
have gcc-4.3.0 on any machines to test against so please reopen if you hit any
problems.
Thanks for the patch and report. Extra thanks for emailing upstream :)