From: "R. Diez" <rdiezmail-newlib@yahoo.de>
To: Mike Frysinger <vapier@gentoo.org>
Cc: Newlib <newlib@sourceware.org>,
Matthew Joyce <matthew.joyce@embedded-brains.de>,
joel@rtems.org
Subject: Re: Question about autoreconf to regenerate configuration files
Date: Sun, 20 Feb 2022 10:51:58 +0100 [thread overview]
Message-ID: <8f8be7c4-3aa5-0a6f-7ca0-bc8921e0b020@yahoo.de> (raw)
In-Reply-To: <Yg3apoTMTMojanx/@vapier>
> [...]
> things are looking up. with all my pending changes, we have 1 configure script
> in newlib and no recursive makes.
>
> $ time (cd newlib && autoreconf)
> real 0m8.740s
I am grateful that you are doing this work. The old build system was horrible.
> generating autotools is now slightly faster that compiling 8 copies of
> newlib+libgloss :). not that i'm advocating for changing anything :P.
Well, that's a pity. If we are down to 16 seconds for both newlib and libgloss together, I would say that performance is no longer a good reason to check in all those Autotools files.
Regards,
rdiez
prev parent reply other threads:[~2022-02-20 9:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 12:32 Matthew Joyce
2022-01-21 13:44 ` Corinna Vinschen
2022-01-21 15:02 ` R. Diez
2022-01-21 15:37 ` Joel Sherrill
2022-01-21 16:09 ` R. Diez
2022-01-21 22:09 ` Mike Frysinger
2022-01-21 23:08 ` Joel Sherrill
2022-01-22 21:20 ` R. Diez
2022-01-23 0:17 ` Joel Sherrill
2022-01-23 16:57 ` R. Diez
2022-01-26 10:19 ` Mike Frysinger
2022-01-30 22:22 ` R. Diez
2022-01-23 7:29 ` Mike Frysinger
2022-01-26 10:02 ` Mike Frysinger
2022-02-17 5:18 ` Mike Frysinger
2022-02-17 6:56 ` Sebastian Huber
2022-02-20 9:51 ` R. Diez [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=8f8be7c4-3aa5-0a6f-7ca0-bc8921e0b020@yahoo.de \
--to=rdiezmail-newlib@yahoo.de \
--cc=joel@rtems.org \
--cc=matthew.joyce@embedded-brains.de \
--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).