public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Gerd Hoffmann" <kraxel@redhat.com>
To: Leif Lindholm <quic_llindhol@quicinc.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Re: [edk2-devel] MicrovmX64, "Did not find any '.text' section"
Date: Fri, 1 Nov 2024 10:55:26 +0100	[thread overview]
Message-ID: <2x5cykaf7erih2e5nkkdq5bragkn756pjhudetcphqzfq2fujo@4h7v7uxp2mta> (raw)
In-Reply-To: <1cac29cf-a460-421b-bb76-b71416fb5274@quicinc.com>

On Thu, Oct 10, 2024 at 04:52:48PM +0100, Leif Lindholm wrote:
> Hi Gerd, others,
> 
> While working on the FdtLib migration to the submodule variant, I decided to
> at least try to test build MicrovmX64 ... but I'm failing.
> 
> Both clang and gcc builds bail out at a GenFw invocation to generate
> ResetVector.efi due to "Did not find any '.text' section". (Assert on line
> 938 of Elf64Convert.c.)
> OvmfPkgX64 builds without issue.
> 
> Is there something I'm missing?
> Can anyone else build MicrovmX64 on current HEAD?

Works for me (Fedora 40, gcc 14.2.1).
Using in-tree C BaseTools.

The microvm build creates an
Build/MicrovmX64/DEBUG_GCC5/X64/OvmfPkg/ResetVector/ResetVector/DEBUG/ResetVector.dll
file which had no .text section indeed.

The OvmfPkgX64 build doesn't even though both use the same
ResetVector.inf.  Hmm, not sure why, but it's probably related.

take care,
  Gerd



-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#120700): https://edk2.groups.io/g/devel/message/120700
Mute This Topic: https://groups.io/mt/108931674/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



  reply	other threads:[~2024-11-01  9:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-10 15:52 [edk2-devel] MicrovmX64, "Did not find any '.text' section" Leif Lindholm
2024-11-01  9:55 ` Gerd Hoffmann [this message]
2024-11-04 21:17   ` Oliver Smith-Denny

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=2x5cykaf7erih2e5nkkdq5bragkn756pjhudetcphqzfq2fujo@4h7v7uxp2mta \
    --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