From: "Ard Biesheuvel" <ard.biesheuvel@linaro.org>
To: edk2-devel-groups-io <devel@edk2.groups.io>,
Laszlo Ersek <lersek@redhat.com>
Cc: discuss@edk2.groups.io, russell@mellanox.com
Subject: Re: [edk2-devel] [edk2-discuss] WriteSections64()
Date: Fri, 14 Jun 2019 21:43:48 +0200 [thread overview]
Message-ID: <CAKv+Gu-J7VWYF6erGKd66iyGscoqVSD_KXZRZk6qcAYEcxRQeg@mail.gmail.com> (raw)
In-Reply-To: <250c832b-150d-e63a-761c-8ac1666fbd80@redhat.com>
On Fri, 14 Jun 2019 at 21:17, Laszlo Ersek <lersek@redhat.com> wrote:
>
> +Ard, +devel
>
> On 06/13/19 17:29, Russell Peterson wrote:
> > Hello,
> >
> > We are in the process of upgrading our gcc toolchain to gcc 8.3 (from 7.3). In the process of doing that we have hit an error building edk2:
> >
> > make[2]: *** [/home/x/RELEASE_GCC5/AARCH64/MdeModulePkg/Universal/Network/DpcDxe/DpcDxe/DEBUG/DpcDxe.efi] Error 1
> > WriteSections64(): /home/x/RELEASE_GCC5/AARCH64/MdeModulePkg/Universal/Network/DpcDxe/DpcDxe/DEBUG/DpcDxe.dll AARCH64 relative relocations require identical ELF and PE/COFF section offsets
> >
> > There are multiple errors similar to this issued by GenFw. Our edk2 version is fairly recent (UDK2018 upstream branch as of commit 10318063b) but all this did build fine with gcc 7.3. Any clues?
> >
Your Conf/tools_def.txt is probably stale, and does not contain the
-fno-pie option we added a while ago.
next prev parent reply other threads:[~2019-06-14 19:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AM6PR05MB5572BFC98AF62AFED0244CC0C7EF0@AM6PR05MB5572.eurprd05.prod.outlook.com>
2019-06-14 19:17 ` [edk2-discuss] WriteSections64() Laszlo Ersek
2019-06-14 19:43 ` Ard Biesheuvel [this message]
2019-06-14 21:19 ` [edk2-devel] " Russell Peterson
[not found] ` <15A82D62E078CF58.4443@groups.io>
2019-06-15 0:17 ` Russell Peterson
2019-06-15 8:28 ` Ard Biesheuvel
2019-06-16 14:11 ` Russell Peterson
2019-06-17 12:56 ` Russell Peterson
2019-06-17 9:41 ` Ard Biesheuvel
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=CAKv+Gu-J7VWYF6erGKd66iyGscoqVSD_KXZRZk6qcAYEcxRQeg@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