* tricore-debian-cross-container CI job failing
@ 2023-01-12 14:13 Peter Maydell
2023-01-12 14:30 ` Peter Maydell
0 siblings, 1 reply; 2+ messages in thread
From: Peter Maydell @ 2023-01-12 14:13 UTC (permalink / raw)
To: QEMU Developers; +Cc: Alex Bennée, Bastian Koppelmann
The tricore-debian-cross-container CI job has started failing for
no obvious reason:
https://gitlab.com/qemu-project/qemu/-/jobs/3593581274
gcc -DHAVE_CONFIG_H -I. -I. -I. -D_GNU_SOURCE -I. -I. -I../bfd
-I./../bfd -I./../include -I./../intl -I../intl -w
-DLOCALEDIR="\"/usr/local/share/locale\"" -W -Wall -Wstrict-prototypes
-Wmissing-prototypes -w -c `test -f 'ldgram.c' || echo './'`ldgram.c
`test -f ldlex.l || echo './'`ldlex.l
/bin/sh: 1: ldlex.l: not found
I think this is happening because the makefile thinks it needs to
rebuild the ldlex.c file but doesn't know how to. In turn this
is probably because:
(a) we don't install flex or bison in the container that's doing
this binutils build
(b) the binutils sources we're building are confused, because they
have a 'missing' script that is not compatible with the 'configure',
and so configure warns:
/usr/src/binutils/missing: Unknown `--run' option
Try `/usr/src/binutils/missing --help' for more information
configure: WARNING: `missing' script is too old or missing
and then later in the build when it needs to do something to
handle the "I have no 'flex' or 'bison'" code path it fails
obscurely rather than being able to use the 'missing' script to
deal with it.
https://stackoverflow.com/questions/40962711/configure-warning-missing-script-is-too-old-or-missing
suggests that this can happen if some autotools stuff wasn't
done right or not all the files were checked into the repo.
I dunno how easy that is to fix. Perhaps installing flex
and bison in our container might be easiest.
thanks
-- PMM
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: tricore-debian-cross-container CI job failing
2023-01-12 14:13 tricore-debian-cross-container CI job failing Peter Maydell
@ 2023-01-12 14:30 ` Peter Maydell
0 siblings, 0 replies; 2+ messages in thread
From: Peter Maydell @ 2023-01-12 14:30 UTC (permalink / raw)
To: QEMU Developers; +Cc: Alex Bennée, Bastian Koppelmann
On Thu, 12 Jan 2023 at 14:13, Peter Maydell <peter.maydell@linaro.org> wrote:
>
> The tricore-debian-cross-container CI job has started failing for
> no obvious reason:
>
> https://gitlab.com/qemu-project/qemu/-/jobs/3593581274
>
> gcc -DHAVE_CONFIG_H -I. -I. -I. -D_GNU_SOURCE -I. -I. -I../bfd
> -I./../bfd -I./../include -I./../intl -I../intl -w
> -DLOCALEDIR="\"/usr/local/share/locale\"" -W -Wall -Wstrict-prototypes
> -Wmissing-prototypes -w -c `test -f 'ldgram.c' || echo './'`ldgram.c
> `test -f ldlex.l || echo './'`ldlex.l
> /bin/sh: 1: ldlex.l: not found
For comparison, here's another run of the same job, which
succeeded:
https://gitlab.com/qemu-project/qemu/-/jobs/3594096306
The difference is that in the success case Make doesn't think
it needs to rebuild ldlex.c or ldgram.c, but in the failure
case it does (and falls over because it can't). I don't know
why this is, maybe a random timestamp thing?
Anyway, to make the job reliable I think we need to have
flex and bison in the container.
thanks
-- PMM
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2023-01-12 15:10 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-01-12 14:13 tricore-debian-cross-container CI job failing Peter Maydell
2023-01-12 14:30 ` Peter Maydell
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 NNTP newsgroup(s).