All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Olivain <ju.o@free.fr>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 3/4] package/gnu-efi: fix build due to short-wchar
Date: Sun, 19 Jan 2025 13:25:32 +0100	[thread overview]
Message-ID: <cdac8d91b8056cdcb045168e5b22e289@free.fr> (raw)
In-Reply-To: <20250119084511.2816892-4-thomas.petazzoni@bootlin.com>

On 19/01/2025 09:45, Thomas Petazzoni via buildroot wrote:
> The gnu-efi code base is so far built with -fshort-wchar:
> 
> ‘-fshort-wchar’
>      Override the underlying type for ‘wchar_t’ to be ‘short unsigned
>      int’ instead of the default for the target.  This option is useful
>      for building programs to run under WINE.
> 
>      *Warning:* the ‘-fshort-wchar’ switch causes GCC to generate code
>      that is not binary compatible with code generated without that
>      switch.  Use it to conform to a non-default application binary
>      interface.
> 
> However, this is highly incompatible with the definitions of wchar_t
> by musl, causing build issues:
> 
> /workdir/instance-0/output-1/build/gnu-efi-3.0.18//lib/console.c:84:68: 
> error: passing argument 2 of 'ConOut->OutputString' from incompatible 
> pointer type [-Werror=incompatible-pointer-types]
> [...]
> /workdir/instance-0/output-1/build/gnu-efi-3.0.18//lib/console.c:84:68: 
> note: expected 'CHAR16 *' {aka 'int *'} but argument is of type 'short 
> unsigned int *'
> 
> These have been addressed upstream by simply not using -fshort-wchar
> anymore, so we backport the relevant patches.
> 
> The patch 0003-Use-char16_t-literals.patch was directly backported, it
> was "redone" (it's a very mechanical patch) as backporting the patch
> and fixing the conflicts was more effort than redoing the patch from
> scratch. But in essence, it is the same patch as what is upstream.
> 
> Fixes:
> 
>   
> http://autobuild.buildroot.net/results/8b2f5b38284e70dde8c5619e5050e7f201a0bcc3/
> 
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>

Applied to master, thanks.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2025-01-19 12:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-19  8:45 [Buildroot] [PATCH 0/4] syslinux and gnu-efi fixes and update Thomas Petazzoni via buildroot
2025-01-19  8:45 ` [Buildroot] [PATCH 1/4] support/testing/tests/boot/test_syslinux: use newer toolchains Thomas Petazzoni via buildroot
2025-01-19 12:24   ` Julien Olivain
2025-01-19  8:45 ` [Buildroot] [PATCH 2/4] boot/syslinux: add multiple patches fixing build issues with GCC >= 14 Thomas Petazzoni via buildroot
2025-01-19 12:24   ` Julien Olivain
2025-01-31 16:43   ` Peter Korsgaard
2025-01-19  8:45 ` [Buildroot] [PATCH 3/4] package/gnu-efi: fix build due to short-wchar Thomas Petazzoni via buildroot
2025-01-19 12:25   ` Julien Olivain [this message]
2025-01-31 16:44   ` Peter Korsgaard
2025-01-19  8:45 ` [Buildroot] [PATCH 4/4] package/gnu-efi: change upstream, bump to 4.0.0 Thomas Petazzoni
2025-01-19 12:32   ` Julien Olivain
2025-01-19 12:36     ` 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=cdac8d91b8056cdcb045168e5b22e289@free.fr \
    --to=ju.o@free.fr \
    --cc=buildroot@buildroot.org \
    --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 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.