public inbox for gentoo-embedded@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dan C <djc@djc.id.au>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] lockups with hardened kernel
Date: Mon, 16 Jan 2006 16:16:58 +1000	[thread overview]
Message-ID: <43CB3A5A.4050505@djc.id.au> (raw)
In-Reply-To: <cc04c5eb0601130300h7c455e7ci58bb6e6acbd62469@mail.gmail.com>

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 <djc@djc.id.au>
-- 
gentoo-embedded@gentoo.org mailing list



  parent reply	other threads:[~2006-01-16  6:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-04  8:52 [gentoo-embedded] lockups with hardened kernel Natanael Copa
2006-01-07  5:44 ` Mike Frysinger
2006-01-07  7:30   ` Natanael Copa
2006-01-07  7:35     ` Mike Frysinger
2006-01-09 16:20       ` Peter S. Mazinger
2006-01-09 19:49         ` Douglas Campos
2006-01-13  9:50         ` Natanael Copa
2006-01-13 11:00           ` Douglas Campos
2006-01-14  4:37             ` Dan C
2006-01-14 10:13               ` Dan C
2006-01-16  6:16             ` Dan C [this message]
2006-01-16 14:19               ` Douglas Campos

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=43CB3A5A.4050505@djc.id.au \
    --to=djc@djc.id.au \
    --cc=gentoo-embedded@lists.gentoo.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