https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89893
--- Comment #27 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to 康 珊 from comment #26)
> I found the previous build log is like "g++ -o
> /builddir/build/BUILD/node-v10.15.3/out/Release/cctest -pthread -rdynamic
> -m64
> -Wl,--whole-archive,/builddir/build/BUILD/node-v10.15.3/out/Release/obj.
> target/deps/uv/libuv.a -Wl,--no-whole-archive -Wl,-z,noexecstack
> -Wl,--whole-archive
> /builddir/build/BUILD/node-v10.15.3/out/Release/obj.target/deps/v8/gypfiles/
> libv8_base.a -Wl,--no-whole-archive -Wl,-z,relro -Wl,-z,now -Wl,-T
> /builddir/build/BUILD/node-v10.15.3/src/large_pages/ld.implicit.script
> -pthread -flto=4 -fuse-linker-plugin -ffat-lto-objects -fno-lto
> -Wl,--start-group
> /builddir/build/BUILD/node-v10.15.3/out/Release/obj.target/cctest/test/
> cctest/node_test_fixture.o...", you mean link options like "-flto=4
> -ffat-lto-objects -fno-lto" are not accurate and "-fno-lto" will not take
> effect, right?
It will take effect, but you defined that only in LDFLAGS.
Anyway, please don't use --enable-lto with {LD,C,CXX}FLAGS="${LDFLAGS}
-fno-lto"!
