From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2013-10-14
Date: Tue, 15 Oct 2013 19:31:07 +0200 [thread overview]
Message-ID: <20131015193107.33e234f5@skate> (raw)
In-Reply-To: <A9D235D0-F376-428F-A49F-E315294C4B5D@layer-7.net>
Dear Michael Rommel,
On Tue, 15 Oct 2013 19:16:16 +0200, Michael Rommel wrote:
> I had a look at this error and tried to compare that with currently
> running builds. As far as I can see, a default build on a i586 with
> the included toolchain works fine and does not need linking with
> libpcre. Also a nm on the mentioned file (sysroot/usr/lib/crt1.o)
> reveals no _gp symbol on an i586 whereas with the external nios
> toolchain, _gp is referenced as symbol.
>
> rommel at pelican:/var/nfs/software/initrds/uclibc/buildroot-clean-i586/host/usr/i586-buildroot-linux-uclibc/sysroot/usr/lib$
> nm crt1.o 00000000 D __data_start
> U __uClibc_main
> U _fini
> U _init
> 00000000 T _start
> 00000000 W data_start
> U main
>
> Yes, if I include -lpcre on the linker line, the nios2 compile
> completes, but I have no way of testing, whether the result works. I
> also could not find any direct dependency from aiccu to the pcre,
> neither a function call that starts with pcre_, nor an inclusion of a
> pcre.h header file. And, yes, If I include -lpcre on the commandline,
> also the resulting i586 binary works, but unless someone convinces me
> that his is really a missing dependency of aiccu, I am hesitant to
> change anything right now, as most other builds went okay.
>
> I tend to think, that this is a problem not related to aiccu, but if
> anyone else can confirm this, I fell better :-)
I do agree that blindly linking with pcre does not seem like a good
option. A quick Google search about NIOS and gp indicates that gp is a
special register used to access global data. So I believe this _gp
symbol is more likely related to some toolchain internals rather than
to pcre.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2013-10-15 17:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2013-10-14 Thomas Petazzoni
2013-10-15 17:16 ` Michael Rommel
2013-10-15 17:31 ` Thomas Petazzoni [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=20131015193107.33e234f5@skate \
--to=thomas.petazzoni@free-electrons.com \
--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