Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Build not bootable when build with Ubuntu 18.04
Date: Wed, 1 Aug 2018 18:57:18 +0200	[thread overview]
Message-ID: <20180801185718.74e1c7bd@windsurf> (raw)
In-Reply-To: <1533140393945.36133@stephan-gmbh.com>

Hello Jedrzej,

On Wed, 1 Aug 2018 16:19:55 +0000, Jedrzej Panek wrote:

> when I build my custom Linux on Ubuntu 16.04 and dd it on my cf-card, my device boots fine.
> Once I changed to Ubuntu 18.04 and did a full rebuild my embedded device cannot boot anymore (disk boot failure).
> I get no errors during the building process itself, and my desktop recognizes the card just fine. Did anyone experience similar issues?
> For me, it seems that the bootloader is failing.

Which bootloader are you using ?

The build process of grub2 and syslinux is a bit convoluted, and at
some point there were using the host (native) compiler to build stuff
for the target. From a quick look at grub2.mk and syslinux.mk, it
doesn't seem to be the case anymore though.

What you could try to do to investigate the problem is to take your
bootloader binaries from the build on Ubuntu 16.04 and put them with
the rest of the Buildroot built under Ubuntu 18.04, just to confirm
that the problem comes from the bootloader.

If you give a bit more details about your bootloader configuration, we
can try to reproduce.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

      reply	other threads:[~2018-08-01 16:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-01 16:19 [Buildroot] Build not bootable when build with Ubuntu 18.04 Jedrzej Panek
2018-08-01 16:57 ` Thomas Petazzoni [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=20180801185718.74e1c7bd@windsurf \
    --to=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox