All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Williams <patrick@stwcx.xyz>
To: Mike <proclivis@gmail.com>
Cc: openbmc@lists.ozlabs.org
Subject: Re: libtirpc link error
Date: Fri, 23 Apr 2021 08:08:54 -0500	[thread overview]
Message-ID: <YILG5jY2q/lHc1hy@heinlein> (raw)
In-Reply-To: <61F426A9-21C7-4D09-BB20-AC4046F436DD@gmail.com>

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

On Wed, Apr 21, 2021 at 04:30:29PM -0600, Mike wrote:
> Hi,
> 
> Has anyone seen link errors for libtirpc-1.2.5-r0 from openbmc tag 2.9?
> 
> I tried building with tag 2.9 using my added layers and conf from a successful tag 2.8, but get errors in libtirpc_la-binddynport.o for multiple definitions of __svc_xports.
> 
> Mike
> 
> Sent from my iPhone

I don't know of anyone reporting build issues with a recent tag.  I had
updated it not too long ago to pull in security fixes from Yocto and it
builds successfully then.

Is this a `bitbake` failure you're seeing?  Which package is it for?  I
assume it is a base Yocto package because we don't have anything that
should be directly linking against libtirpc.

The "multiple definitions" sounds like something that newer versions of
GCC have become stricter about.  In that case, I'd only expect you to
have different results if this were a native package (that for some
reason, incorrectly, your host GCC is being invoked for).  I think many
of us use a Docker container to build in, especially older releases, so
you may want to make sure you've got a common environment to what we use
in CI for testing.  I personally use the crops/poky docker image for
building any older Yocto releases.

-- 
Patrick Williams

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2021-04-23 13:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-21 22:30 libtirpc link error Mike
2021-04-23 13:08 ` Patrick Williams [this message]

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=YILG5jY2q/lHc1hy@heinlein \
    --to=patrick@stwcx.xyz \
    --cc=openbmc@lists.ozlabs.org \
    --cc=proclivis@gmail.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.