From: Andreas Schwab <schwab@suse.de>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Ulrich Drepper <drepper@redhat.com>,
Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: [PATCH] Support getconf -v POSIX_V6_*LP*OFF*
Date: Fri, 26 Nov 2004 01:12:00 -0000 [thread overview]
Message-ID: <jezn15ct16.fsf@sykes.suse.de> (raw)
In-Reply-To: <20041126000451.GE8259@sunsite.mff.cuni.cz> (Jakub Jelinek's message of "Fri, 26 Nov 2004 01:04:51 +0100")
Jakub Jelinek <jakub@redhat.com> writes:
> On Fri, Nov 26, 2004 at 12:56:07AM +0100, Andreas Schwab wrote:
>> Jakub Jelinek <jakub@redhat.com> writes:
>>
>> > @@ -260,3 +262,13 @@ bug-glob2-ENV = MALLOC_TRACE=$(objpfx)bu
>> >
>> > $(objpfx)bug-glob2-mem: $(objpfx)bug-glob2.out
>> > $(common-objpfx)malloc/mtrace $(objpfx)bug-glob2.mtrace > $@
>> > +
>> > +$(inst_libexecdir)/getconf: $(objpfx)getconf FORCE
>> > + $(addprefix $(..)./scripts/mkinstalldirs ,\
>> > + $(filter-out $(wildcard $@),$@))
>> > + for spec in `LC_ALL=C GETCONF_DIR=/dev/null \
>> > + $(run-program-prefix) $< \
>> > + _POSIX_V6_WIDTH_RESTRICTED_ENVS`; do \
>>
>> This will fail when installing a cross-compiled glibc.
>
> Would _POSIX_V6_WIDTH_RESTRICTED_ENVS || :`; do \
> be ok for you?
What's wrong with 'ifeq (no,$(cross-compiling))'?
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
prev parent reply other threads:[~2004-11-26 1:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-25 23:47 Jakub Jelinek
2004-11-25 23:56 ` Andreas Schwab
2004-11-26 0:04 ` Jakub Jelinek
2004-11-26 1:12 ` Andreas Schwab [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=jezn15ct16.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=drepper@redhat.com \
--cc=jakub@redhat.com \
--cc=libc-hacker@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).