From: Roland Hieber <rhi@pengutronix.de>
To: Ariel Garcia <a.garcia@gemfony.eu>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] OSELAS.toolchain - GCC snapshots gone
Date: Sun, 2 May 2021 15:25:46 +0200 [thread overview]
Message-ID: <20210502132546.3bvfuzm2bgobc36q@pengutronix.de> (raw)
In-Reply-To: <3191367.f4lXhxJLn6@atenea>
On Sat, May 01, 2021 at 04:40:14PM +0200, Ariel Garcia wrote:
> Hello,
>
> trying to reproduce a somewhat older setup using OSELAS 2019.09.1
> I noticed that it fails due to:
>
> -----
> Could not download package
> URL: https://ftp.gnu.org/gnu/gcc/gcc-9-20191130/gcc-9-20191130.tar.xz http://
> ftp.uni-kl.de/pub/gnu/gcc/gcc-9-20191130/gcc-9-20191130.tar.xz https://
> sourceware.org/pub/gcc/snapshots/9-20191130/gcc-9-20191130.tar.xz https://
> sourceware.org/pub/gcc/releases/gcc-9-20191130/gcc-9-20191130.tar.xz http://
> launchpad.net/gcc-linaro/4.8/9-20191130/+download/gcc-9-20191130.tar.xz
> http://launchpad.net/gcc-linaro/4.7/9-20191130/+download/gcc-9-20191130.tar.xz
> http://launchpad.net/gcc-linaro/4.6/9-20191130/+download/gcc-9-20191130.tar.xz
> -----
>
> GNU seems to have cleaned up, and mirrors followed. Also the copy in
> https://www.pengutronix.de/software/ptxdist/temporary-src/
> is gone.
As a quick fix, I've put the copy from our local source archive on the
temporary-src mirror for now. Try again.
> Shouldn't OSELAS always use real releases (GCC and other) instead of (daily?)
> snapshots?
I think gcc-9-20191130 included some fixes to make it build on certain
platforms, so Michael picked that version.
- Roland
> I can't "just update" to a newer OSELAS version, since i rely on reproducible
> builds for performing incremental updates. A change in the compiler would
> imply that all binaries would change...
>
> Any suggestion on how to rely on OSELAS / PTXdist versions to remain
> "buildable" in the future?
>
> Also, any hint on where to find the old snapshot?
> (trying "git archive" from the GCC repo and different commits in the
> releases/gcc-9 branch, but i was unable to find the same md5 sum given by
> OSELAS 2019.09.1)
>
> Thanks a lot,
> Ariel
--
Roland Hieber, Pengutronix e.K. | r.hieber@pengutronix.de |
Steuerwalder Str. 21 | https://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next prev parent reply other threads:[~2021-05-02 13:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-01 14:40 Ariel Garcia
2021-05-02 13:25 ` Roland Hieber [this message]
2021-05-02 16:13 ` Alexander Dahl
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=20210502132546.3bvfuzm2bgobc36q@pengutronix.de \
--to=rhi@pengutronix.de \
--cc=a.garcia@gemfony.eu \
--cc=ptxdist@pengutronix.de \
/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