unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mario Lang <mlang@blind.guru>
To: emacs-devel@gnu.org
Subject: Re: Compilation speed
Date: Wed, 19 Aug 2020 11:25:37 +0200	[thread overview]
Message-ID: <87d03n7zse.fsf@tugraz.at> (raw)
In-Reply-To: <52a7dda9-7fc5-bc33-d2ea-ad325e2cde96@cs.ucla.edu> (Paul Eggert's message of "Thu, 6 Aug 2020 12:07:14 -0700")

Paul Eggert <eggert@cs.ucla.edu> writes:

> On 8/6/20 8:20 AM, Lars Ingebrigtsen wrote:
>
>> And then ./configure takes 19 seconds, and that's fully single-threaded,
>> I believe?  And...  I'm guessing there's no way to get that to be
>> multi-threaded?
>
> You'd either have to rework Autoconf to make it multiprocess
> (difficult) or split configure.ac into pieces and run several
> './configure' pieces in parallel (this might be doable but would still
> be tricky).

The "speed" of autoconf is probably the reason why its adoption rate is
falling.  I remember insisting on using autoconf for many years, just
because.  Until I figured out CMake 3.x.  I will never write an autoconf
script again, never.

-- 
AR Mario Lang                               Phone: +43 316 873 6897
Graz University of Technology              Mobile: +43 664 60 873 6897
IT-Services for research and teaching       Email: mlang@tugraz.at
Steyrergasse 30/1, 8010 Graz, Austria       Please https://useplaintext.email/



  reply	other threads:[~2020-08-19  9:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-06 15:20 Compilation speed Lars Ingebrigtsen
2020-08-06 19:07 ` Paul Eggert
2020-08-19  9:25   ` Mario Lang [this message]
2020-08-19  9:43     ` tomas
2020-08-19 12:37       ` Ergus
2020-08-06 22:14 ` Stefan Monnier
2020-08-07  6:55   ` Lars Ingebrigtsen
2020-08-07 16:26   ` Andrea Corallo via Emacs development discussions.
2020-08-10 14:33 ` Arthur Miller
2020-08-12  2:11   ` Paul Eggert
2020-08-12 12:53     ` Arthur Miller
2020-08-12 16:08       ` Stefan Monnier
2020-08-12 16:59       ` Paul Eggert

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87d03n7zse.fsf@tugraz.at \
    --to=mlang@blind.guru \
    --cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).