From: <Paul_Koning@Dell.com>
To: <eggert@cs.ucla.edu>
Cc: <palves@redhat.com>, <gdb@sourceware.org>, <bug-gnulib@gnu.org>
Subject: Re: Cross-build issues in gdb/gnulib
Date: Tue, 25 Aug 2015 17:10:00 -0000 [thread overview]
Message-ID: <35C35F17-7514-4999-8CFE-994F4D99E41B@dell.com> (raw)
In-Reply-To: <55DC9EC3.2080508@cs.ucla.edu>
> On Aug 25, 2015, at 12:58 PM, Paul Eggert <eggert@cs.ucla.edu> wrote:
>
> Pedro Alves wrote:
>> # Test for the AIX locale name.
>>> if (LC_ALL=ja_JP LC_TIME= LC_CTYPE= ./conftest; exit) 2>/dev/null; then
>>> gt_cv_locale_ja=ja_JP
>>>
>>> The comment refers to AIX, but it is in fact executed in the "*" case of a case statement, i.e., for everything other than Windows. The same code pattern also appears in the two other locale-*.m4 files.
>
> I'm lost. Do you have a specific Gnulib patch in mind?
Perhaps you missed the original problem report, which is that this configure machinery doesn't take into account cross-builds. And that broke badly on a build=X86_64-linux, host=i386-netbsdelf cross-build, because Linux attempted to execute the generated conftest image (a NetBSD image). That's wrong of course, but worse yet, it got into an infinite loop, apparently the emulation is buggy. So my build got stuck.
I learned about AC_RUN_IFELSE and constructed a fix with that.
paul
prev parent reply other threads:[~2015-08-25 17:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-24 21:20 Paul_Koning
2015-08-25 9:56 ` Pedro Alves
2015-08-25 13:12 ` Paul_Koning
2015-08-25 13:40 ` Pedro Alves
2015-08-25 16:58 ` Paul Eggert
2015-08-25 17:06 ` Paul_Koning
2015-08-25 17:54 ` Pedro Alves
2015-08-25 17:10 ` Paul_Koning [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=35C35F17-7514-4999-8CFE-994F4D99E41B@dell.com \
--to=paul_koning@dell.com \
--cc=bug-gnulib@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=gdb@sourceware.org \
--cc=palves@redhat.com \
/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