Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Waldemar Brodkorb <wbx@openadk.org>
Cc: buildroot@buildroot.org, Dmitriy Chestnykh <dm.chestnykh@gmail.com>
Subject: Re: [Buildroot] [PATCH] package/uclibc: Fix ARC build with 4.x kernel headers
Date: Tue, 30 Jul 2024 22:16:30 +0200	[thread overview]
Message-ID: <20240730221630.7595f673@windsurf> (raw)
In-Reply-To: <Zqcf31ivOCwqs+01@waldemar-brodkorb.de>

Hello Waldemar,

On Mon, 29 Jul 2024 06:51:43 +0200
Waldemar Brodkorb <wbx@openadk.org> wrote:

> That is strange. I cloned buildroot-toolchains, 
> make qemu_sh4_r2d_defconfig && make

Indeed, I agree as well.

> For me it works with the included Qemu 9.0.0.
> Strange thing is my zImage is smaller then the artefact which can be
> downloaded and did not work.
> 
> $ ls -l Downloads/zImage 
>   -rw-r--r-- 1 6037536 Jul 29 06:06 Downloads/zImage
> $ ls -l buildroot-toolchains/output/images/zImage 
>   -rw-r--r-- 1 4530208 Jul 29 05:57 buildroot-toolchains/output/images/zImage
> 
> Are the toolchain checks are running some tests inside the image?

You probably built "just" qemu_sh4_r2d_defconfig, but the toolchains we
built are more featureful: they have C++ support, Fortran support,
OpenMP support. This means additional GCC runtime libraries installed
in /lib, and therefore a bigger rootfs, which in the SH4 defconfigs is
built into zImage as an initramfs. So not too surprising to have a
bigger zImage.

The SH4 glibc stable toolchain is built using this configuration:

BR2_sh=y
BR2_TOOLCHAIN_BUILDROOT_GLIBC=y
BR2_PACKAGE_GLIBC_KERNEL_COMPAT=y
BR2_KERNEL_HEADERS_4_19=y
BR2_TOOLCHAIN_BUILDROOT_CXX=y
BR2_TOOLCHAIN_BUILDROOT_FORTRAN=y
BR2_INIT_NONE=y
BR2_SYSTEM_BIN_SH_NONE=y
# BR2_PACKAGE_BUSYBOX is not set
# BR2_TARGET_ROOTFS_TAR is not set
BR2_PACKAGE_HOST_GDB=y
BR2_PACKAGE_HOST_GDB_TUI=y
BR2_PACKAGE_HOST_GDB_PYTHON3=y
BR2_PACKAGE_GDB=y
BR2_GCC_ENABLE_OPENMP=y

So I am right building the concatenation of this +
qemu_sh4_r2d_defconfig to see what is the result.

Best regards,

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2024-07-30 20:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-28 11:58 [Buildroot] [PATCH] package/uclibc: Fix ARC build with 4.x kernel headers Dmitry Chestnykh
2024-07-28 16:00 ` Thomas Petazzoni via buildroot
2024-07-28 16:21   ` Dmitriy Chestnykh
2024-07-28 20:11     ` Thomas Petazzoni via buildroot
2024-07-29  4:00       ` Dmitriy Chestnykh
2024-07-29  4:38       ` Dmitriy Chestnykh
2024-07-30 20:17         ` Thomas Petazzoni via buildroot
2024-07-29  4:51       ` Waldemar Brodkorb
2024-07-29  5:00         ` Dmitriy Chestnykh
2024-07-30 20:16         ` Thomas Petazzoni via buildroot [this message]
2024-07-30 20:38           ` [Buildroot] [PATCH] SuperH qemu issues Thomas Petazzoni via buildroot
2024-08-03  6:34 ` [Buildroot] [PATCH] package/uclibc: Fix ARC build with 4.x kernel headers Waldemar Brodkorb
2024-08-12 19:27 ` Thomas Petazzoni via buildroot

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=20240730221630.7595f673@windsurf \
    --to=buildroot@buildroot.org \
    --cc=dm.chestnykh@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=wbx@openadk.org \
    /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