>=media-libs/sdl-mixer-1.2.7 fails to emerge, giving the infamous error: "configure: error: C compiler cannot create executables". The reason is that all sci-libs acml versions in portage (and sci-libs/mkl as well) creates a env file, 35acml, which contains the following lines: LDPATH=/opt/acml4.0.0/gfortran64_int64/lib INCLUDE=/opt/acml4.0.0/gfortran64_int64/include of course, they change depending of the version installed. At least sdl-mixer since 1.2.7 version make use of INCLUDE variable and use it as CFLAGS (see its configure.in file, lines 55-69, I can attach it if necessary). When using acml (and mkl), INCLUDE is set to /opt/acml4.0.0/gfortran64_int64/include, the configure script try to use this as a CFLAG and it fails because is a directory and not a valid flag. This happens when acml is installed, it doesn't mind if another blas/lapack implementation is being used via eselect. Possible solutions are: 1.- Dirty hack I tried: change 35acml to these lines: LDPATH=/opt/acml4.0.0/gfortran64_int64/lib INCLUDE=-L/opt/acml4.0.0/gfortran64_int64/include don't know if it will b0rk other things 2.- Avoid sdl-mixer and some other programs using INCLUDE variable. 3.- Change acml ebuilds to not put an env file and use the solution suggested in bug #128084 which, for some reason, it isn't used anymore. I'm providing config.log and emerge -v --info in the next comment. Reproducible: Always Steps to Reproduce: 1. emerge acml (or mkl) 2. emerge sdl-mixer Actual Results: sdl-mixer fails showing the call stack next. Expected Results: sdl-mixer gets installed call stack: ./configure --prefix=/usr --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --disable-dependency-tracking --disable-music-midi --disable-timidity-midi --enable-music-mod --enable-music-libmikmod --enable-music-mp3 --enable-music-ogg --libdir=/usr/lib64 --build=x86_64-pc-linux-gnu checking build system type... x86_64-pc-linux-gnu checking host system type... x86_64-pc-linux-gnu checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc checking for C compiler default output file name... configure: error: C compiler cannot create executables See `config.log' for more details. !!! Please attach the following file when filing a report to bugs.gentoo.org: !!! /var/tmp/portage/media-libs/sdl-mixer-1.2.7/work/SDL_mixer-1.2.7/config.log * * ERROR: media-libs/sdl-mixer-1.2.7 failed. * Call stack: * ebuild.sh, line 1695: Called dyn_compile * ebuild.sh, line 1033: Called qa_call 'src_compile' * ebuild.sh, line 44: Called src_compile * sdl-mixer-1.2.7.ebuild, line 41: Called econf '--disable-dependency-tracking' '--disable-music-midi' '--disable-timidity-midi' '--enable-music-mod' '--enable-music-libmikmod' '--enable-music-mp3' '--enable-music-ogg' * ebuild.sh, line 632: Called die * The specific snippet of code: * die "econf failed" * The die message: * econf failed * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/media-libs/sdl-mixer-1.2.7/temp/build.log'. *
Created attachment 135148 [details] config.log This is the config.log produced when trying to emerge sdl-mixer. The INCLUDE variable: juantxorena@localhost ~/Desktop $ echo $INCLUDE /opt/acml4.0.0/gfortran64_int64/include I'm not showing emerge -v --info because is too long and I think that is useless in this bug.
A little OT: acml-4.0.1 has been released. The ebuild for 4.0.0 version works with a name change. If the solution of this problem has to change acml ebuilds, maybe the version bump can wait till this bug is fixed and commit the updated and correct ebuild.
same problem here: echo $INCLUDE /opt/intel/cc/10.0.026/include icc 10.x seam to set the $INCLUDE env too. after doing 'export INCLUDE=""' evrything went fine
Hi, acml, mkl, icc and ifc should now be free of the INCLUDE variable. Re-emerge the corresponding packages after a sync and the problem should be gone. Thanks.
*** Bug 209547 has been marked as a duplicate of this bug. ***
*** Bug 209645 has been marked as a duplicate of this bug. ***
