From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] linking against gdbm fails when emerging python
Date: Mon, 26 Sep 2005 01:04:22 -0400 [thread overview]
Message-ID: <200509260104.22167.vapier@gentoo.org> (raw)
In-Reply-To: <43327A5D.9090807@tanael.org>
On Thursday 22 September 2005 05:33 am, Natanael Copa wrote:
> i386-gentoo-linux-uclibc-gcc -pthread -DNDEBUG -march=i386 -Os -pipe
> -fomit-frame-pointer -fPIC -fno-strict-aliasing -DHAVE_GDBM_NDBM_H -I.
> -I/var/tmp/portage/python-2.3.5-r2/work/Python-2.3.5/./Include
> -I/var/tmp/portage/python-2.3.5-r2/work/Python-2.3.5/Include
> -I/var/tmp/portage/python-2.3.5-r2/work/Python-2.3.5 -c
> /var/tmp/portage/python-2.3.5-r2/work/Python-2.3.5/Modules/dbmmodule.c
> -o build/temp.linux-i686-2.3/dbmmodule.o
> i386-gentoo-linux-uclibc-gcc -pthread -shared
> build/temp.linux-i686-2.3/dbmmodule.o -L/usr/local/lib -lgdbm -o
> build/lib.linux-i686-2.3/dbm.so
> ./python: can't resolve symbol 'dbm_firstkey'
> make: *** [sharedmods] Error 1
so you're still hitting this linker bug ? just wondering whether i should
start poking at it or assume that it's been resolved one way or another ...
-mike
--
gentoo-embedded@gentoo.org mailing list
next prev parent reply other threads:[~2005-09-26 5:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-22 9:33 [gentoo-embedded] linking against gdbm fails when emerging python Natanael Copa
2005-09-22 13:31 ` Mike Frysinger
2005-09-22 13:43 ` Natanael Copa
2005-09-22 13:59 ` Mike Frysinger
2005-09-22 14:56 ` Natanael Copa
2005-09-22 20:58 ` Natanael Copa
2005-09-26 5:04 ` Mike Frysinger [this message]
2005-09-26 7:32 ` Natanael Copa
2005-12-27 8:33 ` Mike Frysinger
2005-12-27 9:33 ` Natanael Copa
2005-12-27 9:39 ` Mike Frysinger
2005-12-27 9:52 ` Natanael Copa
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=200509260104.22167.vapier@gentoo.org \
--to=vapier@gentoo.org \
--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