All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Peter Seiderer <ps.report@gmx.net>
Cc: "Köry Maincent" <kory.maincent@bootlin.com>,
	"Walter, Stefan" <stefan.walter@iml.fraunhofer.de>,
	"buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] Boot process stuck at "GRUB loading.." since 2021.02.1
Date: Thu, 21 Oct 2021 19:59:01 +0200	[thread overview]
Message-ID: <20211021175901.GE2400@scaer> (raw)
In-Reply-To: <20211019230252.324bbb61@gmx.net>

Peter, Stefan, All,

+Köry who did some heavy works on grub2 recently...

On 2021-10-19 23:02 +0200, Peter Seiderer spake thusly:
> On Tue, 19 Oct 2021 15:17:23 +0000, "Walter, Stefan" <stefan.walter@iml.fraunhofer.de> wrote:
> The host-grub2 modules build can be fixed by the following patch:
> 
> --- a/boot/grub2/grub2.mk
> +++ b/boot/grub2/grub2.mk
> @@ -125,7 +125,9 @@ GRUB2_TUPLES-$(BR2_TARGET_GRUB2_ARM64_EFI) += arm64-efi
>  # use the cross compile variant to ensure grub2 builds
> 
>  HOST_GRUB2_CONF_ENV = \
> -       CPP="$(HOSTCC) -E"
> +       CPP="$(HOSTCC) -E" \
> +       CFLAGS="$(HOST_CFLAGS) -Os" \
> +       CPPFLAGS="$(HOST_CPPFLAGS) -Os"

Sure, but why do we even need to build the modules in the host version
to begin with?

We should probably build the host version with --with-platform=none I
think.

Yes, we do currently use cdboot.img from the host, but that is probably
a mistake and a remnant for long ago... Instead, I think we should only
used modules from the target build.

Regards,
Yann E. MORIN.

>  GRUB2_CONF_ENV = \
>         CPP="$(TARGET_CC) -E" \
> 
> Regards,
> Peter
> 
> >
> > Thank you for your help so far! I'll reference this in the issue at https://bugs.busybox.net/show_bug.cgi?id=14281.
> >
> > Best regards,
> > Stefan
> 
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2021-10-21 17:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-07 20:36 [Buildroot] Boot process stuck at "GRUB loading.." since 2021.02.1 Walter, Stefan
2021-10-07 21:50 ` Peter Seiderer
2021-10-08 14:27   ` Walter, Stefan
2021-10-08 17:25     ` Peter Seiderer
2021-10-11 12:23       ` Walter, Stefan
2021-10-11 17:29         ` Walter, Stefan
2021-10-18 22:22           ` Peter Seiderer
2021-10-19 15:17             ` Walter, Stefan
2021-10-19 21:02               ` Peter Seiderer
2021-10-21 17:59                 ` Yann E. MORIN [this message]
2021-10-22  9:48                   ` Köry Maincent
2021-10-22 17:42                     ` Peter Seiderer
2021-10-08 16:53 ` Alexander Dahl

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=20211021175901.GE2400@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@buildroot.org \
    --cc=kory.maincent@bootlin.com \
    --cc=ps.report@gmx.net \
    --cc=stefan.walter@iml.fraunhofer.de \
    /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.