public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/58995] Use of -ldl in libcilkrts breaks bootstrap
Date: Tue, 05 Nov 2013 00:32:00 -0000 [thread overview]
Message-ID: <bug-58995-4-zMhRT6vwgX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58995-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58995
--- Comment #1 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Tue, Nov 05, 2013 at 12:20:59AM +0000, kargl at gcc dot gnu.org wrote:
>
> bsupc++/.libs -lpthread -ldl -L/home/sgk/gcc/obj4x/./gcc
> /home/sgk/gcc/obj4x/x86_64-unknown-freebsd10.0/libstdc++-v3/src/.libs/libstdc++.so
> -lm -lc -lgcc_s /home/sgk/gcc/obj4x/./gcc/crtendS.o /usr/lib/crtn.o
> -Wl,-soname -Wl,libcilkrts.so.5 -o .libs/libcilkrts.so.5
> /usr/bin/ld: cannot find -ldl
> collect2: error: ld returned 1 exit status
> gmake[2]: *** [libcilkrts.la] Error 1
> gmake[2]: Leaving directory
> `/usr/home/sgk/gcc/obj4x/x86_64-unknown-freebsd10.0/libcilkrts'
> gmake[1]: *** [all-target-libcilkrts] Error 2
> gmake[1]: Leaving directory `/usr/home/sgk/gcc/obj4x'
> gmake: *** [all] Error 2
>
> This is caused by the hardcoded reference to libdl.
>
> troutmask:sgk[319] grep ldl libcilkrts/Makefile.am
> AM_LDFLAGS = -lpthread -ldl
> libcilkrts_la_LDFLAGS += -lpthread -ldl
>
> Please fix.
>
For the moment, hand editing x86_64-unknown-freebsd10.0/libcilkrts/Makefile
to remove the two offending -ldl allows the build to complete.
next parent reply other threads:[~2013-11-05 0:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-58995-4@http.gcc.gnu.org/bugzilla/>
2013-11-05 0:32 ` sgk at troutmask dot apl.washington.edu [this message]
2013-11-05 4:23 ` kargl at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-58995-4-zMhRT6vwgX@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).