libtool
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Incorrect dependency on GLIBC_PRIVATE symbol, who to blame?


From: Ralf Wildenhues
Subject: Re: Incorrect dependency on GLIBC_PRIVATE symbol, who to blame?
Date: Tue, 13 Oct 2009 06:12:35 +0200
User-agent: Mutt/1.5.20 (2009-08-09)

* Kent Boortz wrote on Sun, Oct 11, 2009 at 08:33:26PM CEST:
> Ralf Wildenhues writes:
> > In order to be able to decide whether libtool is doing something wrong,
> > and what exactly it gets wrong, I'd like to see the output of
> >   ./libtool --tag=CXX --config
> >
> > as well as the output of the link command line in question, with --debug
> > added as first argument to ./libtool.  Please catch both stdout and
> > stderr intermingled (2>&1) and gzip.
> 
> The output is attached,

Not sure yet what would be the best way to avoid this issue, but can you
work around it with either of the following?

- remove -lc -lgcc from /usr/lib/libunwind.la

- the patch below.  This patch is probably a bit too general, but as I
  said I don't know a better one off-hand.

Thanks,
Ralf

diff --git a/libltdl/config/ltmain.m4sh b/libltdl/config/ltmain.m4sh
index 4502e68..1741641 100644
--- a/libltdl/config/ltmain.m4sh
+++ b/libltdl/config/ltmain.m4sh
@@ -4154,6 +4154,9 @@ func_mode_link ()
            # Compiler inserts libc in the correct place for threads to work
            test "X$arg" = "X-lc" && continue
            ;;
+         *-*-linux*)
+           test "X$arg" = "X-lc" && continue
+           ;;
          esac
        elif test "X$arg" = "X-lc_r"; then
         case $host in




reply via email to

[Prev in Thread] Current Thread [Next in Thread]