Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Waldemar Brodkorb <wbx@openadk.org>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
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: Mon, 29 Jul 2024 06:51:43 +0200	[thread overview]
Message-ID: <Zqcf31ivOCwqs+01@waldemar-brodkorb.de> (raw)
In-Reply-To: <20240728221140.01aa7ed1@windsurf>

Hi,
Thomas Petazzoni wrote,

> Hello,
> 
> On Sun, 28 Jul 2024 19:21:20 +0300
> Dmitriy Chestnykh <dm.chestnykh@gmail.com> wrote:
> 
> > Hello Thomas
> > The SuperH4 issue has already been fixed by patch number 0002 (
> > https://gitlab.com/buildroot.org/buildroot/-/commit/f463a4953534df13397ce113bfbbc03d4b8e4df7
> > )
> 
> Indeed, thanks!
> 
> I still have an issue with SuperH 4 though.. it doesn't boot in Qemu:
> 
>   https://gitlab.com/buildroot.org/toolchains-builder/-/pipelines/1391146782

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

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?

best regards
 Waldemar
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2024-07-29  4:51 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 [this message]
2024-07-29  5:00         ` Dmitriy Chestnykh
2024-07-30 20:16         ` Thomas Petazzoni via buildroot
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=Zqcf31ivOCwqs+01@waldemar-brodkorb.de \
    --to=wbx@openadk.org \
    --cc=buildroot@buildroot.org \
    --cc=dm.chestnykh@gmail.com \
    --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