Re: Should libtool link in libgcc when building a shared library?
On Wed, Mar 23, 2005 at 03:25:05PM -0800, Steve Ellcey wrote:
> I look at the file libtool.m4 from libtool 1.5.10, and I see:
>
> # Check if GNU C++ uses GNU ld as the underlying linker, since the
> # archiving commands below assume that GNU ld is being used.
> if test "$with_gnu_ld" = yes; then
> _LT_AC_TAGVAR(archive_cmds, $1)='$CC -shared -nostdlib $predep_objects
> $libobjs $deplibs $postdep_objects $compiler_flags ${wl}-soname $wl$soname -o
> $lib'
>
> It uses the compiler to link but it also uses -nostdlib and so we are
> not using the compiler to automatically link in any libraries. It is
> the use of -nostdlib that I am most interested in. Will that usage
> continue?
What's the value of $postdep_objects?
--
albert chin ([EMAIL PROTECTED])
___
http://lists.gnu.org/mailman/listinfo/libtool
Re: Should libtool link in libgcc when building a shared library?
> From: Bob Friesenhahn <[EMAIL PROTECTED]>
>
> >From the beginning, libtool took the approach that it knew best. It
> would glean the list of libraries that the compiler would supply,
> extend the list, and then do the link using the system linker.
>
> More recently, libtool has started to change its approach. For C++,
> linking is already done using the compiler. I believe that this has
> started to change for C as well. It is a gradual process since care
> must be taken to not break something which already works.
But when it uses the C++ compiler (and that compiler is GNU g++), does
it also use -nostdlib? It looks to me like it does, but I could be
wrong. I.e. I look at the file libtool.m4 from libtool 1.5.10, and I
see:
# Check if GNU C++ uses GNU ld as the underlying linker, since the
# archiving commands below assume that GNU ld is being used.
if test "$with_gnu_ld" = yes; then
_LT_AC_TAGVAR(archive_cmds, $1)='$CC -shared -nostdlib $predep_objects
$libobjs $deplibs $postdep_objects $compiler_flags ${wl}-soname $wl$soname -o
$lib'
It uses the compiler to link but it also uses -nostdlib and so we are
not using the compiler to automatically link in any libraries. It is
the use of -nostdlib that I am most interested in. Will that usage
continue?
Steve Ellcey
[EMAIL PROTECTED]
___
http://lists.gnu.org/mailman/listinfo/libtool
Re: Should libtool link in libgcc when building a shared library?
On Wed, 23 Mar 2005, Steve Ellcey wrote: libtool certainly would not want to explicitly add '-lgcc' to a link line, my question is why libtool goes out of its way to remove '-lgcc' (by using the -nostdlib option). The issue of different compilers does not seem to apply here because we know we are using GCC (otherwise we couldn't add -nostdlib). From the beginning, libtool took the approach that it knew best. It would glean the list of libraries that the compiler would supply, extend the list, and then do the link using the system linker. More recently, libtool has started to change its approach. For C++, linking is already done using the compiler. I believe that this has started to change for C as well. It is a gradual process since care must be taken to not break something which already works. Bob == Bob Friesenhahn [EMAIL PROTECTED], http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer,http://www.GraphicsMagick.org/ ___ http://lists.gnu.org/mailman/listinfo/libtool
Re: Should libtool link in libgcc when building a shared library?
> From: Bob Friesenhahn <[EMAIL PROTECTED]> > > > I would just like to verify that the intended behaviour of libtool, when > > using GCC to build a shared library, is to *not* automatically include > > '-lgcc' on the link line used to build the shared library. > > Libtool does not include '-lgcc' because it is a compiler-specific > support library that the compiler normally provides. It may not make > sense to use -lgcc if a different compiler is used. libtool certainly would not want to explicitly add '-lgcc' to a link line, my question is why libtool goes out of its way to remove '-lgcc' (by using the -nostdlib option). The issue of different compilers does not seem to apply here because we know we are using GCC (otherwise we couldn't add -nostdlib). Steve Ellcey [EMAIL PROTECTED] ___ http://lists.gnu.org/mailman/listinfo/libtool
Offshore Corporations - Infiinteaza simplu o firma cu impozit 0%, TVA 0%
* PARADIS FISCAL / TAX HAVENS * Esti un om de afaceri de succes! (ROMANIAN / ENGLISH) Te-ai gindit vreodata sa infiintezi o companie OFFSHORE? Stiai ca societatile comerciale offshore sunt infiintate in paradisuri fiscale? Acolo nu se plateste nici un impozit ! Nici TVA, nici accize, nici taxe pe dividende. Mai mult ! Nu se tine contabilitate ! Mai mult ! Actionarii si directorii sunt CONFIDENTIALI. Nimeni nu are datoria morala de a plati maximum de impozite ! DE CE sa platesti tu ??? Suna-ma la 0233/227744 sau 0740 637709 Numele meu este Alberto Kurtyan si iti voi raspunde gratuit la orice intrebare despre fiscalitate si corporatii offshore. email: [EMAIL PROTECTED] www.bnc.ro Din strainatate> +40 233 227744 sau +40 740 637709 * Dear Business Owner, Have you ever thought of registering an offshore corporation?? Did you know that the offshore corporations are established in Fiscal Paradises? There is no income tax there. Neither VAT, excise tax or tax on dividends. Moreover, you don't need to keep books and report income. Even more ! Stockholder's and CEO's names are confidential. Nobody has a moral duty to pay maximum of taxes! Why should you pay? Call me at 0233/227744 or 0740 637709 I'm Alberto Kurtyan and I'll answer any questions you may have about offshore corporations and tax management. email: [EMAIL PROTECTED] www.bnc.ro International customers CALL > +40 233 227744 sau +40 740 637709 ___ http://lists.gnu.org/mailman/listinfo/libtool
Re: Should libtool link in libgcc when building a shared library?
On Wed, 23 Mar 2005, Steve Ellcey wrote: I would just like to verify that the intended behaviour of libtool, when using GCC to build a shared library, is to *not* automatically include '-lgcc' on the link line used to build the shared library. Libtool does not include '-lgcc' because it is a compiler-specific support library that the compiler normally provides. It may not make sense to use -lgcc if a different compiler is used. Bob == Bob Friesenhahn [EMAIL PROTECTED], http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer,http://www.GraphicsMagick.org/ ___ http://lists.gnu.org/mailman/listinfo/libtool
Should libtool link in libgcc when building a shared library?
I would just like to verify that the intended behaviour of libtool, when using GCC to build a shared library, is to *not* automatically include '-lgcc' on the link line used to build the shared library. Is that the correct, intended behaviour? The reason I ask is I am trying to port libffi (part of GCC) to IA64 HP-UX and am using the HP-UX linker. libffi has a dependency on libgcc, but is currently not including '-lgcc' on the link line that builds libffi. This causes the HP linker to issue a warning when I link a program against libffi. In the 1.4 (?) based libtool that is in the GCC sources, some platforms use GCC to link and when they do that they get -lgcc automatically. I made this change (locally) and it fixed my problem, but when I look at the latest libtool sources I see that platforms that use GCC to link now also use '-nostdlib' and thus would not get the '-lgcc' automatically. So it seems like the change I made is not the correct change (since it would get undone if and when GCC updated to libtool 1.5.*. Rather I need to add an explicit '-lgcc' to the libtool command line that creates libffi instead. Does that sound right? Steve Ellcey [EMAIL PROTECTED] ___ http://lists.gnu.org/mailman/listinfo/libtool
Fw:
$B40A4L5NA3NDj!*!*!*(B
$B:#$^$G!"[EMAIL PROTECTED],(B
$B9%I>$K$D$-!"A49q3HBg!*!*:#$,%A%c%s%9$G$9!#(B
$B"(%3%3$KEPO?$7$F$k=w$N;R$OK\Ev$G$9!#(B
1.$B5U!{=u4uK>[EMAIL PROTECTED](B
2.$B#S#M4uK>[EMAIL PROTECTED](B
3.$B:#F|[EMAIL PROTECTED](B
4.$BITNQ4uK>[EMAIL PROTECTED](B
[EMAIL PROTECTED]|Bj(B
$BAa$/$7$J$$$H#S#O#L#D!!#O#U#T(B
http://loves.qsv20.com/
___
http://lists.gnu.org/mailman/listinfo/libtool
