From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Core 121 error downloading toolchain
Date: Wed, 13 Jun 2018 20:27:12 +0200 [thread overview]
Message-ID: <1528914432.14230.5.camel@ipfire.org> (raw)
In-Reply-To: <ea96c81b1574ec8f4fe3d4ac04dead860e28c7b6.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 738 bytes --]
Hi Michael,
Am Mittwoch, den 13.06.2018, 18:57 +0100 schrieb Michael Tremer:
> Hello,
>
> the file is here:
>
> https://source.ipfire.org/toolchains/
>
> What is in your logs?
tried as usual to download the current sources and the appropriate
toolchain via './make.sh gettoolchain' and get this message, there are
no further log entries.
>
> -Michael
>
> On Wed, 2018-06-13 at 18:24 +0200, ummeegge wrote:
> >
> > Hi all,
> > i wanted to report that it is currently not possible to download
> > the
> > toolchain:
> >
> > Jun 13 15:27:42: Load toolchain image for x86_64
> > Jun 13 15:27:42: error downloading ipfire-2.21-toolchain-20180213-
> > x86_64
> > toolchain for x86_64 machine
> >
> >
> > Greetings,
> >
> > Erik
next prev parent reply other threads:[~2018-06-13 18:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 16:24 ummeegge
2018-06-13 17:57 ` Michael Tremer
2018-06-13 18:27 ` ummeegge [this message]
2018-06-13 18:28 ` Michael Tremer
2018-06-13 18:34 ` ummeegge
2018-06-13 18:35 ` Michael Tremer
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=1528914432.14230.5.camel@ipfire.org \
--to=ummeegge@ipfire.org \
--cc=development@lists.ipfire.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