From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: p.stephani2@gmail.com, Alan Third <alan@idiocy.org>,
Eli Zaretskii <eliz@gnu.org>,
emacs-devel@gnu.org
Subject: Re: Files in build-aux
Date: Mon, 03 May 2021 13:34:50 -0700 [thread overview]
Message-ID: <87y2cvsgid.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87k0ofmvid.fsf@igel.home> (Andreas Schwab's message of "Mon, 03 May 2021 22:07:22 +0200")
Andreas Schwab <schwab@linux-m68k.org> writes:
> On Mai 03 2021, Alan Third wrote:
>
>> It looks like it may require a run of autogen.sh to generate the
>> changes.
>
> Since Emacs does not use automake, nothing should be touching these
> files.
I want to say that I saw those files after playing with native
compilation, with the:
./configure --with-native-compilation
call. Normally I don't use "configure" at all. I've attempted a couple
times over the past few weeks to build with native compilation (Arch's
libgccjit was broken for a bit), and that might explain why I've seen
this more than once. I'm now unable to reproduce the problem, starting
with "make distclean" and then the configure invocation from above.
Maybe this is a red herring, I don't know.
Eric
next prev parent reply other threads:[~2021-05-03 20:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-01 11:49 Files in build-aux Alan Third
2021-05-03 18:36 ` Philipp Stephani
2021-05-03 18:56 ` Eli Zaretskii
2021-05-03 19:04 ` Philipp Stephani
2021-05-03 19:07 ` Eli Zaretskii
2021-05-03 19:21 ` Eric Abrahamsen
2021-05-03 21:29 ` Arash Esbati
2021-05-03 19:21 ` Eric Abrahamsen
2021-05-03 19:25 ` Eli Zaretskii
2021-05-03 19:49 ` Alan Third
2021-05-03 20:07 ` Andreas Schwab
2021-05-03 20:34 ` Eric Abrahamsen [this message]
2021-05-03 23:04 ` Alan Third
2021-05-04 11:40 ` Eli Zaretskii
2021-05-04 18:40 ` Eli Zaretskii
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=87y2cvsgid.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=alan@idiocy.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=p.stephani2@gmail.com \
--cc=schwab@linux-m68k.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).