From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] cross-nasm: nasm.us seems gone. Add extra URL.
Date: Fri, 9 May 2025 09:25:19 +0200 [thread overview]
Message-ID: <20250509072519.2679952-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20250421161641.786297-1-christian.melki@t2data.com>
Thanks, applied as 6d53fc0c6e34c03233857222bf8b00886505866d.
Michael
[sent from post-receive hook]
On Fri, 09 May 2025 09:25:19 +0200, Christian Melki <christian.melki@t2data.com> wrote:
> Don't know what has happened to nasm.us, but it has been
> gone the last couple of days.
> Add another URL to fetch source from (debian archive).
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20250421161641.786297-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/cross-nasm.make b/rules/cross-nasm.make
> index da159da43d93..ea419af71f87 100644
> --- a/rules/cross-nasm.make
> +++ b/rules/cross-nasm.make
> @@ -20,7 +20,9 @@ ifdef PTXCONF_ARCH_X86
> CROSS_NASM_MD5 := 2b8c72c52eee4f20085065e68ac83b55
> CROSS_NASM := nasm-$(CROSS_NASM_VERSION)
> CROSS_NASM_SUFFIX := tar.xz
> -CROSS_NASM_URL := http://www.nasm.us/pub/nasm/releasebuilds/$(CROSS_NASM_VERSION)/$(CROSS_NASM).$(CROSS_NASM_SUFFIX)
> +CROSS_NASM_URL := \
> + http://www.nasm.us/pub/nasm/releasebuilds/$(CROSS_NASM_VERSION)/$(CROSS_NASM).$(CROSS_NASM_SUFFIX) \
> + https://snapshot.debian.org/archive/debian/20250401T023134Z/pool/main/n/nasm/nasm_$(CROSS_NASM_VERSION).orig.$(CROSS_NASM_SUFFIX)
> CROSS_NASM_SOURCE := $(SRCDIR)/$(CROSS_NASM).$(CROSS_NASM_SUFFIX)
> CROSS_NASM_DIR := $(CROSS_BUILDDIR)/$(CROSS_NASM)
> CROSS_NASM_LICENSE := BSD-2-Clause
prev parent reply other threads:[~2025-05-09 7:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-21 16:16 [ptxdist] [PATCH] " Christian Melki
2025-05-09 7:25 ` Michael Olbrich [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=20250509072519.2679952-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=christian.melki@t2data.com \
--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