Re: how to "parse" gcc -v output

On Sun, 4 Apr 2010, Ralf Wildenhues wrote: > How would g++ know that part of the objects were from Fortran sources? By looking for undefined symbols matching patterns for symbols from libgfortran. > Maybe from a different (non-GCC) Fortran compiler, that needs a > different set of libraries at

Re: link-time optimization

On 04/04/2010 11:54 AM, Ralf Wildenhues wrote: > * Ralf Wildenhues wrote on Sun, Mar 28, 2010 at 05:33:44PM CEST: >> I'm still working on a patch to support -flto in libtool, it needs >> changes in several places. > > I have a preliminary(!) patch set here for LTO support in libtool. Hi, Thanks

Re: how to "parse" gcc -v output

* Joseph S. Myers wrote on Sun, Apr 04, 2010 at 11:40:19AM CEST: > On Sun, 4 Apr 2010, Ralf Wildenhues wrote: > > > - which libraries it needs to link shared modules against, or > > - which libraries are needed to let g++ link mixed C++/Fortran code, > > so in practice there is no other choice (un

Re: how to "parse" gcc -v output

On Sun, 4 Apr 2010, Ralf Wildenhues wrote: > - which libraries it needs to link shared modules against, or > - which libraries are needed to let g++ link mixed C++/Fortran code, > so in practice there is no other choice (unless the user provides this > information). [...] > I'm willing to add API

[PATCH 4/4] Add $pic_flag to archive_cmds and archive_expsym_cmds.

* libltdl/m4/libtool.m4 (_LT_LINKER_SHLIBS) [GNU ld, netbsd]: Add $pic_flag if ELF. [GNU ld, solaris]: Likewise. [GNU ld, default case]: Likewise. [!GNU ld, freebsd, dragonfly]: Add $pic_flag. [!GNU ld, GCC, hpux9]: Add $pic_flag. [!GNU ld, GCC, hpux10]: Replace -fPIC with $pic_flag [!GNU ld, GCC,

[PATCH 3/4] Uniform const'ness of symlist variable lt_preloaded_symbols.

On some systems, lt_preloaded_symbols may not be declared const due to relocation issues. C99 requires qualification to match for compatible declarations, so ensure we declare const'ness in the same way everywhere; link-time optimization may otherwise rightfully complain about inconsistencies. Sin

Re: link-time optimization

* Ralf Wildenhues wrote on Sun, Mar 28, 2010 at 05:33:44PM CEST: > > I'm still working on a patch to support -flto in libtool, it needs > changes in several places. I have a preliminary(!) patch set here for LTO support in libtool. DO NOT submit this to your favorite distribution, it is not ready

how to "parse" gcc -v output

Hello gcc and libtool lists, Both Autoconf and Libtool have macros which "parse" output of 'gcc -v' for some link commands. Yes, I know, almost by definition this is not "parseable" text, but GCC does not provide a stable API that allows to find out - which libraries it needs to link shared modul