Yocto Project Discussions
 help / color / mirror / Atom feed
From: "Peter Kjellerstedt" <peter.kjellerstedt@axis.com>
To: Joshua Watt <JPEWhacker@gmail.com>, Khem Raj <raj.khem@gmail.com>
Cc: "yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>
Subject: Re: [yocto] [meta-gplv2] [PATCH] gnupg: Make it build with GCC 10 (which uses -fno-common by default)
Date: Mon, 5 Oct 2020 20:36:52 +0000	[thread overview]
Message-ID: <39a0f312f43f4a19919eeec0451ff8d3@XBOX03.axis.com> (raw)
In-Reply-To: <CAJdd5GbfPOcAFk5cZfthBK=jL_yNypqFNeVtvC0snh9rBsj_5g@mail.gmail.com>

> -----Original Message-----
> From: yocto@lists.yoctoproject.org <yocto@lists.yoctoproject.org> On
> Behalf Of Joshua Watt
> Sent: den 1 oktober 2020 15:27
> To: Khem Raj <raj.khem@gmail.com>
> Cc: Peter Kjellerstedt <peter.kjellerstedt@axis.com>;
> yocto@lists.yoctoproject.org
> Subject: Re: [yocto] [meta-gplv2] [PATCH] gnupg: Make it build with GCC
> 10 (which uses -fno-common by default)
> 
> On Wed, Sep 30, 2020 at 4:34 PM Khem Raj <raj.khem@gmail.com> wrote:
> >
> > On Wed, Sep 30, 2020 at 1:37 PM Joshua Watt <JPEWhacker@gmail.com>
> wrote:
> > >
> > > With this patch applied, I get the following errors when using the
> > > latest master branches:
> > >
> > > | ../mpi/libmpi.a(mpiutil.o): In function `mpi_alloc_limb_space':
> > > | mpiutil.c:(.text+0x84): undefined reference to `memory_debug_mode'
> > > | ../mpi/libmpi.a(mpiutil.o): In function `mpi_alloc':
> > > | mpiutil.c:(.text+0xda): undefined reference to `memory_debug_mode'
> > > | ../mpi/libmpi.a(mpiutil.o): In function `mpi_alloc_secure':
> > > | mpiutil.c:(.text+0x14a): undefined reference to `memory_debug_mode'
> > > | ../mpi/libmpi.a(mpiutil.o): In function `mpi_free_limb_space':
> > > | mpiutil.c:(.text+0x1c7): undefined reference to `memory_debug_mode'
> > > | ../mpi/libmpi.a(mpiutil.o): In function `mpi_free':
> > > | mpiutil.c:(.text+0x267): undefined reference to `memory_debug_mode'
> > > | ../util/libutil.a(iobuf.o): In function `file_filter':
> > > | iobuf.c:(.text+0x1c0): undefined reference to `iobuf_debug_mode'
> > > | iobuf.c:(.text+0x1ea): undefined reference to `iobuf_debug_mode'
> > > | iobuf.c:(.text+0x2e0): undefined reference to `iobuf_debug_mode'
> > > | iobuf.c:(.text+0x305): undefined reference to `iobuf_debug_mode'
> > > | ../util/libutil.a(iobuf.o): In function `underflow':
> > > | iobuf.c:(.text+0x4b3): undefined reference to `iobuf_debug_mode'
> > > | ../util/libutil.a(iobuf.o):iobuf.c:(.text+0x567): more undefined
> > > references to `iobuf_debug_mode' follow
> > > | collect2: error: ld returned 1 exit status
> > >
> > > If I revert this commit, gnupg-native will again build correctly. Any
> > > ideas?

Interesting. I had not considered building the recipes from 
meta-gplv2 for native as we only use them for target builds.

> > does it help if you add -fno-common to native CFLAGS
> 
> No. It works in all cases if I remove the patch and use "-fcommon"
> though. Oddly enough, in my build having the patch caused the target
> recipe to fail one way, and not having it caused it to fail another
> way....

Are you saying you still have build failures when building gnupg for 
target as well, with the patch applied?

> not sure what's going on there, but I suspect for something
> this old, adding "-fcommon" to restore the original behavior makes the
> most sense.

Anyway, I get the same errors as above when I try building it for 
native using gcc 9.3.1. I'll look into it and see if I can improve 
the patch, or if I will have to resort to using -fcommon.

//Peter


  reply	other threads:[~2020-10-05 20:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-31 22:44 [meta-gplv2] [PATCH] gnupg: Make it build with GCC 10 (which uses -fno-common by default) Peter Kjellerstedt
2020-09-30 20:36 ` [yocto] " Joshua Watt
2020-09-30 21:34   ` Khem Raj
2020-10-01 13:26     ` Joshua Watt
2020-10-05 20:36       ` Peter Kjellerstedt [this message]
2020-10-05 20:57         ` Joshua Watt
2020-10-13 15:00         ` Joshua Watt

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=39a0f312f43f4a19919eeec0451ff8d3@XBOX03.axis.com \
    --to=peter.kjellerstedt@axis.com \
    --cc=JPEWhacker@gmail.com \
    --cc=raj.khem@gmail.com \
    --cc=yocto@lists.yoctoproject.org \
    /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