When trying to emerge the lcms package it fails on compilation with a "no such file or directory" error. The main problem is that there is no missing directory or file listed. The output looks like this: [...] mkdir .libs i686-pc-linux-gnu-g++ -DPACKAGE_NAME=\"lcms\" -DPACKAGE_TARNAME=\"lcms\" -DPACKAGE_VERSION=\"1.17\" "-DPACKAGE_STRING=\"lcms 1.17\"" -DPACKAGE_BUGREPORT=\"\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DSIZEOF_INT=4 -DSIZEOF_UNSIGNED_INT=4 -DSIZEOF_LONG=4 -DSIZEOF_UNSIGNED_LONG=4 -DSIZEOF_LONG_LONG=8 -DSIZEOF_UNSIGNED_LONG_LONG=8 -DHasZLIB=1 -I. -I/usr/include/python2.4 -I/usr/include/python2.4 -I../include -I../include "%{CFLAGS}" -c lcms_wrap.cxx -DPIC i686-pc-linux-gnu-g++: %{CFLAGS}: No such file or directory make[1]: *** [_lcms_la-lcms_wrap.lo] Error 1 make[1]: Leaving directory `/var/tmp/portage/media-libs/lcms-1.17/work/lcms-1.17/python' make: *** [all-recursive] Error 1 Reproducible: Always Steps to Reproduce: 1. emerge lcms Actual Results: Everything runs fine until it reaches g++ call after creating the directory .libs. The error output looks like this: [...] mkdir .libs i686-pc-linux-gnu-g++ -DPACKAGE_NAME=\"lcms\" -DPACKAGE_TARNAME=\"lcms\" -DPACKAGE_VERSION=\"1.17\" "-DPACKAGE_STRING=\"lcms 1.17\"" -DPACKAGE_BUGREPORT=\"\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DSIZEOF_INT=4 -DSIZEOF_UNSIGNED_INT=4 -DSIZEOF_LONG=4 -DSIZEOF_UNSIGNED_LONG=4 -DSIZEOF_LONG_LONG=8 -DSIZEOF_UNSIGNED_LONG_LONG=8 -DHasZLIB=1 -I. -I/usr/include/python2.4 -I/usr/include/python2.4 -I../include -I../include "%{CFLAGS}" -c lcms_wrap.cxx -DPIC i686-pc-linux-gnu-g++: %{CFLAGS}: No such file or directory make[1]: *** [_lcms_la-lcms_wrap.lo] Error 1 make[1]: Leaving directory `/var/tmp/portage/media-libs/lcms-1.17/work/lcms-1.17/python' make: *** [all-recursive] Error 1 Expected Results: There should be at least a path to a directory or file which is missing, but the error names no such path. Additional output of emerge after stopping the compilation is: ERROR: media-libs/lcms-1.17 failed. Call stack: ebuild.sh, line 49: Called src_compile environment, line 2322: Called die The specific snippet of code: emake || die "emake failed" The die message: emake 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/lcms-1.17/temp/build.log'. The ebuild environment file is located at '/var/tmp/portage/media-libs/lcms-1.17/temp/environment'.
[cite] -I../include "%{CFLAGS}" -c lcms_wrap.cxx -DPIC [/cite] Looks to me that you have set CXXFLAGS="%{CFLAGS}". Check your /etc/make.conf and make sure it says there CXXFLAGS="${CFLAGS}" ^ Note the "$" there! If error persists, please post your emerge --info as well. If it compiles fine, this bug is INVALID
I have been able to resolv this issue on my system by running emerge --sync emerge --deep --update world # now retry emerge lcms So I still don't know what this problem caused and if it is really fixed (if it ever was a bug).
(In reply to comment #1) > [cite] > -I../include "%{CFLAGS}" -c lcms_wrap.cxx -DPIC > [/cite] > > Looks to me that you have set CXXFLAGS="%{CFLAGS}". > Check your /etc/make.conf and make sure it says there > CXXFLAGS="${CFLAGS}" > ^ > Note the "$" there! > > If error persists, please post your emerge --info as well. > If it compiles fine, this bug is INVALID > Hello, yes I see, you're right that was the actual mistake, it seems its been running now because I have manually set the CXXFLAG because there was an error at another package compilation.
