From: Mats Erik Andersson <mats.andersson64@comhem.se>
To: buildroot@busybox.net
Subject: [Buildroot] _IO_getc inconsistent with uClibc?
Date: Wed, 16 May 2007 19:51:29 +0200 [thread overview]
Message-ID: <1179337889.9676.22.camel@localhost> (raw)
Hi there,
in an effort to implement bluez-utils-2.15 for
an embedded system using uClibc, I ran into
unexpected problems, since my linker cannot
resolve the the symbol _IO_getc. Using a similar
configuration with Debian Sarge and building
bluez-utils, does not pose any problems, and
its linker kindly points to
_IO_getc@@GLIBC_2.0
when the relevant object files have been linkt
together. It was exactly at this stage that my
Buildroot setting decided to cancel work for the day!
Now, I did allow uClibc to use macros for getc
and puts in the configuration, out of old habit.
Is it these macros that cause the mess?
Regards, Mats Erik Andersson
next reply other threads:[~2007-05-16 17:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-16 17:51 Mats Erik Andersson [this message]
2007-05-16 18:16 ` [Buildroot] _IO_getc inconsistent with uClibc? Bernhard Fischer
2007-05-16 20:55 ` [Buildroot] libiconv Christopher Reder
2007-05-16 21:19 ` Christopher Reder
2007-05-18 7:20 ` Bernhard Fischer
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=1179337889.9676.22.camel@localhost \
--to=mats.andersson64@comhem.se \
--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