_IO_getc inconsistent with uClibc?

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

What version of uClibc are you using?
Does uClibc-0.9.29-fix-fget_putc.diff help?

I have searched around for a solution to the problem I have been having and while there are a number of entries with the same issue, no one has a posted solution. I am using buildroot from svn with tiny-x server and metacity enabled. This will bring in gtk+ and other packages. Without metacity and those packages, everything compiles fine.

When I add it in, I get the following error:

checking for iconv_open in -liconv... no
configure: error: *** No iconv() implementation found in C library or libiconv
make: *** [/home/christopher/buildroot/build_arm/glib-2.12.9/.configured] Error 1

and from config.log:

configure:5964: checking for iconv_open
configure:6020:
/home/christopher/buildroot/build_arm/staging_dir/bin/arm-linux-uclibc-gcc -$/tmp/cc06WWDf.o: In function `main':
conftest.c:(.text+0x4): undefined reference to `iconv_open'
collect2: ld returned 1 exit status
configure:6026: $? = 1

I have iconv installed and see iconv in /usr/local/bin . can someone please explain what is going on and what is wrong with this?

Has anyone gotten something like this working for the arm (920T architecture) ?

Christopher

To add to the question, when I install libiconv, do I need to cross compile it as well? When I do, if I should, do I install it in a specific directory? What about the libiconv.so.2 for the pc? Can someone clarify what should happen with that?

-----Original Message-----
From: [email protected] [mailto:buildroot-bounces at uclibc.org] On Behalf Of Christopher Reder
Sent: Wednesday, May 16, 2007 3:55 PM
To: buildroot at uclibc.org
Subject: [Buildroot] libiconv

I have searched around for a solution to the problem I have been having and while there are a number of entries with the same issue, no one has a posted solution. I am using buildroot from svn with tiny-x server and metacity enabled. This will bring in gtk+ and other packages. Without metacity and those packages, everything compiles fine.

When I add it in, I get the following error:

checking for iconv_open in -liconv... no
configure: error: *** No iconv() implementation found in C library or libiconv
make: *** [/home/christopher/buildroot/build_arm/glib-2.12.9/.configured] Error 1

and from config.log:

configure:5964: checking for iconv_open
configure:6020:
/home/christopher/buildroot/build_arm/staging_dir/bin/arm-linux-uclibc-gcc -$/tmp/cc06WWDf.o: In function `main':
conftest.c:(.text+0x4): undefined reference to `iconv_open'
collect2: ld returned 1 exit status
configure:6026: $? = 1

I have iconv installed and see iconv in /usr/local/bin . can someone please explain what is going on and what is wrong with this?

Has anyone gotten something like this working for the arm (920T architecture) ?

Christopher

_______________________________________________
buildroot mailing list
buildroot at uclibc.org
http://busybox.net/mailman/listinfo/buildroot

How is this related to getc()? Don't hijack threads!