From: Jakub Jelinek <jakub@redhat.com>
To: Paolo Carlini <paolo.carlini@oracle.com>
Cc: Richard Guenther <richard.guenther@gmail.com>,
Sebastian Pop <sebpop@gmail.com>,
Ralf Wildenhues <ralf.wildenhues@gmx.de>,
GCC Patches <gcc-patches@gcc.gnu.org>,
binutils@sourceware.org, gdb-patches@sourceware.org
Subject: Re: [PATCH] Add -lpwl to ppllibs.
Date: Wed, 02 Mar 2011 12:57:00 -0000 [thread overview]
Message-ID: <20110302125700.GQ30899@tyan-ft48-01.lab.bos.redhat.com> (raw)
In-Reply-To: <4D6E3BCD.1070100@oracle.com>
On Wed, Mar 02, 2011 at 01:45:01PM +0100, Paolo Carlini wrote:
> On 03/02/2011 01:20 PM, Richard Guenther wrote:
> > so it seems it broke some configure tests. I have ppl-0.11 and cloog 0.15.10.
> >
> I was about to send a message...
>
> For the record, it broke the boostrap for me too. Until yesterday I used
> to build successfully with ppl-0.11 and cloog-0.16.1 with
> --enable-cloog-backend=isl. Today I see a lot of undefined references.
> For the record, upgrading to ppl-0.11.2 doesn't help.
It also broke bootstrap with ppl-0.10.2 and cloog-ppl 0.15.7 (which before
didn't try to compile in graphite, now it does, except it doesn't link in
-lppl and uses unconditionally ppl 0.11+ functions).
Jakub
next prev parent reply other threads:[~2011-03-02 12:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110223193905.GD24784@gmx.de>
[not found] ` <1298494027-24185-1-git-send-email-sebpop@gmail.com>
[not found] ` <20110227063524.GD16255@gmx.de>
[not found] ` <AANLkTimoE=0tCvV_ZhJ-Y3BDdFXSkKFTVXZMyic9--Ss@mail.gmail.com>
[not found] ` <20110227093848.GA19328@gmx.de>
2011-03-02 3:53 ` Sebastian Pop
2011-03-02 12:20 ` Richard Guenther
2011-03-02 12:45 ` Paolo Carlini
2011-03-02 12:57 ` Jakub Jelinek [this message]
2011-03-02 18:43 ` Sebastian Pop
2011-03-02 14:49 ` Sebastian Pop
2011-03-02 15:02 ` Richard Guenther
2011-03-02 15:07 ` Sebastian Pop
2011-03-02 15:09 ` Richard Guenther
2011-03-02 15:15 ` Paolo Carlini
2011-03-02 15:21 ` Sebastian Pop
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=20110302125700.GQ30899@tyan-ft48-01.lab.bos.redhat.com \
--to=jakub@redhat.com \
--cc=binutils@sourceware.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=paolo.carlini@oracle.com \
--cc=ralf.wildenhues@gmx.de \
--cc=richard.guenther@gmail.com \
--cc=sebpop@gmail.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