From: Carmelo AMOROSO <carmelo.amoroso@st.com>
To: buildroot@busybox.net
Subject: [Buildroot] [Fwd: Re: Struggling with undefined reference to `__fgetc_unlocked']
Date: Thu, 23 Aug 2007 18:43:11 +0200 [thread overview]
Message-ID: <46CDB91F.80307@st.com> (raw)
my reply below
-------- Original Message --------
Subject: Re: [Buildroot] Struggling with undefined reference to
`__fgetc_unlocked'
Date: Thu, 23 Aug 2007 18:42:31 +0200
From: Carmelo Amoroso <carmelo.amoroso@st.com>
Organization: STMicroelectronics
To: "Thiago A. Corr?a" <thiago.correa@gmail.com>
References:
<d6cda7730708230925x19bc0901v9a6dd1f18ee325ec@mail.gmail.com>
<46CDB759.709@st.com>
<d6cda7730708230939p7b126fe1mbe28768aa4413bb4@mail.gmail.com>
Thiago A. Corr?a wrote:
> Hi Carmelo,
>
> That command returned
> gentoo-vm buildroot # readelf -s /lib/libc.so.6 | grep fgetc_unlocked
> 1868: 0005e040 40 FUNC WEAK DEFAULT 11 fgetc_unlocked@@GLIBC_2.1
> gentoo-vm buildroot #
>
> I'm guessing the prepended underscores are due to mangling, but
> could be wrong.
>
Not, they are part of the symbol's name... you need to fix qtopia to
call the fgetc_unlocked.
Cheers
> On 8/23/07, Carmelo AMOROSO <carmelo.amoroso@st.com> wrote:
>
>> Thiago A. Corr?a wrote:
>>
>>> Hi,
>>>
>>> I'm struggling with qtopia. During the link of rcc (which is a host
>>> tool, natively compiled) I get:
>>>
>>> I googled for the error, but could only find ppl complaining about
>>> this when linking against uClibc, when this should be linking against
>>> the system glibc. Does anyone has an idea of what I could try?
>>>
>>> Regards,
>>> Thiago A. Correa
>>>
>>>
>> Which glibc version have you installed on your host?
>> For example, on my RHEL 3 there is glibc-2.3.4 which doesn't contain the
>> __fgetc_unlocked
>> symbol, while fgetc_unlocked (no underscore prepending)...
>> so just check your glibc by running 'readelf -s /lib/libc.so.6 | grep
>> fgetc_unlocked'
>> and see what it returns.
>>
>> Regards,
>> Carmelo
>>
>>
>>> _______________________________________________
>>> buildroot mailing list
>>> buildroot at uclibc.org
>>> http://busybox.net/mailman/listinfo/buildroot
>>>
>>>
>>>
>>
next reply other threads:[~2007-08-23 16:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-23 16:43 Carmelo AMOROSO [this message]
2007-08-23 16:53 ` [Buildroot] [Fwd: Re: Struggling with undefined reference to `__fgetc_unlocked'] Thiago A. Corrêa
2007-08-23 16:57 ` Carmelo AMOROSO
2007-08-23 17:25 ` Thiago A. Corrêa
2007-08-23 20:18 ` Bernhard Fischer
2007-08-27 10:37 ` Hans-Christian Egtvedt
2007-08-27 13:33 ` Thiago A. Corrêa
2007-08-27 13:48 ` Hans-Christian Egtvedt
2007-08-27 15:50 ` Thiago A. Corrêa
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=46CDB91F.80307@st.com \
--to=carmelo.amoroso@st.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