public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Reinoud Koornstra <reinoudkoornstra@gmail.com>
To: muhammad hatami <muhammadrezahatami@gmail.com>
Cc: crossgcc@sourceware.org
Subject: Re: build error
Date: Wed, 6 Oct 2021 18:54:02 +0200	[thread overview]
Message-ID: <CAAA5faGqfSyn2JqwftNmzu9GuJMKzYP2cB6Nm8xDGPE6fi4DDw@mail.gmail.com> (raw)
In-Reply-To: <CANVy1tieSs2UfFZGTRwwGMvmcN3PhQ4HiKkAE6bso1sRiNjqvw@mail.gmail.com>

Hi Muhammad,

It seems that that site is down? Question is do you really that isl 0.24 as
you can also get earlier versions of isl with which GCC itself compiles
just fine. Can you change the build script to fetch it from
https://guix.gnu.org/packages/isl-0.18/ for example and see if it works?
Or perhaps you can find 0.24 from somewhere else? Thanks,

Reinoud.


On Wed, Oct 6, 2021, 11:18 AM muhammad hatami via crossgcc <
crossgcc@sourceware.org> wrote:

> hello,
>
> iam using ct-ng version 1.24 and my os is ubuntu 20.10
>
> i got build error (same error from ./ct-ng source) from build.log file its
> because of it cant get a package "
> http://isl.gforge.inria.fr/isl-0.24.tar.gz"
> (connections fails)
>
> i tried to use vpn and i also tried it on a different machine and network
> but i got same error
>
> i attached build.log file
>
> please please help me
>
> thanks
> --
> For unsubscribe information see http://sourceware.org/lists.html#faq
>

  reply	other threads:[~2021-10-06 17:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-06  9:17 muhammad hatami
2021-10-06 16:54 ` Reinoud Koornstra [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-02-03 12:17 Build Error Alexandr Zatevalov
2012-02-03 20:07 ` Alexandr Zatevalov
2012-02-03 20:11   ` Bryan Hundven

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=CAAA5faGqfSyn2JqwftNmzu9GuJMKzYP2cB6Nm8xDGPE6fi4DDw@mail.gmail.com \
    --to=reinoudkoornstra@gmail.com \
    --cc=crossgcc@sourceware.org \
    --cc=muhammadrezahatami@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).