USE="-bootstrap fortran nls objc objc++ -test" x86_64 with 2.6.30-gentoo-r4 kernel Build fails without libffi beeing installed like this: /var/tmp/portage/sys-devel/llvm-gcc-2.6_pre2/work/llvm-gcc4.2-2.6.source/obj/./prev-gcc/xgcc -B/var/tmp/portage/sys-devel/llvm-gcc-2.6_pre2/work/llvm-gcc4.2-2.6.source/obj/./prev-gcc/ -B/usr/lib64/llvm-gcc-4.2-2.6/x86_64-pc-linux-gnu/bin/ -g -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Wold-style-definition -Wmissing-format-attribute -DHAVE_CONFIG_H -o gfortran \ gcc.o opts-common.o gcc-options.o gfortranspec.o version.o prefix.o intl.o driver-i386.o ../libcpp/libcpp.a ../libiberty/libiberty.a ../libdecnumber/libdecnumber.a -L/usr/lib -lpthread -lffi -ldl -lm /usr/lib/gcc/x86_64-pc-linux-gnu/4.3.4/../../../../x86_64-pc-linux-gnu/bin/ld: cannot find -lffi collect2: ld returned 1 exit status make[3]: *** [gfortran] Error 1 make[3]: *** Waiting for unfinished jobs.... rm gcov.pod gfdl.pod cpp.pod gpl.pod gfortran.pod fsf-funding.pod gcc.pod make[3]: Leaving directory `/var/tmp/portage/sys-devel/llvm-gcc-2.6_pre2/work/llvm-gcc4.2-2.6.source/obj/gcc' make[2]: *** [all-stage2-gcc] Error 2 make[2]: Leaving directory `/var/tmp/portage/sys-devel/llvm-gcc-2.6_pre2/work/llvm-gcc4.2-2.6.source/obj' make[1]: *** [stage2-bubble] Error 2 make[1]: Leaving directory `/var/tmp/portage/sys-devel/llvm-gcc-2.6_pre2/work/llvm-gcc4.2-2.6.source/obj' make: *** [all] Error 2 Sorry I didn't save the full log or tried without fortran but it definitely compiled with libffi installed.
Most likely also sys-devel/llvm, based on this, # ./configure --help | grep ffi --enable-libffi Check for the presence of libffi (default is YES)
Nope, llvm went without problems. I installed it without llvm-gcc at first.
(In reply to comment #2) > Nope, llvm went without problems. I installed it without llvm-gcc at first. > It's a optional depend (automagic) so it would use it if present.
ssuominen, I suppose this bug was why you were looking for me on IRC ;) For llvm, I added the libffi USE flag (enabled by default, after checking the release notes for 2.6), thanks for spotting it! However building llvm-gcc with the same USE flags and libffi unmerged ran fine (including fortran), I'll check if llvm-gcc should have a libffi USE-flag linked to llvm's one, or if it's enough to enable/disable it in llvm
Strange... I just installed libffi. It did not compile before, but it did compile afterwards. Maybe because llvm was already installed without llvm-gcc useflag? Or Because I am running on x86_64?
Both should not affect this behaviour. Just tested on 2 machines, llvm-gcc compiles fine without libffi and with USE=-libffi in llvm. So probably llvm had picked up libffi (probably the gcc bundled version) in your system, but llvm-gcc only works with dev-libs/libffi. I'll leave the bug open if someone else encounters the problem, now that llvm has its libffi USE-flag
So far so good :) Closing fixed
