All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roberto Alejandro Espí Muñoz" <teratux@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] problems building a system for Rpi4
Date: Tue, 4 May 2021 14:02:01 -0400	[thread overview]
Message-ID: <CAG-SZaLq6drODUU+4+CatQjRBtH3OPDasUnEVHQtd8Kr3D8XpQ@mail.gmail.com> (raw)
In-Reply-To: <20210503210605.2b441f31@gmx.net>

That completely did the trick, thank you, system booted perfectly ?

On Mon, May 3, 2021 at 3:06 PM Peter Seiderer <ps.report@gmx.net> wrote:

> Hello Alejandro,
>
> On Mon, 3 May 2021 11:18:06 -0400, Roberto Alejandro Esp? Mu?oz <
> teratux at gmail.com> wrote:
>
> > Hello, I'm having some trouble getting my build to boot on a RPi4.  I
> > initially tried building the default config version for 64 bits
> > (raspberrypi4_64_defconfig) and it builds and boots ok with no problem.
> I
> > need to change the system to use glibc but whenever I manage to build the
> > system and boot it I get a kernel panic error: Attempted to kill init
> with
> > exitcode=0x00007f00.  The only change I'm making is switching over to a
> > glibc toolchain and so far no progress.
> >
> > I'm using buildroot buildroot-2020.11.3 and I attached my current config.
>
> Simple mismatch between toolchain headers:
>
> BR2_TOOLCHAIN_EXTERNAL_HEADERS_5_9=y
>
> and Linux-Kernel Version, here still 5.4.72...
>
> Can reproduce your problem with this combination (buildroot toolchain
> instead
> of external one), and can be fixed by simple changing the toolchain
> headers to 5.4.x (and complete re-build)...
>
> Regards,
> Peter
>
> >
> > Thanks in advance
> >
>
>

-- 
teratux
------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20210504/52ec879a/attachment.html>

      reply	other threads:[~2021-05-04 18:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-03 15:18 [Buildroot] problems building a system for Rpi4 Roberto Alejandro Espí Muñoz
2021-05-03 19:06 ` Peter Seiderer
2021-05-04 18:02   ` Roberto Alejandro Espí Muñoz [this message]

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=CAG-SZaLq6drODUU+4+CatQjRBtH3OPDasUnEVHQtd8Kr3D8XpQ@mail.gmail.com \
    --to=teratux@gmail.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.