From: Stefan Monnier <monnier@iro.umontreal.ca>
To: James Luke <james92856@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Make cross-compiling temacs easier: drop gnulib for build intermediates, or use recursive autoconf?
Date: Sat, 26 Jun 2021 09:56:15 -0400 [thread overview]
Message-ID: <jwvtulkpwjc.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CAFOX7SizgGTBJdakSnLcttkgUgGO0MeWdx01PghoX8oYWfBZsA@mail.gmail.com> (James Luke's message of "Fri, 25 Jun 2021 19:22:10 -0700")
> These intermediates both use gnulib (with #include <config.h> etc), but
> configure.ac only configures gnulib for the host machine. So the headers,
> #defines, and library are all wrong for the build machine and compilation
> fails. To fix this, I'd like to rewrite make-fingerprint.c and
> make-docfile.c to avoid non-portable constructs and thus the dependency on
> gnulib, but I don't know if this is considered acceptable for a GNU
> project.
Have you looked at what that would take?
E.g. how do you plan to deal with the sha256 code used by make-fingerprint.c
and normally provided by gnulib?
How 'bout doing "a bit of both": i.e. use a separate gnulib+autoconf for
those two executables, but patch them when it's easy to try and minimize
the reliance on gnulib and autoconf?
Stefan
prev parent reply other threads:[~2021-06-26 13:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-26 2:22 Make cross-compiling temacs easier: drop gnulib for build intermediates, or use recursive autoconf? James Luke
2021-06-26 6:26 ` Eli Zaretskii
2021-06-26 22:56 ` James Luke
2021-06-27 6:08 ` Eli Zaretskii
2021-06-26 13:56 ` Stefan Monnier [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
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=jwvtulkpwjc.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=james92856@gmail.com \
/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).