cflags have params (processor is amd e-350): --param l1-cache-size=32 --param l1-cache-line-size=64 --param l2-cache-size=512 www-client/chromium-22.0.1229.2-r1 ebuild morph cflags: --param l2-cache-size=512 => --param ../printing/l2-cache-size=512 final linking will fail with message "x86_64-pc-linux-gnu-g++: error: ../printing/l2-cache-size=512: No such file or directory" Reproducible: Always Steps to Reproduce: 0. include "--param l2-cache-size=512" 1. start emerge of www-client/chromium-22.0.1229.2-r1 2. wait untill message ">>> Source configured." appears 3. see for example /var/tmp/portage/www-client/chromium-22.0.1229.2-r1/work/chromium-22.0.1229.2/chrome/ipclist.target.mk 4. you will see: LIBS := \ \ -lX11 -lXcursor \ -lrt \ ... ../printing/l2-cache-size=512 \ ... Actual Results: final linking will fail with message "x86_64-pc-linux-gnu-g++: error: ../printing/l2-cache-size=512: No such file or directory"
Created attachment 321468 [details] emerge --info
Created attachment 321470 [details] build.log.tar.xz
Comment on attachment 321470 [details] build.log.tar.xz Please do not put a single file in a tar archive.
This looks like bug 396133.
yeah it does. the big problem with this sort of bug is not about unsafe cflags but because gcc -march=native can include those problem flags but the correct, -march=amdfam10 in my case, does not include those flags
*** This bug has been marked as a duplicate of bug 396133 ***
