From: Carmelo AMOROSO <carmelo.amoroso@st.com>
To: linux-sh@vger.kernel.org
Subject: Re: Hi, all,
Date: Mon, 21 Jan 2008 17:14:43 +0000 [thread overview]
Message-ID: <4794D303.8070001@st.com> (raw)
In-Reply-To: <200801201730.07407.vapier@gentoo.org>
Fabio Giovagnini wrote:
> Sorry Carmelo,
> could you explain me better how you solved the problem?
> Regards
>
>
There is a problem into uClibc when statically linking a C++ application,
but it's not clear if this is what you are trying to do.... even if the
output
is the same as in my case.
So you should attach the whole command line used to build you app,
further the verbose output (using -v)
could be useful.
Carmelo
> Alle 08:46, lunedì 21 gennaio 2008, Carmelo AMOROSO ha scritto:
>
>> Mike Frysinger wrote:
>>
>>> On Sunday 20 January 2008, Mike Frysinger wrote:
>>>
>>>> On Sunday 20 January 2008, Fabio Giovagnini wrote:
>>>>
>>>>> I have such a problem with.
>>>>> sh-uclibc-g++ 3.4.6
>>>>>
>>>>> /home/fgiovagnini/sh7203-uClinux-1.4/build/../gcc-3.4.6/gcc/unwind-dw2-
>>>>> fd e- glibc.c:291: undefined reference to `dl_iterate_phdr'
>>>>>
>>>>> How can I solve.
>>>>> Any suggestion will be appreciated.
>>>>>
>>>> a one line error isnt exactly useful ... you didnt say what version of
>>>> uClibc you're using or what you're using for a build system.
>>>>
>>> and more importantly, what exactly are you doing
>>> -mike
>>>
>> Hi Mike,
>> I think that Fabio is trying to linking statically a C++ application
>> against uClibc. If so, (Fabio please clarify), the problem is extactly
>> the same
>> I posted on uClibc list last week (mmove _dl_iterate_phdr from libdl.a
>> to libc.a).
>>
>> I have a already fixed it for nptl/sh4 branch... I'm just now merging
>> the patch
>> for the uClibc branch and post it for a wider review on uClibc.
>>
>> I'll put Fabio into the loop.. anyway Fabio should post his full command
>> line
>> used to build/link his application.
>>
>> Cheers,
>> Carmelo
>> -
>> To unsubscribe from this list: send the line "unsubscribe linux-sh" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
>
next prev parent reply other threads:[~2008-01-21 17:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-20 22:30 Hi, all, Mike Frysinger
2008-01-21 1:55 ` Mike Frysinger
2008-01-21 7:46 ` Carmelo AMOROSO
2008-01-21 8:08 ` Mike Frysinger
2008-01-21 8:38 ` Fabio Giovagnini
2008-01-21 8:39 ` Fabio Giovagnini
2008-01-21 14:29 ` Fabio Giovagnini
2008-01-21 17:14 ` Carmelo AMOROSO [this message]
2008-01-21 17:50 ` Fabio Giovagnini
2008-01-22 7:58 ` Carmelo AMOROSO
2008-01-22 9:34 ` Kieran Bingham
2008-01-22 9:39 ` Fabio Giovagnini
2008-01-22 9:57 ` Paul Mundt
2008-01-22 10:13 ` Carmelo AMOROSO
2008-01-22 11:21 ` Fabio Giovagnini
2008-01-23 19:50 ` Fabio Giovagnini
2008-01-23 23:06 ` Fabio Giovagnini
2008-01-23 23:47 ` Kieran Bingham
2008-01-24 12:16 ` Fabio Giovagnini
2008-01-28 10:05 ` Fabio Giovagnini
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=4794D303.8070001@st.com \
--to=carmelo.amoroso@st.com \
--cc=linux-sh@vger.kernel.org \
/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