This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug lto/47528] New: liblto_plugin.so not found should not to be an fatal error
- From: "dongsheng.song at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sat, 29 Jan 2011 03:28:21 +0000
- Subject: [Bug lto/47528] New: liblto_plugin.so not found should not to be an fatal error
- Auto-submitted: auto-generated
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47528
Summary: liblto_plugin.so not found should not to be an fatal
error
Product: gcc
Version: 4.6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: lto
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: dongsheng.song@gmail.com
When build gcc without CRT available like mingw-w64:
1. Build Binutils
2. Install mingw-w64-headers
3. Make all-gcc and install-gcc
4. Build mingw-w64 CRT and install
5. Make all-target-libgcc and install-target-libgcc
6. Build pthread and install
7. Make gcc finally and install
In step 4, gcc should create simple C program which need not use CRT functions.
But if gcc configured with enable-lto, there will have an fatal error:
i686-w64-mingw32-gcc: fatal error: -fuse-linker-plugin, but liblto_plugin.so
not found
In my opinion, if liblto_plugin.so not found, gcc should issued an error
message and going on gengerate code without lto support.