From: "H.J. Lu" <hjl.tools@gmail.com>
To: Ian Lance Taylor <iant@google.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Graphite build fails if PPL configured with --disable-shared
Date: Mon, 11 May 2009 23:45:00 -0000 [thread overview]
Message-ID: <6dc9ffc80905111313l7f190d37sc1c4f7fd3bd4615a@mail.gmail.com> (raw)
In-Reply-To: <m3prefxv25.fsf@google.com>
On Mon, May 11, 2009 at 1:07 PM, Ian Lance Taylor <iant@google.com> wrote:
> Another Graphite build issue: it appears that I must not use
> --disable-shared when I configure PPL. If I do use --disable-shared, I
> get this:
>
> /home/iant/gnu/ppl-0.10.2-install/lib/libppl_c.a(ppl_c_implementation_common.o): In function `finalize':
> /home/iant/gnu/ppl-0.10.2/interfaces/C/../../src/ppl.hh:1842: undefined reference to `operator delete(void*)'
>
> followed by thousands of similar errors. This is unfortunate, as it
> means that I must manually set LD_LIBRARY_PATH to the directory where
> the PPL library is installed. This also makes it harder for anybody
> else to run the compiler that I build. This needs to be fixed.
>
>
Personally, I think all those extra libraries should be linked in
statically. Otherwise, I can't give my compiler binaries to others.
I have been using:
http://gcc.gnu.org/ml/gcc-patches/2009-04/msg00132.html
--
H.J.
next prev parent reply other threads:[~2009-05-11 20:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-11 20:13 Ian Lance Taylor
2009-05-11 20:13 ` Andrew Pinski
2009-05-11 20:14 ` Andrew Pinski
2009-05-11 23:45 ` H.J. Lu [this message]
2009-05-11 23:48 ` Janis Johnson
2009-05-12 17:45 ` Roberto Bagnara
2009-05-12 18:05 ` Ian Lance Taylor
2009-05-12 19:31 ` Laurent GUERBY
2009-05-12 19:49 ` Andreas Schwab
2009-05-12 20:03 ` Laurent GUERBY
2009-05-12 20:25 ` Andreas Schwab
2009-05-12 20:48 ` Laurent GUERBY
2009-07-08 19:18 ` Maik Beckmann
2009-05-12 21:39 ` Janis Johnson
2009-05-12 8:13 ` Laurent GUERBY
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=6dc9ffc80905111313l7f190d37sc1c4f7fd3bd4615a@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=iant@google.com \
/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).