On Fri, 2021-11-12 at 09:41 +0100, Lukasz Majewski wrote:
> Hi Khem,
> 
> > seeing this
> > 
> > https://errors.yoctoproject.org/Errors/Details/616955/
> 
> The error is about autoconf version:
> 
> DEBUG: Executing shell function do_configure
> aclocal.m4:6: error: Exactly version 2.69 of Autoconf is required but
> you have 2.71
> 
> aclocal.m4:6: the top level
> autom4te: error: m4 failed with exit status: 63
> 
> This is strange, as on my setup (qemuarm, qemuarm64, qemux86) the glibc
> and glibc-tests are built without any issues with autoconf version 2.71.
> 
> 
> I've built the glibc-tests without issues with:
> 
> Build Configuration:
> BB_VERSION           = "1.52.0"
> BUILD_SYS            = "x86_64-linux"
> NATIVELSBSTRING      = "universal"
> TARGET_SYS           = "riscv64-poky-linux"
> MACHINE              = "qemuriscv64"
> DISTRO               = "poky"
> DISTRO_VERSION       = "3.4"
> TUNE_FEATURES        = "riscv64"
> meta
> meta-poky
> meta-yocto-bsp       =
> "glibc-ptest_v4:164923f0586ac189f01938a32fa102c2df7cc447"
> 
> DISTRO=poky MACHINE=qemuriscv64 bitbake glibc-tests
> 
> 
> Khem, could you help me with setting up environment to reproduce this
> issue?

The autoconf version message isn't a fatal error and if you look at your own
build logs you probably have that too. What looks like it is the issue is:

checking if riscv64-yoe-linux-clang -target riscv64-yoe-linux    
-mlittle-endian -mno-relax -Qunused-arguments -fstack-protector-strong  -O2 
-D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security 
--sysroot=TOPDIR/build/tmp/work/riscv64-yoe-linux/glibc-tests/2.34-r0/recipe-sysroot
 is sufficient to build libc... no

which I think leads to:

configure: error: 
*** These critical programs are missing or too old: compiler

Khem was implying this was a musl build, I can't see that from the logs but if
it is a musl build, it shouldn't be building glibc tests.

For that reason I did add:

http://git.yoctoproject.org/cgit.cgi/poky/commit/?h=master-next&id=f54774199ef09b655de1b586045995e0f284925a

to master-next since I believe that was the remaining issue blocking the patch
apart from a typo Khem also mentioned which I meant to find and tweak.

I still am concerned about having duplication of tests but I don't see any way
around that since you want to get this patch merged and I don't have any
solution for that.

Cheers,

Richard


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#158212): 
https://lists.openembedded.org/g/openembedded-core/message/158212
Mute This Topic: https://lists.openembedded.org/mt/86933618/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to