public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Carsten Schoenert <c.schoenert@gmail.com>
To: crossgcc@sourceware.org
Subject: Re: [PATCH] Add support for latest CLooG and ISL required by GCC 4.8
Date: Fri, 15 Nov 2013 13:53:00 -0000	[thread overview]
Message-ID: <5286272C.6090606@googlemail.com> (raw)
In-Reply-To: <5268386E.4070908@googlemail.com>

Hello,

no one have a good idea?

Am 23.10.2013 22:58, schrieb Carsten Schoenert:
> Hello Yann,
> 
> On 15.03.2013 18:53, Yann E. MORIN wrote:
>> Steven, All,
>>
>> On Friday 15 March 2013 Steven Newbury wrote:
>>> On Fri, 2013-03-15 at 00:29 +0100, Yann E. MORIN wrote:
>>>> Please, can you confirm the following (I think I read that somewhere,
>>>> can't find it again, though...):
>>>>   - even if CLooG now requires ISL and not PPL, PPL is still needed
>>>>     directly by gcc, right?
>>>> (so, gcc still needs to "select CC_GCC_NEEDS_PPL")
>>>
>>> This was the case until recently.  GCC trunk no longer uses PPL.
>>
>> OK, so we'll have to rework hos gcc 'selects' PPL.
> 
> I don't know exactly if my build issue is related to this older post,
> but I think it depends a little bit on this.
> 
> I use the last crosstool-ng release 1.19.0 and try to build a ARM
> crosstoolchain with
> GCC 4.8.1
> Binutils 2.22
> EGlibc 2.17
> GMP 5.1.1
> MPFR 3.1.2
> ISL 0.11.1
> Cloog 0.18.0
> MPC 0.9
> 
> The build fails while try to download cloog-ppl-0.18.0 what is wrong I
> think as this file nothere exits.
>> [ALL  ]    Resolving gcc.gnu.org (gcc.gnu.org)... 209.132.180.131
>> [ALL  ]    Connecting to gcc.gnu.org (gcc.gnu.org)|209.132.180.131|:21... connected.
>> [ALL  ]    Logging in as anonymous ... Logged in!
>> [ALL  ]    ==> SYST ... done.    ==> PWD ... done.
>> [ALL  ]    ==> TYPE I ... done.  ==> CWD (1) /pub/gcc/infrastructure ... done.
>> [ALL  ]    ==> SIZE cloog-ppl-0.18.0 ... done.
>> [ALL  ]    ==> PASV ... done.    ==> RETR cloog-ppl-0.18.0 ... 
>> [ALL  ]    No such file 'cloog-ppl-0.18.0'.
>> [ALL  ]    
>> [ERROR]  
>> [ERROR]  >>
>> [ERROR]  >>  Build failed in step 'Retrieving needed toolchain components' tarballs'
>> [ERROR]  >>        called in step '(top-level)'
>> [ERROR]  >>
>> [ERROR]  >>  Error happened in: do_cloog_get[scripts/build/companion_libs/cloog.sh@735]
>> [ERROR]  >>        called from: do_companion_libs_get[scripts/build/companion_libs.sh@15]
>> [ERROR]  >>        called from: main[scripts/crosstool-NG.sh@577]
>> [ERROR]  >>
>> [ERROR]  >>  There is a list of known issues, some with workarounds, in:
>> [ERROR]  >>      '/home/carsten/tmp/ctng-build/share/doc/crosstool-ng/ct-ng.1.19.0/B - Known issues.txt'
>> [ERROR]  
>> [ERROR]  (elapsed: 0:22.01)
>> make: *** [build] Fehler 1
> 
> Because I don't the interna of crosstool-ng I also don't know which
> tunig has to be done. ;)
> So any checks I can do?
> 
> Regards
> Carsten
> 

--
For unsubscribe information see http://sourceware.org/lists.html#faq

  reply	other threads:[~2013-11-15 13:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5141DCFC.1070408@ispras.ru>
2013-03-14 23:29 ` Yann E. MORIN
2013-03-15 11:33   ` Steven Newbury
2013-03-15 17:54     ` Yann E. MORIN
2013-10-23 20:58       ` Carsten Schoenert
2013-11-15 13:53         ` Carsten Schoenert [this message]
2013-03-20  9:39   ` Dmitry Plotnikov
2013-03-20 22:35     ` Cody P Schafer

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=5286272C.6090606@googlemail.com \
    --to=c.schoenert@gmail.com \
    --cc=crossgcc@sourceware.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).