From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2017-03-17
Date: Sat, 18 Mar 2017 17:02:25 +0100 [thread overview]
Message-ID: <20170318160225.GL23128@waldemar-brodkorb.de> (raw)
In-Reply-To: <124f5fc5-6307-f72f-f1be-8f2139dffced@mind.be>
Hi Arnout,
Arnout Vandecappelle wrote,
>
>
> On 18-03-17 08:28, Thomas Petazzoni wrote:
> > microblazeel | nfs-utils-1.3.3 | NOK | http://autobuild.buildroot.net/results/240cfb0497b1dd7b5b33b8f64635cca435d49f05
>
> I looked at this one and I'm a bit stumped. This is the error:
> .../sysroot/usr/lib/libc.a(clnt_simple.os): In function `callrpc':
> (.text+0x0): multiple definition of `callrpc'
> .../sysroot/usr/lib/libtirpc.a(libtirpc_la-rpc_soc.o):(.text+0x784): first
> defined here
> (and many more like that).
>
> It's a bit weird that this object file from the C library even gets linked in.
> The Map file says:
>
> .../sysroot/usr/lib/libc.a(rpc_thread.os)
> .../sysroot/usr/lib/libc.a(cancel.os) (__rpc_thread_destroy)
> (skipping a few levels of indirection here).
>
> So somehow the pthread library is pulling in the RPC support from uClibc, which
> obviously conflicts with tirpc.
But if BR2_TOOLCHAIN_EXTERNAL_INET_RPC=y is active, isn't uClibc-ng
build with RPC support? If this is the case, you end up with two RPC
implememtations. That should be handled by Buildroot.
Do you have support for use either libtirpc or uClibc-ng internal
RPC support?
best regards
Waldemar
next prev parent reply other threads:[~2017-03-18 16:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-18 7:28 [Buildroot] [autobuild.buildroot.net] Build results for 2017-03-17 Thomas Petazzoni
2017-03-18 15:15 ` Arnout Vandecappelle
2017-03-18 16:02 ` Waldemar Brodkorb [this message]
2017-03-18 16:19 ` Arnout Vandecappelle
2017-03-18 16:33 ` Waldemar Brodkorb
2017-03-18 17:11 ` Arnout Vandecappelle
2017-03-18 19:46 ` Waldemar Brodkorb
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=20170318160225.GL23128@waldemar-brodkorb.de \
--to=wbx@openadk.org \
--cc=buildroot@busybox.net \
/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