This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug lto/41376] collect2 does not handle static libraries
- From: "bmei at broadcom dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 4 May 2010 16:54:56 -0000
- Subject: [Bug lto/41376] collect2 does not handle static libraries
- References: <bug-41376-10053@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #6 from bmei at broadcom dot com 2010-05-04 16:54 -------
> So this is a rough first draft of the-kind-of-thing-i-was-thinking-of. We get
> collect2 to run a dummy link early, and extract the output from the
> --lto-assist flag to get a list of archive members that we need lto to
> recompile for us.
>
Well I spent some time to read into collect2/lto code and understand pro/cons
of different approaches. So far, adding --lto-assist to ld/hacking collect2
approach looks reasonable to me, though it does require gnu ld. What extra info
should be in a complete symbol resolution file?
--
bmei at broadcom dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bmei at broadcom dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41376