platform-testers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [platform-testers] new snapshot available: autoconf-2.72c


From: Frederic Berat
Subject: Re: [platform-testers] new snapshot available: autoconf-2.72c
Date: Wed, 29 Mar 2023 19:21:33 +0200

Hi,

I'm done walking through the Fedora rebuilds, I get the following failures due to largefile.m4 which breaks with autoconf:

ImageMagick 1:7.1.1.4
emacs 1:28.2
grub2 2.06
gzip 1.12
libidn 1.41
libloc 0.9.16
make 4.4
parted 3.5
pspp 1.6.2
rcs 5.10.1

Indirectly: 'fatresize' (1.1.0) has a bug in its configuration file, which leads to a build failure with largefile support enabled.

Besides that, I didn't see anything critical.

On top of that, few failures due to malformed configuration files (some being already fixed upstream): krb5, am-utils

I need to have a closer look at 'kguitar', but there is likely a problem in the configure.in file too:
./configure: line 27629: syntax error near unexpected token `fi'
./configure: line 27629: `fi'

Fred.

On Tue, Mar 28, 2023 at 4:23 PM Richard Purdie <richard.purdie@linuxfoundation.org> wrote:
I was able to work around the EGREP_TRADITIONAL issue by reordering
macros. The issue is conditional code blocks which mean
EGREP_TRADITIONAL was not set in some configure option combinations
leading to obtuse failures.

Our testing so far shows the following three sets of issues.


Macro ordering issues with EGREP_TRADITIONAL being unset:

apr 1.7.2
libarchive 3.6.2


Ship with an older gnulib largefile.m4 which breaks with autoconf
2.72c:

parted 3.5
man-db 2.11.2
libpipeline 1.5.7
gzip 1.12
findutils 4.9.0
bison 3.8.2
gettext 0.21.1
coreutils 9.1
wget 1.21.3

On x32 were seeing two recipes which configure "ok" but fail at compile
time:

gpgme 1.18.0
mpg123 1.31.2

https://autobuilder.yoctoproject.org/typhoon/#/builders/57/builds/6771/steps/11/logs/stdio


Now that things are roughly building, we should get some better
automated runtime testing results in a few hours.

Cheers,

Richard


reply via email to

[Prev in Thread] Current Thread [Next in Thread]