Created attachment 388374 [details] Build log Rebuilding x11-libs/fltk is failing with "x86_64 no such file or directory" followed by "unrecognised option '-arch'". x86_64-pc-linux-gnu-g++ -I.. -arch x86_64 -Wall -Wunused -Wno-format-y2k -fPIC -fno-exceptions -fno-strict-aliasing -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -I/usr/include/cairo -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libdrm -I/usr/include/libpng16 -O2 -pipe -march=corei7 -mcx16 -msahf -mno-movbe -mno-aes -mno-pclmul -mpopcnt -mno-abm -mno-lwp -mno-fma -mno-fma4 -mno-xop -mno-bmi -mno-bmi2 -mno-tbm -mno-avx -mno-avx2 -msse4.2 -msse4.1 -mno-lzcnt -mno-rdrnd -mno-f16c -mno-fsgsbase --param l1-cache-size=32 --param l1-cache-line-size=64 --param l2-cache-size=8192 -mtune=corei7 -fomit-frame-pointer -DFL_LIBRARY -c Fl.cxx -o Fl.o x86_64-pc-linux-gnu-g++: error: x86_64: No such file or directory x86_64-pc-linux-gnu-g++: error: unrecognized command line option ‘-arch’ ../makeinclude:148: recipe for target 'Fl.o' failed
Created attachment 388376 [details] emerge --info
Comment on attachment 388374 [details] Build log Fix MIME type on attachment
Comment on attachment 388374 [details] Build log It would help if you attached the build log instead of the emerge output.
Would you happen to have a variable ARCHFLAGS set in your environment?
Created attachment 388470 [details] Build log Apologies, I must have mixed up files :/ Build log from /var/tmp/portage/x11-libs/fltk-1.3.2/temp freshly copied
(In reply to Jeroen Roovers from comment #4) > Would you happen to have a variable ARCHFLAGS set in your environment? As a matter of fact it would appear I do, though I'm not sure where it's being exported - grepping root's $HOME and /etc doesn't return anything. `ARCHFLAGS="" emerge -1 x11-libs/fltk` does allow it to build.
(In reply to wraeth from comment #6) > (In reply to Jeroen Roovers from comment #4) > > Would you happen to have a variable ARCHFLAGS set in your environment? > > As a matter of fact it would appear I do, though I'm not sure where it's > being exported - grepping root's $HOME and /etc doesn't return anything. Well, do let us know if it's set by something installed by an ebuild.
I'm closing this bug as I believe it was invalid and related to something in my environment, which seems confirmed by the lack of "me-too's". If anyone disagrees, feel free to re-open.