* bug#62482: Acknowledgement (Unclear configure errors about "gl_PROG_CC_C99" and "gl_EARLY")
2023-03-27 8:55 bug#62482: Unclear configure errors about "gl_PROG_CC_C99" and "gl_EARLY" c.buhtz
@ 2023-03-27 13:15 ` GNU bug Tracking System
2023-03-30 6:18 ` Jean Louis
2023-03-27 13:23 ` bug#62482: Unclear configure errors about "gl_PROG_CC_C99" and "gl_EARLY" Andreas Schwab
` (3 subsequent siblings)
4 siblings, 1 reply; 8+ messages in thread
From: GNU bug Tracking System @ 2023-03-27 13:15 UTC (permalink / raw)
To: bug-gnu-emacs
Thank you for filing a new bug report with debbugs.gnu.org.
This is an automatically generated reply to let you know your message
has been received.
Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.
Your message has been sent to the package maintainer(s):
bug-gnu-emacs@gnu.org
If you wish to submit further information on this problem, please
send it to 62482@debbugs.gnu.org.
Please do not send mail to help-debbugs@gnu.org unless you wish
to report a problem with the Bug-tracking system.
--
62482: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=62482
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
^ permalink raw reply [flat|nested] 8+ messages in thread* bug#62482: Unclear configure errors about "gl_PROG_CC_C99" and "gl_EARLY"
2023-03-27 8:55 bug#62482: Unclear configure errors about "gl_PROG_CC_C99" and "gl_EARLY" c.buhtz
2023-03-27 13:15 ` bug#62482: Acknowledgement (Unclear configure errors about "gl_PROG_CC_C99" and "gl_EARLY") GNU bug Tracking System
@ 2023-03-27 13:23 ` Andreas Schwab
2023-03-27 13:25 ` Gregory Heytings
` (2 subsequent siblings)
4 siblings, 0 replies; 8+ messages in thread
From: Andreas Schwab @ 2023-03-27 13:23 UTC (permalink / raw)
To: c.buhtz; +Cc: 62482
Please read INSTALL.REPO.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
^ permalink raw reply [flat|nested] 8+ messages in thread* bug#62482: Unclear configure errors about "gl_PROG_CC_C99" and "gl_EARLY"
2023-03-27 8:55 bug#62482: Unclear configure errors about "gl_PROG_CC_C99" and "gl_EARLY" c.buhtz
2023-03-27 13:15 ` bug#62482: Acknowledgement (Unclear configure errors about "gl_PROG_CC_C99" and "gl_EARLY") GNU bug Tracking System
2023-03-27 13:23 ` bug#62482: Unclear configure errors about "gl_PROG_CC_C99" and "gl_EARLY" Andreas Schwab
@ 2023-03-27 13:25 ` Gregory Heytings
2023-03-27 13:54 ` Eli Zaretskii
2023-09-03 10:38 ` bug#62482: closed (Re: bug#62482: Unclear configure errors about "gl_PROG_CC_C99" and "gl_EARLY") GNU bug Tracking System
4 siblings, 0 replies; 8+ messages in thread
From: Gregory Heytings @ 2023-03-27 13:25 UTC (permalink / raw)
To: c.buhtz; +Cc: 62482
>
> I have this two errors (?) running "configure". It is unclear what they
> are mean. Even if I look into the "configure" script the meaning is
> unclear to me.
>
> ./configure: line 5063: gl_PROG_CC_C99: command not found
> ./configure: line 5196: gl_EARLY: command not found
>
Do you see these errors if you use "./autogen.sh", as explained in the
INSTALL.REPO file?
^ permalink raw reply [flat|nested] 8+ messages in thread
* bug#62482: Unclear configure errors about "gl_PROG_CC_C99" and "gl_EARLY"
2023-03-27 8:55 bug#62482: Unclear configure errors about "gl_PROG_CC_C99" and "gl_EARLY" c.buhtz
` (2 preceding siblings ...)
2023-03-27 13:25 ` Gregory Heytings
@ 2023-03-27 13:54 ` Eli Zaretskii
2023-09-03 10:37 ` Stefan Kangas
2023-09-03 10:38 ` bug#62482: closed (Re: bug#62482: Unclear configure errors about "gl_PROG_CC_C99" and "gl_EARLY") GNU bug Tracking System
4 siblings, 1 reply; 8+ messages in thread
From: Eli Zaretskii @ 2023-03-27 13:54 UTC (permalink / raw)
To: 62482
tags 62482 notabug
thanks
> Date: Mon, 27 Mar 2023 08:55:14 +0000
> From: c.buhtz@posteo.jp
>
> Hello,
>
> beside I'm interested into how to solve that problem (what is IMHO
> off-topic on that list) this message main intention is a bug report to
> improve the output of a configure script.
>
> I have this two errors (?) running "configure". It is unclear what they
> are mean. Even if I look into the "configure" script the meaning is
> unclear to me.
>
> ./configure: line 5063: gl_PROG_CC_C99: command not found
> ./configure: line 5196: gl_EARLY: command not found
>
> Please improve the output of the script to make it easier to understand
> it for the users, to prevent further support questions and lower the
> workload for emacs "support channels".
>
> To reproduce:
>
> I cloned from git and switch to "emacs-29" branch. The machine is a
> Raspberry Pi4 with Debian 11 (pure Debian, not rasbian).
>
> Because the configure script is missing (bug-report exists) I checked
> the content of "configure.ac". It points out to use "autoconf" to
> generate such a script. I did.
>
> $ autoconf
> configure.ac:55: error: possibly undefined macro: AS_ECHO
> If this token and others are legitimate, please use
> m4_pattern_allow.
> See the Autoconf documentation.
> configure.ac:1777: error: possibly undefined macro: m4_default
Please read INSTALL.REPO, which tells you to run ./autogen.sh script
instead. Then such errors ought not to happen.
^ permalink raw reply [flat|nested] 8+ messages in thread* bug#62482: closed (Re: bug#62482: Unclear configure errors about "gl_PROG_CC_C99" and "gl_EARLY")
2023-03-27 8:55 bug#62482: Unclear configure errors about "gl_PROG_CC_C99" and "gl_EARLY" c.buhtz
` (3 preceding siblings ...)
2023-03-27 13:54 ` Eli Zaretskii
@ 2023-09-03 10:38 ` GNU bug Tracking System
4 siblings, 0 replies; 8+ messages in thread
From: GNU bug Tracking System @ 2023-09-03 10:38 UTC (permalink / raw)
To: bug-gnu-emacs
[-- Attachment #1: Type: text/plain, Size: 430 bytes --]
Your bug report
#62482: Unclear configure errors about "gl_PROG_CC_C99" and "gl_EARLY"
which was filed against the emacs package, has been closed.
The explanation is attached below, along with your original report.
If you require more details, please reply to 62482@debbugs.gnu.org.
--
62482: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=62482
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
[-- Attachment #2: Type: message/rfc822, Size: 4203 bytes --]
From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 62482-done@debbugs.gnu.org
Subject: Re: bug#62482: Unclear configure errors about "gl_PROG_CC_C99" and "gl_EARLY"
Date: Sun, 3 Sep 2023 03:37:38 -0700
Message-ID: <CADwFkmn1sn9DCXFoRJ9BYtYgUr5jhUumjoJYtHTFQ8MggPLfow@mail.gmail.com>
Eli Zaretskii <eliz@gnu.org> writes:
> tags 62482 notabug
> thanks
[...]
>
> Please read INSTALL.REPO, which tells you to run ./autogen.sh script
> instead. Then such errors ought not to happen.
I'm therefore closing this bug report.
[-- Attachment #3: Type: message/rfc822, Size: 6002 bytes --]
From: c.buhtz@posteo.jp
To: bug-gnu-emacs@gnu.org
Subject: Unclear configure errors about "gl_PROG_CC_C99" and "gl_EARLY"
Date: Mon, 27 Mar 2023 08:55:14 +0000
Message-ID: <a965dd44a1889318c1d4def51b8a0e35@posteo.de>
Hello,
beside I'm interested into how to solve that problem (what is IMHO
off-topic on that list) this message main intention is a bug report to
improve the output of a configure script.
I have this two errors (?) running "configure". It is unclear what they
are mean. Even if I look into the "configure" script the meaning is
unclear to me.
./configure: line 5063: gl_PROG_CC_C99: command not found
./configure: line 5196: gl_EARLY: command not found
Please improve the output of the script to make it easier to understand
it for the users, to prevent further support questions and lower the
workload for emacs "support channels".
To reproduce:
I cloned from git and switch to "emacs-29" branch. The machine is a
Raspberry Pi4 with Debian 11 (pure Debian, not rasbian).
Because the configure script is missing (bug-report exists) I checked
the content of "configure.ac". It points out to use "autoconf" to
generate such a script. I did.
$ autoconf
configure.ac:55: error: possibly undefined macro: AS_ECHO
If this token and others are legitimate, please use
m4_pattern_allow.
See the Autoconf documentation.
configure.ac:1777: error: possibly undefined macro: m4_default
Two errors are there. I don't understand. But a "./configure" was
created. So I tried.
$ ./configure
checking for xcrun... no
checking for GNU Make... make
checking build system type... aarch64-unknown-linux-gnu
checking host system type... aarch64-unknown-linux-gnu
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
./configure: line 5063: gl_PROG_CC_C99: command not found
checking whether gcc and cc understand -c and -o together... yes
./configure: line 5196: gl_EARLY: command not found
checking whether gcc accepts -g3 -O2... yes
checking whether the compiler is clang... no
checking how to run the C preprocessor... gcc -E
./configure: line 5555: syntax error near unexpected token `-Wno-switch'
./configure: line 5555: ` gl_WARN_ADD(-Wno-switch)'
^ permalink raw reply [flat|nested] 8+ messages in thread