From: Jan Nieuwenhuizen <janneke@gnu.org>
To: Carl Dong <contact@carldong.me>
Cc: 45165@debbugs.gnu.org
Subject: bug#45165: binutils-mesboot0 fails at configure, cannot find lex
Date: Fri, 11 Dec 2020 07:33:36 +0100 [thread overview]
Message-ID: <87a6ukkg1r.fsf@gnu.org> (raw)
In-Reply-To: <3FFC3D46-B961-479D-BCA9-273C150BF9CC@carldong.me> (Carl Dong's message of "Thu, 10 Dec 2020 17:28:37 -0500")
Carl Dong writes:
Hello!
> Some more information from my debugging:
>
> 1. This error is reproducible even when I specify --cores=1, which is very strange
> 2. I have attached the full log to this email
Diffing this with the build log from
--8<---------------cut here---------------start------------->8---
guix build -e '(@@ (gnu packages commencement) binutils-mesboot0)' --log-file
wget https://ci.guix.gnu.org/log/jfa9b78rdniyw7qilsmw3bh02x8x68ly-binutils-mesboot0-2.14 -O jfa9b78rdniyw7qilsmw3bh02x8x68ly-binutils-mesboot0-2.14.gz
gunzip jfa9b78rdniyw7qilsmw3bh02x8x68ly-binutils-mesboot0-2.14.gz
diff -u jfa9b78rdniyw7qilsmw3bh02x8x68ly-binutils-mesboot0-2.14 2020-10-10-binutils-mesboot0.log
[..]
@@ -5538,16 +5537,16 @@
checking for i386-unknown-linux-windres... no
checking for windres... windres
checking whether to enable maintainer-specific portions of Makefiles... no
-updating cache ./config.cache
+not updating unwritable cache ./config.cache
creating ./config.status
creating Makefile
[..]
@@ -5558,7 +5557,7 @@
checking whether the C compiler (tcc -D __GLIBC_MINOR__=6 -g ) works... yes
checking whether the C compiler (tcc -D __GLIBC_MINOR__=6 -g ) is a cross-compiler... no
checking whether we are using GNU C... no
-checking for ranlib... (cached) true
+checking for ranlib... true
checking for POSIXized ISC... no
checking for ANSI C header files... yes
checking for working const... yes
--8<---------------cut here---------------end--------------->8---
config values do not get cached (why is config.cache
unwritable?)...which seems to lead to a misdectected presence of lex:
--8<---------------cut here---------------start------------->8---
-@ build-succeeded /gnu/store/bz6xjpzlwf57m4bg3w5ihlq638sscx54-binutils-mesboot0-2.14.drv -
-checking for flex... (cached) /tmp/guix-build-binutils-mesboot0-2.14.drv-0/binutils-2.14/missing flex
-checking for flex... (cached) /tmp/guix-build-binutils-mesboot0-2.14.drv-0/binutils-2.14/missing flex
-checking for yywrap in -ll... (cached) no
-checking lex output file root... (cached) lex.yy
[..]
+checking for flex... no
+checking for lex... no
+./configure: line 4417: flex: command not found
+checking for flex... lex
+checking for yywrap in -ll... no
+checking lex output file root... ./configure: line 4505: lex: command not found
+configure: error: cannot find output from lex; giving up
+make: *** [configure-ld] Error 1
--8<---------------cut here---------------end--------------->8---
What is your build environment/version of guix you're using? It looks
like some unreproducible bit is leaking in somewhere??
Greetings,
Janneke
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
next prev parent reply other threads:[~2020-12-11 6:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-10 20:01 bug#45165: binutils-mesboot0 fails at configure, cannot find lex Carl Dong
2020-12-10 22:28 ` Carl Dong
2020-12-11 6:33 ` Jan Nieuwenhuizen [this message]
2020-12-11 16:37 ` Carl Dong
2020-12-15 18:50 ` Carl Dong
2020-12-16 0:46 ` Carl Dong
2020-12-16 17:49 ` Carl Dong
2020-12-22 14:33 ` Ludovic Courtès
2020-12-22 16:42 ` Carl Dong
2021-01-18 22:48 ` Carl Dong
2021-01-19 23:03 ` Carl Dong
2021-02-03 19:18 ` Carl Dong
2021-02-06 21:04 ` Ludovic Courtès
2020-12-25 15:57 ` Tom Hiller
2021-02-27 10:33 ` Vincent Legoll
2021-06-09 13:36 ` kitzman via Bug reports for GNU Guix
2021-06-09 15:12 ` kitzman via Bug reports for GNU Guix
2021-12-24 5:58 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-12-24 8:11 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2022-02-24 13:09 ` kitzman via Bug reports for GNU Guix
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a6ukkg1r.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=45165@debbugs.gnu.org \
--cc=contact@carldong.me \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.