From: Sebastian Huber <sebastian.huber@embedded-brains.de>
To: newlib@sourceware.org
Subject: Re: Question about autoreconf to regenerate configuration files
Date: Thu, 17 Feb 2022 07:56:36 +0100 [thread overview]
Message-ID: <6a08b091-6496-7d34-4294-acc88396611c@embedded-brains.de> (raw)
In-Reply-To: <Yg3apoTMTMojanx/@vapier>
Hello Mike,
On 17/02/2022 06:18, Mike Frysinger wrote:
> we can see that killing excessive configure scripts & recursive makes helps
> with compilation times too.
>
> $ time (cd build; ../configure --host=bfin-elf; make -j4)
> real 0m28.831s
> user 0m34.828s
> sys 0m23.093s
>
> generating autotools is now slightly faster that compiling 8 copies of
> newlib+libgloss :). not that i'm advocating for changing anything :P.
thanks a lot for cleaning up the build system. I always had trouble to
understand how it works and your changes are really helpful (for example
the removal of the libtool support). Speeding up the build is nice.
--
embedded brains GmbH
Herr Sebastian HUBER
Dornierstr. 4
82178 Puchheim
Germany
email: sebastian.huber@embedded-brains.de
phone: +49-89-18 94 741 - 16
fax: +49-89-18 94 741 - 08
Registergericht: Amtsgericht München
Registernummer: HRB 157899
Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
Unsere Datenschutzerklärung finden Sie hier:
https://embedded-brains.de/datenschutzerklaerung/
next prev parent reply other threads:[~2022-02-17 6:56 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 [this message]
2022-02-20 9:51 ` R. Diez
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=6a08b091-6496-7d34-4294-acc88396611c@embedded-brains.de \
--to=sebastian.huber@embedded-brains.de \
--cc=newlib@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).