-
Bug
-
Resolution: Unresolved
-
P4
-
24
The gcc devkit contains (for example)
./x86_64-linux-gnu-to-x86_64-linux-gnu/libexec/gcc/x86_64-linux-gnu/13.2.0/liblto_plugin.so
but an LTO-enabled build (--enable-jvm-feature-link-time-opt) needs
./x86_64-linux-gnu-to-x86_64-linux-gnu/lib/bfd-plugins/liblto_plugin.so
Presumably the latter should be a symlink to the former. Manually making such a symlink in my installed devkit seemed to work.
Without this I get a build warning message during the build: "plugin needed to handle lto object", and later the build fails with a ton of undefined references.
See also this gcc bug about the same issue:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70345
./x86_64-linux-gnu-to-x86_64-linux-gnu/libexec/gcc/x86_64-linux-gnu/13.2.0/liblto_plugin.so
but an LTO-enabled build (--enable-jvm-feature-link-time-opt) needs
./x86_64-linux-gnu-to-x86_64-linux-gnu/lib/bfd-plugins/liblto_plugin.so
Presumably the latter should be a symlink to the former. Manually making such a symlink in my installed devkit seemed to work.
Without this I get a build warning message during the build: "plugin needed to handle lto object", and later the build fails with a ton of undefined references.
See also this gcc bug about the same issue:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70345
- relates to
-
JDK-8343698 Linux x86_64 lto build gives a lot of warnings and fails lto-wrapper: fatal error: make returned 2 exit status
- Resolved