From: Andreas Schwab <schwab@suse.de>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] intl: reintroduce unintentionally disabled optimization
Date: Mon, 22 Feb 2016 14:31:00 -0000 [thread overview]
Message-ID: <mvmd1rozuiw.fsf@hawking.suse.de> (raw)
In-Reply-To: <874md096x0.fsf@mid.deneb.enyo.de> (Florian Weimer's message of "Mon, 22 Feb 2016 15:05:47 +0100")
Florian Weimer <fw@deneb.enyo.de> writes:
> Can we have autoreconf automatically generate config.h.in, like other
> GNU projects do?
That doesn't work with our use of sysdep configure scripts.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2016-02-22 14:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-24 0:07 Dmitry V. Levin
2016-01-24 8:46 ` Andreas Schwab
2016-01-24 18:13 ` [PATCH v2] " Dmitry V. Levin
2016-02-22 9:17 ` Mike Frysinger
2016-02-22 12:01 ` Dmitry V. Levin
2016-02-22 12:51 ` Andreas Schwab
2016-02-22 12:59 ` Dmitry V. Levin
2016-02-22 13:09 ` Andreas Schwab
2016-02-22 14:07 ` Dmitry V. Levin
2016-02-22 14:32 ` Andreas Schwab
2016-02-22 12:31 ` [PATCH] " Florian Weimer
2016-02-22 13:06 ` Dmitry V. Levin
2016-02-22 14:05 ` Florian Weimer
2016-02-22 14:23 ` Q: generate config.h.in automatically (was: Re: [PATCH] intl: reintroduce unintentionally disabled optimization) Dmitry V. Levin
2016-02-22 14:31 ` Andreas Schwab [this message]
2016-02-22 16:27 ` [PATCH] intl: reintroduce unintentionally disabled optimization Mike Frysinger
2016-02-22 18:25 ` Joseph Myers
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=mvmd1rozuiw.fsf@hawking.suse.de \
--to=schwab@suse.de \
--cc=fw@deneb.enyo.de \
--cc=libc-alpha@sourceware.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).