From: Richard Earnshaw <Richard.Earnshaw@foss.arm.com>
To: Mike Frysinger <vapier@gentoo.org>, newlib@sourceware.org
Subject: newlib not building (needs aclocal)
Date: Tue, 22 Feb 2022 11:57:44 +0000 [thread overview]
Message-ID: <6e6ec1c8-70b3-5cc2-3b06-60f516a44ed0@foss.arm.com> (raw)
Mike,
I think something you've changed is forcing the newlib build to now need
a local installation of automake. This wasn't needed before unless you
were updating the makefiles locally.
CDPATH="${ZSH_VERSION+.}:" && cd [...]/libgloss && /bin/bash
[...]/missing aclocal-1.15 -I . -I .. -I ../config
[...]/missing: line 81: aclocal-1.15: command not found
WARNING: 'aclocal-1.15' is missing on your system.
You should only need it if you modified 'acinclude.m4' or
'configure.ac' or m4 files included by 'configure.ac'.
Did you leave something out of a commit somewhere? If not, how can this
be fixed so that we don't need automake during normal builds from the repo?
R.
PS While I appreciate what you're trying to do here, the timing couldn't
be worse given that we're trying to stabilize a GCC release and all my
builds are breaking at present.
next reply other threads:[~2022-02-22 11:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 11:57 Richard Earnshaw [this message]
2022-02-22 22:11 ` [PATCH/committed] libgloss: enable maintainer mode support Mike Frysinger
2022-02-23 11:26 ` Richard Earnshaw
2022-02-23 6:01 ` newlib not building (needs aclocal) Brian Inglis
2022-02-23 11:33 ` Richard Earnshaw
2022-02-24 7:07 ` Mike Frysinger
2022-02-24 7:11 ` Mike Frysinger
2022-02-24 9:08 ` Corinna Vinschen
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=6e6ec1c8-70b3-5cc2-3b06-60f516a44ed0@foss.arm.com \
--to=richard.earnshaw@foss.arm.com \
--cc=newlib@sourceware.org \
--cc=vapier@gentoo.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).