public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Tony McKnight <tony.mcknight22@gmail.com>
To: "riscv/riscv-edk2-platforms"
	<reply+ABZF42IXEUZV7T36QXQPODN5SVJ5LEVBNHHCWCLQNA@reply.github.com>,
	 devel@edk2.groups.io
Subject: Re: [riscv/riscv-edk2-platforms] U540 Platform UEFI building failed (#10)
Date: Mon, 19 Oct 2020 12:34:41 +0800	[thread overview]
Message-ID: <CANrhGQDKidzLOrB54__7jBhPVfhcvr+E_+iw6TmETyiDu2r-sg@mail.gmail.com> (raw)
In-Reply-To: <riscv/riscv-edk2-platforms/issues/10/709958189@github.com>

[-- Attachment #1: Type: text/plain, Size: 2688 bytes --]

Hi,


Due to Daniel Schaefer's suggestion, I describe my case in details.
My case reproduction steps:
ENV:
Host: Ubuntu 20.04 but local $LANG is zh_CN.utf8
VM: Fedora RISCV Kernel 5.5 and local $LANG is en_US.UTF-8
Steps:
1) Boot up Fedora RISCV VM:
qemu-system-riscv64 \
>   -nographic \
>   -machine virt \
>   -smp 8 \
>   -m 2G \
>   -kernel
Fedora-Developer-Rawhide-20200108.n.0-fw_payload-uboot-qemu-virt-smode.elf \
>   -object rng-random,filename=/dev/urandom,id=rng0 \
>   -device virtio-rng-device,rng=rng0 \
>   -device virtio-blk-device,drive=hd0 \
>   -drive
file=Fedora-Developer-Rawhide-20200108.n.0-sda.raw,format=raw,id=hd0 \
>   -device virtio-net-device,netdev=usernet \
>   -netdev user,id=usernet,hostfwd=tcp::10000-:22
2) SSH to Fedora RISCV VM from Host:
ssh -p 10000 -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o
PreferredAuthentications=password -o PubkeyAuthentication=no root@localhost
3) Login Fedora RISCV VM:
Inherit Host env variable $LANG "zh_CN.utf8", although the VM's local $LANG
var in /etc/locale.conf is "en_US.UTF-8".
4) Build the EDK2 binary:
build -a RISCV64 -t GCC5 -p
Platform/SiFive/U5SeriesPkg/FreedomU540HiFiveUnleashedBoard/U540.dsc
When building, UiApp.offset file not created is due to the offset variable
cannot be fetched from UiApp.map file, and it causes the building failed.
The root cause of UiApp.offset file not created is "Archive member
included" does not appears in the head of UiApp.map.
But instead, "Archive member included" is written in Chinese words in
UiApp.map in my case. So offset var cannot be fetched because
GetVariableOffset doesn't handle Chinese words in its code logic.

So it's probably edk2 prioritizes or only handles env var $LANG, but not
check $LANG difference between env var and /etc/locale.conf.
My case workaround: Just re-source the VM local "/etc/locale.conf" to
change the $LANG to "en_US.UTF-8" and re-build the binary, then succeed.


Best Regards


Daniel Schaefer <notifications@github.com> 于2020年10月16日周五 下午6:15写道:

> Hmm, that sounds like a general EDK2 problem. In what language are those
> words written?
> How did you fix it?
> The people on the official EDK2 development mailing list would probably be
> interested to hear about your case: devel@edk2.groups.io
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/riscv/riscv-edk2-platforms/issues/10#issuecomment-709958189>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ABZF42J7MK2CSB6NNXITCVLSLAMNLANCNFSM4SRRJFUQ>
> .
>

[-- Attachment #2: Type: text/html, Size: 4782 bytes --]

           reply	other threads:[~2020-10-19  4:34 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <riscv/riscv-edk2-platforms/issues/10/709958189@github.com>]

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-list 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=CANrhGQDKidzLOrB54__7jBhPVfhcvr+E_+iw6TmETyiDu2r-sg@mail.gmail.com \
    --to=devel@edk2.groups.io \
    /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