From: Marcus Folkesson <marcus.folkesson@gmail.com>
To: Julien Olivain <ju.o@free.fr>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v3] package/criu: new package
Date: Mon, 9 Oct 2023 10:29:40 +0200 [thread overview]
Message-ID: <ZSO59B783UDZGL1m@gmail.com> (raw)
In-Reply-To: <0d205f8ab83f4f387912227cbb95238c@free.fr>
[-- Attachment #1.1: Type: text/plain, Size: 2389 bytes --]
Hi Julian,
On Fri, Oct 06, 2023 at 10:35:14PM +0200, Julien Olivain wrote:
> Hi Marcus,
>
> On 06/10/2023 13:46, Marcus Folkesson wrote:
> > Julien, do you have the posibility to run test-pkg on this patch?
> >
> > I still get wierd errors (related to host-libzlib (?) ) for the
> > bootlin-armv7-glibc toolchain.
>
> I ran a test-pkg on this v3 patch. I am not able to reproduce this
> host-libzlib failure (both on my host system and in the reference
> utils/docker-run Docker image). But I do see a build failure with
> the bootlin-armv7-glibc toolchain in the criu package:
>
> cat > criu.config <<EOF
> BR2_PACKAGE_HOST_PYTHON3=y
> BR2_PACKAGE_CRIU=y
> EOF
>
> utils/test-pkg -c criu.config -p criu
> bootlin-armv5-uclibc [1/6]: SKIPPED
> bootlin-armv7-glibc [2/6]: FAILED
> bootlin-armv7m-uclibc [3/6]: SKIPPED
> bootlin-x86-64-musl [4/6]: OK
> br-arm-full-static [5/6]: SKIPPED
> sourcery-arm [6/6]: SKIPPED
> 6 builds, 4 skipped, 1 build failed, 0 legal-info failed, 0 show-info
> failed
>
> It fails with output:
>
> /home/br-user/br-test-pkg/bootlin-armv7-glibc/host/bin/arm-linux-ld:
> ./compel/plugins/std.lib.a(string.o): in function `std_vdprintf':
> string.c:(.text+0x114): undefined reference to `__aeabi_idivmod'
>
> Maybe the SUBARCH make variable need to be set for Arm, because the
> criu Makefile adjust few flags based on its value. See [1].
Thank you for testing, it is highly appreciated.
I will try to build using the docker image as I'm only getting problem
with host-libzlib, even for a clean build.
I will add this for the next patch version
ifeq ($(BR2_ARM_CPU_ARMV6), y)
CRIU_MAKE_ENV += SUBARCH=armv6
else ifeq ($(BR2_ARM_CPU_ARMV7A), y)
CRIU_MAKE_ENV += SUBARCH=armv7
else ifeq ($(BR2_ARM_CPU_ARMV7M), y)
CRIU_MAKE_ENV += SUBARCH=armv7
else ifeq ($(BR2_ARM_CPU_ARMV8A), y)
CRIU_MAKE_ENV += SUBARCH=armv8
else ifeq ($(BR2_ARM_CPU_ARMV8M), y)
CRIU_MAKE_ENV += SUBARCH=armv8
endif
But the Makefile defaults to armv7, so I do not think it make any
difference for bootlin-armv7-glibc.
>
> >
> > bootlin-x86-64-musl is 'OK' though.
> >
> > Thanks,
> > Marcus
>
> Best regards,
>
> Julien.
>
> [1] https://github.com/checkpoint-restore/criu/blob/v3.18/Makefile#L35
/Marcus
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 150 bytes --]
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-10-09 8:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 8:48 [Buildroot] [PATCH v3] package/criu: new package Marcus Folkesson
2023-10-06 11:46 ` Marcus Folkesson
2023-10-06 20:35 ` Julien Olivain
2023-10-09 8:29 ` Marcus Folkesson [this message]
2023-10-06 20:52 ` Julien Olivain
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=ZSO59B783UDZGL1m@gmail.com \
--to=marcus.folkesson@gmail.com \
--cc=buildroot@buildroot.org \
--cc=ju.o@free.fr \
--cc=thomas.petazzoni@bootlin.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox