From: Jeffrey Walton <noloader@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: "Alexey Dokuchaev" <danfe@nsu.ru>,
"Tijl Coosemans" <tijl@freebsd.org>,
"Gnulib bugs" <bug-gnulib@gnu.org>,
"Bruno Haible" <bruno@clisp.org>,
51144@debbugs.gnu.org
Subject: Re: bug#51144: GNU grep 3.7 fails to build on FreeBSD
Date: Sat, 16 Oct 2021 17:06:56 -0400 [thread overview]
Message-ID: <CAH8yC8=6jwUmqjoJfJZwuq3qVyPTsNBm7gZ_xoHx=ceJ5Yj2WA@mail.gmail.com> (raw)
In-Reply-To: <9f102510-fe6a-8156-8a00-962538bfef24@cs.ucla.edu>
On Sat, Oct 16, 2021 at 12:53 PM Paul Eggert <eggert@cs.ucla.edu> wrote:
>
> On 10/16/21 9:40 AM, Tijl Coosemans wrote:
> > Where
> > necessary we simply pass --build=x64_64-portbld-freebsd$(version). An
> > example is gcc.
>
> Could you pass --build=x64_64-portbld-freebsd$(version) to every
> 'configure' invocation, not just gcc's and a few others?
>
> If I understand you correctly, doing that would have avoided this
> particular problem, and it would avoid other potential problems with
> gnulib/m4's float_h.m4, host-cpu-c-abi.m4, lib-prefix.m4, multiarch.m4,
> printf.m4, as well as in GNU projects other than Gnulib (I haven't tried
> to catalog them).
Related, that may affect Solaris, too. I believe Sun prefers the amd64 prefix.
And there's no telling what some of the other lesser known distros are doing.
Jeff
next prev parent reply other threads:[~2021-10-16 21:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211012025300.GA43189@regency.nsu.ru>
[not found] ` <a24e453e-9e54-b5f2-61df-2fe64bb49aec@cs.ucla.edu>
[not found] ` <20211013040258.GA99982@regency.nsu.ru>
2021-10-13 18:47 ` bug#51144: GNU grep 3.7 fails to build on FreeBSD Paul Eggert
2021-10-14 14:02 ` Alexey Dokuchaev via Gnulib discussion list
2021-10-14 17:34 ` Paul Eggert
2021-10-15 7:32 ` Alexey Dokuchaev via Gnulib discussion list
2021-10-16 16:40 ` Tijl Coosemans
2021-10-16 16:53 ` Paul Eggert
2021-10-16 21:06 ` Jeffrey Walton [this message]
2021-10-16 21:54 ` Paul Eggert
2021-10-17 21:20 ` Bruno Haible
2021-10-18 2:03 ` Alexey Dokuchaev via Gnulib discussion list
2021-10-18 5:18 ` Bruno Haible
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://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAH8yC8=6jwUmqjoJfJZwuq3qVyPTsNBm7gZ_xoHx=ceJ5Yj2WA@mail.gmail.com' \
--to=noloader@gmail.com \
--cc=51144@debbugs.gnu.org \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=danfe@nsu.ru \
--cc=eggert@cs.ucla.edu \
--cc=tijl@freebsd.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).