From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] Bump gpsd from version 2.95 to version 3.7
Date: Tue, 24 Jul 2012 10:11:03 +0200 [thread overview]
Message-ID: <20120724101103.6a11efda@skate> (raw)
In-Reply-To: <20120724084545.6c0cedab@skate>
Another build issue:
(5)
gpsd.o: In function `onsig':
gpsd.c:(.text+0x8): undefined reference to `_mcount'
gpsd.o: In function `adjust_max_fd':
gpsd.c:(.text+0x38): undefined reference to `_mcount'
gpsd.o: In function `rstrip':
gpsd.c:(.text+0xe0): undefined reference to `_mcount'
gpsd.o: In function `find_device':
gpsd.c:(.text+0x160): undefined reference to `_mcount'
gpsd.o: In function `snarfline':
gpsd.c:(.text+0x204): undefined reference to `_mcount'
gpsd.o:gpsd.c:(.text+0x2ec): more undefined references to `_mcount' follow
collect2: ld returned 1 exit status
scons: *** [gpsd] Error 1
scons: building terminated because of errors.
make: *** [/home/peko/scratch/build/gpsd-3.7/.stamp_built] Error 2
See
http://autobuild.buildroot.org/results/be707893f4bf0e7e964d183e4a655c5bb72d1889/build-end.log
and
http://autobuild.buildroot.org/results/be707893f4bf0e7e964d183e4a655c5bb72d1889/defconfig.
It happens when BR2_PACKAGE_GPSD_PROFILING is enabled. I don't know if
uClibc has the necessary infrastructure to support profiling.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-07-24 8:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-23 19:29 [Buildroot] [PATCH v3] Bump gpsd from version 2.95 to version 3.7 spdawson at gmail.com
2012-07-23 21:27 ` Thomas Petazzoni
2012-07-24 6:40 ` Thomas Petazzoni
2012-07-24 6:45 ` Thomas Petazzoni
2012-07-24 8:11 ` Thomas Petazzoni [this message]
2012-07-24 8:23 ` Simon Dawson
2012-07-24 8:50 ` Thomas Petazzoni
2012-07-24 14:05 ` Simon Dawson
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=20120724101103.6a11efda@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