bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Bruno Haible <INVALID.NOREPLY@gnu.org>
To: bug-gnulib@gnu.org
Subject: GNU gnulib: calling for beta-testers
Date: Sun, 21 Apr 2024 06:52:39 -0400 (EDT)	[thread overview]
Message-ID: <20240421-125239.sv1871.186403@savannah.gnu.org> (raw)

If you are developer on a package that uses GNU gnulib as part of its build
system:

gnulib-tool has been known for being slow for many years. We have listened to
your complaints. A rewrite of gnulib-tool in another programming language
(Python) is ready for beta-testing. It is between 8 times and 100 times faster
than the original gnulib-tool.

Both implementations should behave identically, that is, produce the same
generated files and the same output. You can help us ensure this, through the
following steps:

1. Make sure you have Python (version 3.7 or newer) installed on your
machine.

2. Update your gnulib checkout. (For some packages, it comes as a git
submodule named 'gnulib'.) Like this:

  $ git checkout master
  $ git pull

     Set the environment variable GNULIB_SRCDIR, pointing to this checkout.

     If the package is using a git submodule named 'gnulib', it is also
advisable to do

  $ git commit -m 'build: Update gnulib submodule to latest.' gnulib

     (as a preparation for step 5, because the --no-git option does not work
as expected in all variants of 'bootstrap').

3. Set an environment variable that enables checking that the two
implementations behave the same:

  $ export GNULIB_TOOL_IMPL=sh+py


4. Clean the built files of your package:

  $ make -k distclean


5. Regenerate the fetched and generated files of your package. Depending on
the package, this may be a command such as

  $ ./bootstrap --no-git --gnulib-srcdir=$GNULIB_SRCDIR

     or

  $ export GNULIB_SRCDIR; ./autopull.sh; ./autogen.sh

     or, if no such script is available:

  $ $GNULIB_SRCDIR/gnulib-tool --update

     If there is a failure, due to differences between the 'sh' and 'py'
results, please report it to <bug-gnulib@gnu.org>.

6. If this invocation was successful, you can trust the rewritten gnulib-tool
and use it from now on, by setting the environment variable

  $ export GNULIB_TOOL_IMPL=py


7. Continue with

  $ ./configure
  $ make

     as usual.

And enjoy the speed! The rewritten gnulib-tool was implemented by Dmitry
Selyutin, Collin Funk, and me.



_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/



             reply	other threads:[~2024-04-21 10:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-21 10:52 Bruno Haible [this message]
2024-04-21 11:52 ` GNU gnulib: calling for beta-testers Vivien Kraus
2024-04-22  7:56 ` Paul Eggert
2024-04-22  8:23   ` Collin Funk
2024-04-22  8:51     ` diffutils __pycache__ failure Collin Funk
2024-04-22 11:38       ` Bruno Haible
2024-04-22 19:44         ` Collin Funk
2024-04-22 20:55           ` Bruno Haible
2024-04-22 11:22     ` GNU gnulib: calling for beta-testers Bruno Haible
2024-04-22 20:00       ` Collin Funk
2024-04-22 20:56         ` Bruno Haible
     [not found] <7232287.lbvTjQenqM@nimes>
     [not found] ` <7ef75a77-ec33-43e0-8e57-8960b09ccd5a@akhlaghi.org>
2024-04-21 22:27   ` Bruno Haible
2024-04-22  7:16     ` Paul Eggert
2024-04-22  8:17       ` Mohammad Akhlaghi

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://lists.gnu.org/mailman/listinfo/bug-gnulib

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

  git send-email \
    --in-reply-to=20240421-125239.sv1871.186403@savannah.gnu.org \
    --to=invalid.noreply@gnu.org \
    --cc=bug-gnulib@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.
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).