For a little while now I've had two files that seem to be updated when I run make, and then git tells me have been modified: build-aux/config.guess build-aux/config.sub I've just been resetting as and when required, but they always come back after a build. I only see this on my mac, I don't see it on a Debian system. Is there something I should be doing with them? -- Alan Third
Am Mo., 3. Mai 2021 um 19:53 Uhr schrieb Alan Third <alan@idiocy.org>:
>
> For a little while now I've had two files that seem to be updated when
> I run make, and then git tells me have been modified:
>
> build-aux/config.guess
> build-aux/config.sub
>
> I've just been resetting as and when required, but they always come
> back after a build. I only see this on my mac, I don't see it on a
> Debian system. Is there something I should be doing with them?
FWIW, I see the same behavior.
> From: Philipp Stephani <p.stephani2@gmail.com>
> Date: Mon, 3 May 2021 20:36:55 +0200
>
> Am Mo., 3. Mai 2021 um 19:53 Uhr schrieb Alan Third <alan@idiocy.org>:
> >
> > For a little while now I've had two files that seem to be updated when
> > I run make, and then git tells me have been modified:
> >
> > build-aux/config.guess
> > build-aux/config.sub
> >
> > I've just been resetting as and when required, but they always come
> > back after a build. I only see this on my mac, I don't see it on a
> > Debian system. Is there something I should be doing with them?
>
> FWIW, I see the same behavior.
FWIW, I don't. Strange.
Am Mo., 3. Mai 2021 um 20:56 Uhr schrieb Eli Zaretskii <eliz@gnu.org>:
>
> > From: Philipp Stephani <p.stephani2@gmail.com>
> > Date: Mon, 3 May 2021 20:36:55 +0200
> >
> > Am Mo., 3. Mai 2021 um 19:53 Uhr schrieb Alan Third <alan@idiocy.org>:
> > >
> > > For a little while now I've had two files that seem to be updated when
> > > I run make, and then git tells me have been modified:
> > >
> > > build-aux/config.guess
> > > build-aux/config.sub
> > >
> > > I've just been resetting as and when required, but they always come
> > > back after a build. I only see this on my mac, I don't see it on a
> > > Debian system. Is there something I should be doing with them?
> >
> > FWIW, I see the same behavior.
>
> FWIW, I don't. Strange.
This only happens on macOS.
> From: Philipp Stephani <p.stephani2@gmail.com>
> Date: Mon, 3 May 2021 21:04:55 +0200
> Cc: Alan Third <alan@idiocy.org>, Emacs developers <emacs-devel@gnu.org>
>
> > > > build-aux/config.guess
> > > > build-aux/config.sub
> > > >
> > > > I've just been resetting as and when required, but they always come
> > > > back after a build. I only see this on my mac, I don't see it on a
> > > > Debian system. Is there something I should be doing with them?
> > >
> > > FWIW, I see the same behavior.
> >
> > FWIW, I don't. Strange.
>
> This only happens on macOS.
A Git-on-macOS bug?
Philipp Stephani <p.stephani2@gmail.com> writes:
> Am Mo., 3. Mai 2021 um 20:56 Uhr schrieb Eli Zaretskii <eliz@gnu.org>:
>>
>> > From: Philipp Stephani <p.stephani2@gmail.com>
>> > Date: Mon, 3 May 2021 20:36:55 +0200
>> >
>> > Am Mo., 3. Mai 2021 um 19:53 Uhr schrieb Alan Third <alan@idiocy.org>:
>> > >
>> > > For a little while now I've had two files that seem to be updated when
>> > > I run make, and then git tells me have been modified:
>> > >
>> > > build-aux/config.guess
>> > > build-aux/config.sub
>> > >
>> > > I've just been resetting as and when required, but they always come
>> > > back after a build. I only see this on my mac, I don't see it on a
>> > > Debian system. Is there something I should be doing with them?
>> >
>> > FWIW, I see the same behavior.
>>
>> FWIW, I don't. Strange.
>
> This only happens on macOS.
Happens on Arch Linux, too!
Philipp Stephani <p.stephani2@gmail.com> writes:
> Am Mo., 3. Mai 2021 um 20:56 Uhr schrieb Eli Zaretskii <eliz@gnu.org>:
>>
>> > From: Philipp Stephani <p.stephani2@gmail.com>
>> > Date: Mon, 3 May 2021 20:36:55 +0200
>> >
>> > Am Mo., 3. Mai 2021 um 19:53 Uhr schrieb Alan Third <alan@idiocy.org>:
>> > >
>> > > For a little while now I've had two files that seem to be updated when
>> > > I run make, and then git tells me have been modified:
>> > >
>> > > build-aux/config.guess
>> > > build-aux/config.sub
>> > >
>> > > I've just been resetting as and when required, but they always come
>> > > back after a build. I only see this on my mac, I don't see it on a
>> > > Debian system. Is there something I should be doing with them?
>> >
>> > FWIW, I see the same behavior.
>>
>> FWIW, I don't. Strange.
>
> This only happens on macOS.
Happens on Arch Linux, too!
> From: Eric Abrahamsen <eric@ericabrahamsen.net>
> Cc: Eli Zaretskii <eliz@gnu.org>, Alan Third <alan@idiocy.org>, Emacs
> developers <emacs-devel@gnu.org>
> Date: Mon, 03 May 2021 12:21:54 -0700
>
> >> > > build-aux/config.guess
> >> > > build-aux/config.sub
> >> > >
> >> > > I've just been resetting as and when required, but they always come
> >> > > back after a build. I only see this on my mac, I don't see it on a
> >> > > Debian system. Is there something I should be doing with them?
> >> >
> >> > FWIW, I see the same behavior.
> >>
> >> FWIW, I don't. Strange.
> >
> > This only happens on macOS.
>
> Happens on Arch Linux, too!
Now it's really strange.
What kind of changes does Git report in these two files? Attributes,
perhaps?
On Mon, May 03, 2021 at 10:25:35PM +0300, Eli Zaretskii wrote:
> > From: Eric Abrahamsen <eric@ericabrahamsen.net>
> > Cc: Eli Zaretskii <eliz@gnu.org>, Alan Third <alan@idiocy.org>, Emacs
> > developers <emacs-devel@gnu.org>
> > Date: Mon, 03 May 2021 12:21:54 -0700
> >
> > >> > > build-aux/config.guess
> > >> > > build-aux/config.sub
> > >> > >
>
> What kind of changes does Git report in these two files? Attributes,
> perhaps?
It looks like it may require a run of autogen.sh to generate the
changes. I was sure before that just running plain "make" was enough,
but perhaps not.
I see these changes:
modified build-aux/config.guess
@@ -2,7 +2,7 @@
# Attempt to guess a canonical system name.
# Copyright 1992-2021 Free Software Foundation, Inc.
-timestamp='2021-01-01'
+timestamp='2021-01-25'
# This file is free software; you can redistribute it and/or modify it
# under the terms of the GNU General Public License as published by
@@ -188,10 +188,9 @@ UNAME_VERSION=
#
# Note: NetBSD doesn't particularly care about the vendor
# portion of the name. We always set it to "unknown".
- sysctl="sysctl -n hw.machine_arch"
UNAME_MACHINE_ARCH=$( (uname -p 2>/dev/null || \
- "/sbin/$sysctl" 2>/dev/null || \
- "/usr/sbin/$sysctl" 2>/dev/null || \
+ /sbin/sysctl -n hw.machine_arch 2>/dev/null || \
+ /usr/sbin/sysctl -n hw.machine_arch 2>/dev/null || \
echo unknown))
case "$UNAME_MACHINE_ARCH" in
aarch64eb) machine=aarch64_be-unknown ;;
@@ -1483,8 +1482,8 @@ main ()
i*86:rdos:*:*)
echo "$UNAME_MACHINE"-pc-rdos
exit ;;
- i*86:AROS:*:*)
- echo "$UNAME_MACHINE"-pc-aros
+ *:AROS:*:*)
+ echo "$UNAME_MACHINE"-unknown-aros
exit ;;
x86_64:VMkernel:*:*)
echo "$UNAME_MACHINE"-unknown-esx
modified build-aux/config.sub
@@ -2,7 +2,7 @@
# Configuration validation subroutine script.
# Copyright 1992-2021 Free Software Foundation, Inc.
-timestamp='2021-01-07'
+timestamp='2021-01-08'
# This file is free software; you can redistribute it and/or modify it
# under the terms of the GNU General Public License as published by
@@ -1683,12 +1683,15 @@ kernel=
# Now, validate our (potentially fixed-up) OS.
case $os in
- # Sometimes we do "kernel-abi", so those need to count as OSes.
+ # Sometimes we do "kernel-libc", so those need to count as OSes.
musl* | newlib* | uclibc*)
;;
- # Likewise for "kernel-libc"
+ # Likewise for "kernel-abi"
eabi* | gnueabi*)
;;
+ # VxWorks passes extra cpu info in the 4th filed.
+ simlinux | simwindows | spe)
+ ;;
# Now accept the basic system types.
# The portable systems comes first.
# Each alternative MUST end in a * to match a version number.
@@ -1751,6 +1754,8 @@ kernel=
;;
kfreebsd*-gnu* | kopensolaris*-gnu*)
;;
+ vxworks-simlinux | vxworks-simwindows | vxworks-spe)
+ ;;
nto-qnx*)
;;
os2-emx)
--
Alan Third
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.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
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
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> Philipp Stephani <p.stephani2@gmail.com> writes:
>
>> Am Mo., 3. Mai 2021 um 20:56 Uhr schrieb Eli Zaretskii <eliz@gnu.org>:
>>>
>>> > From: Philipp Stephani <p.stephani2@gmail.com>
>>> > Date: Mon, 3 May 2021 20:36:55 +0200
>>> >
>>> > Am Mo., 3. Mai 2021 um 19:53 Uhr schrieb Alan Third <alan@idiocy.org>:
>>> > >
>>> > > For a little while now I've had two files that seem to be updated when
>>> > > I run make, and then git tells me have been modified:
>>> > >
>>> > > build-aux/config.guess
>>> > > build-aux/config.sub
>>> > >
>>> > > I've just been resetting as and when required, but they always come
>>> > > back after a build. I only see this on my mac, I don't see it on a
>>> > > Debian system. Is there something I should be doing with them?
>>> >
>>> > FWIW, I see the same behavior.
>>>
>>> FWIW, I don't. Strange.
>>
>> This only happens on macOS.
>
> Happens on Arch Linux, too!
Happens on Win10 with MSYS2, too.
Best, Arash
On Mon, May 03, 2021 at 10:07:22PM +0200, Andreas Schwab wrote:
> 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.
Looks like it's autoreconf in autogen.sh:258. If I run
autoreconf -fi -I m4
it updates the two files. I'm using autoconf 2.71.
--
Alan Third
> Date: Tue, 4 May 2021 00:04:17 +0100
> From: Alan Third <alan@idiocy.org>
> Cc: Eric Abrahamsen <eric@ericabrahamsen.net>, Eli Zaretskii <eliz@gnu.org>,
> p.stephani2@gmail.com, emacs-devel@gnu.org
>
> Looks like it's autoreconf in autogen.sh:258. If I run
>
> autoreconf -fi -I m4
>
> it updates the two files. I'm using autoconf 2.71.
So I guess we need to look for autoreconf switches that prevent it
from updating these files, and use them in our builds?
> Date: Tue, 04 May 2021 14:40:07 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: eric@ericabrahamsen.net, p.stephani2@gmail.com, schwab@linux-m68k.org,
> emacs-devel@gnu.org
>
> > Looks like it's autoreconf in autogen.sh:258. If I run
> >
> > autoreconf -fi -I m4
> >
> > it updates the two files. I'm using autoconf 2.71.
>
> So I guess we need to look for autoreconf switches that prevent it
> from updating these files, and use them in our builds?
I don't see such switches. It looks like this is a "feature", and
cannot be turned off. It is triggered by the -f command-line option.
Unless we can do without -f, someone should talk to Autoconf
developers and ask them for a workaround.
Alternatively, downgrade to an older Autoconf.