From: Mark Wielaard <mark@klomp.org>
To: Christophe Lyon <christophe.lyon@linaro.org>
Cc: buildbot@sourceware.org
Subject: Re: [PATCH 4/5] autoregen.py: libcpp can use autoreconf
Date: Thu, 18 Apr 2024 23:46:47 +0200 [thread overview]
Message-ID: <20240418214647.GE25080@gnu.wildebeest.org> (raw)
In-Reply-To: <20240417145033.2077525-4-christophe.lyon@linaro.org>
Hi,
On Wed, Apr 17, 2024 at 02:50:32PM +0000, Christophe Lyon wrote:
> After libcpp's aclocal.m4 and configure were fixed in GCC, we can now
> use autoreconf for it too.
This works now, but it does show some warnings:
Entering directory /home/mark/src/gcc/libcpp
+ autoreconf-2.69 -f
configure.ac:91: warning: macro 'AM_LANGINFO_CODESET' not found in library
configure.ac:112: warning: macro 'AM_ICONV' not found in library
autoreconf-2.69: configure.ac: AM_GNU_GETTEXT is used, but not AM_GNU_GETTEXT_VERSION
next prev parent reply other threads:[~2024-04-18 21:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 14:50 [PATCH 1/5] autoregen.py: enable autoreconf for gcc, libdecnumber, libiberty, libobjc Christophe Lyon
2024-04-17 14:50 ` [PATCH 2/5] autoregen.py: Move subdirs common to binutils-gdb and gcc Christophe Lyon
2024-04-17 14:50 ` [PATCH 3/5] autoregen.py: improve comment Christophe Lyon
2024-04-17 14:50 ` [PATCH 4/5] autoregen.py: libcpp can use autoreconf Christophe Lyon
2024-04-18 21:46 ` Mark Wielaard [this message]
2024-04-19 8:20 ` Christophe Lyon
2024-04-17 14:50 ` [PATCH 5/5] autoregen.py: Add introduction comment Christophe Lyon
2024-04-17 15:12 ` Simon Marchi
2024-04-18 9:59 ` Christophe Lyon
2024-04-18 21:55 ` Mark Wielaard
2024-04-19 8:22 ` Christophe Lyon
2024-04-18 21:53 ` [PATCH 1/5] autoregen.py: enable autoreconf for gcc, libdecnumber, libiberty, libobjc Mark Wielaard
2024-04-19 8:21 ` Christophe Lyon
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=20240418214647.GE25080@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=buildbot@sourceware.org \
--cc=christophe.lyon@linaro.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).