From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2017-03-17
Date: Sat, 18 Mar 2017 16:15:51 +0100 [thread overview]
Message-ID: <124f5fc5-6307-f72f-f1be-8f2139dffced@mind.be> (raw)
In-Reply-To: <20170318072841.AF04B20775@mail.free-electrons.com>
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.
The weird thing is that other packages using libtirpc *don't* fail, e.g. argus.
Hm, looks like that one links against libtirpc but doesn't actually use any of
its symbols...
Waldemar, any idea?
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2017-03-18 15:15 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 [this message]
2017-03-18 16:02 ` Waldemar Brodkorb
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=124f5fc5-6307-f72f-f1be-8f2139dffced@mind.be \
--to=arnout@mind.be \
--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 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.