unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Taylor R Campbell <campbell+guile@mumble.net>
Cc: 54915-done@debbugs.gnu.org
Subject: bug#54915: [PATCH] Guile rejects empty vendor in GNU triplets, as used by NetBSD
Date: Thu, 16 Jun 2022 09:43:12 +0200	[thread overview]
Message-ID: <878rpxoxyn.fsf@gnu.org> (raw)
In-Reply-To: <20220413112644.6016B60859@jupiter.mumble.net> (Taylor R. Campbell's message of "Wed, 13 Apr 2022 11:26:44 +0000")

Hi,

Taylor R Campbell <campbell+guile@mumble.net> skribis:

>>From 12440a85559c3de5e6bced9c9377f3d5d7f5948e Mon Sep 17 00:00:00 2001
> From: Taylor R Campbell <campbell+guile@mumble.net>
> Date: Wed, 13 Apr 2022 09:51:08 +0000
> Subject: [PATCH] Allow empty vendor string in GNU target triplets.
>
> NetBSD and pkgsrc have been using an empty vendor string since the
> mid-'90s, such as x86_64--netbsd.  pkgsrc has been carrying around a
> workaround just the guile build for a long time.  (Before that,
> NetBSD omitted the vendor altogether, so if x86_64 existed then it
> might have been `x86_64-netbsd', but that caused more problems.)
> This change makes Guile accept an empty vendor string so workarounds
> are no longer necessary.
>
> * module/system/base/target.scm (validate-target): Allow empty vendor
> string in GNU target triplets.

I added tests in cross-compilation.test and committed.

Thanks!

Ludo’.





      reply	other threads:[~2022-06-16  7:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-13 11:26 bug#54915: [PATCH] Guile rejects empty vendor in GNU triplets, as used by NetBSD Taylor R Campbell
2022-06-16  7:43 ` Ludovic Courtès [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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878rpxoxyn.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=54915-done@debbugs.gnu.org \
    --cc=campbell+guile@mumble.net \
    /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).