From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.54) id 1EyVDw-0003ur-0Q for garchives@archives.gentoo.org; Mon, 16 Jan 2006 14:20:44 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id k0GEJQbp024524; Mon, 16 Jan 2006 14:19:26 GMT Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.200]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id k0GEJOB5012777 for ; Mon, 16 Jan 2006 14:19:25 GMT Received: by wproxy.gmail.com with SMTP id i12so1041051wra for ; Mon, 16 Jan 2006 06:19:24 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=lTQjrkqHyFfecdyNiDqYx9A7CXzwpGfg9DYf8/e4WfmtP/RAO6wogup4ecGZGjBU9hLtL7h3Ak8Eyo58bA95r370TxNM/kl8AqL2LFuelhe6l1lHNfFbGOAPUEc+GztRWuOQi8O8TbKAHqdHbqABxfGCQ30L4diK3b11SjyruK0= Received: by 10.54.132.10 with SMTP id f10mr8617564wrd; Mon, 16 Jan 2006 06:19:24 -0800 (PST) Received: by 10.54.156.9 with HTTP; Mon, 16 Jan 2006 06:19:24 -0800 (PST) Message-ID: Date: Mon, 16 Jan 2006 12:19:24 -0200 From: Douglas Campos To: gentoo-embedded@lists.gentoo.org Subject: Re: [gentoo-embedded] lockups with hardened kernel In-Reply-To: <43CB3A5A.4050505@djc.id.au> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-embedded@gentoo.org Reply-to: gentoo-embedded@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_21533_30380047.1137421164216" References: <1137145814.27064.171.camel@nc> <43CB3A5A.4050505@djc.id.au> X-Archives-Salt: 152b4930-7be5-44a2-9a11-46fc4724db62 X-Archives-Hash: 04b57c609403cf0129074a972df4ee38 ------=_Part_21533_30380047.1137421164216 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline No luck too... Just reboot then go crying aloud On 1/16/06, Dan C wrote: > > Douglas Campos wrote: > > I've found that using gcc-3.4.4-r1 made a lot of python modules going > > with "unresolved symbols", even when they compiled shamelessly > > > > I switched to gcc-3.3.6 and then everything went right! > > Well I have had no such luck. :-( > > I set up an alternate root and switched it to gcc-3.3.6, emerged > Subversion, but still got an unresolved symbol error with the Python > bindings. I updated to python 2.4 (since the stage only has 2.3), which > successfully compiled but now python2.4 itself dies with > > /usr/bin/python: can't resolve symbol 'dl_iterate_phdr' > > I guess for some reason, gcc, python, and uclibc are not playing nicely > together, at least not on my system, and I lack the necessary skills to > figure out exactly what's going on ... > > I'm really starting to wish that there were a big-endian ARM stage > available that uses regular old glibc, I expect that would eliminate all > these problems ... > > -- > Dan C > -- > gentoo-embedded@gentoo.org mailing list > > ------=_Part_21533_30380047.1137421164216 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
No luck too... Just reboot then go crying aloud
 
On 1/16/06, = Dan C <djc@djc.id.au> wrote:=
Douglas Campos wrote:
> I'= ve found that using gcc-3.4.4-r1 made a lot of python modules going
>= with "unresolved symbols", even when they compiled shamelessly
>
> I switched to gcc-3.3.6 and then everything went right!
Well I have had no such luck. :-(

I set up an alternate root an= d switched it to gcc-3.3.6, emerged
Subversion, but still got an unresol= ved symbol error with the Python
bindings. I updated to python 2.4 (since the stage only has 2.3), which=
successfully compiled but now python2.4 itself dies with

/usr/bi= n/python: can't resolve symbol 'dl_iterate_phdr'

I guess for some re= ason, gcc, python, and uclibc are not playing nicely
together, at least not on my system, and I lack the necessary skills to=
figure out exactly what's going on ...

I'm really starting to wi= sh that there were a big-endian ARM stage
available that uses regular ol= d glibc, I expect that would eliminate all
these problems ...

--
Dan C <djc@djc.id.au>
--
gentoo-embedded@gentoo.org mailing list


------=_Part_21533_30380047.1137421164216-- -- gentoo-embedded@gentoo.org mailing list