From: Alexander Dahl <post@lespocky.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] OSELAS.toolchain - GCC snapshots gone
Date: Sun, 2 May 2021 18:13:50 +0200 [thread overview]
Message-ID: <20210502161350.uubnlp5obi75tu32@falbala.internal.home.lespocky.de> (raw)
In-Reply-To: <3191367.f4lXhxJLn6@atenea>
[-- Attachment #1.1: Type: text/plain, Size: 2364 bytes --]
Hello Ariel,
On Sat, May 01, 2021 at 04:40:14PM +0200, Ariel Garcia wrote:
> 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.
>
> Shouldn't OSELAS always use real releases (GCC and other) instead of (daily?)
> snapshots?
>
>
> 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?
In the old days I packed once built toolchains to tarballs and put it
aside and in my backup. Nowadays I use the pre built debian packages
from http://debian.pengutronix.de/ – maybe that's an option for you,
too?
> 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)
Although I keep my src archive in a central place covered by backup, I
doubt I have stuff for oselas toolchain 2019.09.x in there. I can not
remember having used it at all. Otherwise I could have given you a
copy for your own archive or mirror.
Greets
Alex
--
/"\ ASCII RIBBON | »With the first link, the chain is forged. The first
\ / CAMPAIGN | speech censured, the first thought forbidden, the
X AGAINST | first freedom denied, chains us all irrevocably.«
/ \ HTML MAIL | (Jean-Luc Picard, quoting Judge Aaron Satie)
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 181 bytes --]
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
prev parent reply other threads:[~2021-05-02 16:14 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
2021-05-02 16:13 ` Alexander Dahl [this message]
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=20210502161350.uubnlp5obi75tu32@falbala.internal.home.lespocky.de \
--to=post@lespocky.de \
--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