http://bugzilla.suse.com/show_bug.cgi?id=1151068 http://bugzilla.suse.com/show_bug.cgi?id=1151068#c7 --- Comment #7 from Martin Liška --- (In reply to Michel Normand from comment #6)

Created attachment 818717 [details] bug1676475_configs.tgz

I will do the build verbose, But I previously did a build trial in my ppc64le env and retrieved the configure log and status in attached tgz. At least the config.log is reporting gcc still using -flto=4 while configure executed, and LDFLAGS set with -flto=4 (not CFLAGS)

Then you'll need to investigate why is the option still set? I see in the build log: [ 72s] + CFLAGS='-fmessage-length=0 -grecord-gcc-switches -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type -g' [ 72s] + export CFLAGS [ 72s] + CXXFLAGS='-fmessage-length=0 -grecord-gcc-switches -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type -g' [ 72s] + export CXXFLAGS [ 72s] + FFLAGS='-fmessage-length=0 -grecord-gcc-switches -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type -g ' [ 72s] + export FFLAGS [ 72s] + FCFLAGS='-fmessage-length=0 -grecord-gcc-switches -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type -g ' [ 72s] + export FCFLAGS which does not contain any -flto. Maybe the option is somehow inherited from a different package in configure? -- You are receiving this mail because: You are on the CC list for the bug.