From: Martin Str|mberg <ams AT speedy DOT ludd DOT luth DOT se>
Subject: Re: DXE2GEN: unresolved symbol
Newsgroups: comp.os.msdos.djgpp
References: <3cf910c2$0$23731$9b622d9e AT news DOT freenet DOT de>
User-Agent: tin/1.4.4-20000803 ("Vet for the Insane") (UNIX) (NetBSD/1.5_BETA (alpha))
Message-ID: <1022961734.321994@queeg.ludd.luth.se>
Cache-Post-Path: queeg.ludd.luth.se!unknown AT speedy DOT ludd DOT luth DOT se
X-Cache: nntpcache 2.4.0b5 (see http://www.nntpcache.org/)
Date: 01 Jun 2002 20:02:14 GMT
Lines: 20
NNTP-Posting-Date: 01 Jun 2002 20:02:14 GMT
NNTP-Posting-Host: queeg.ludd.luth.se
X-Trace: 1022961734 news.luth.se 286 130.240.16.109
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

deckerben <deckerben AT freenet DOT de> wrote:
: Hello group,

: I must resolve some DJGPP-specific symbols somewhere in Python so that
: dynamic linking can start (hopefully) really working. The first step, I
: believe, is to build a single .dxe with no unresolved symbols to isolate the
: problem areas and what the DXE_EXPORT_TABLE needs to carry. The following
: symbols cannot be resolved:

: command:
: dxe2gen zlibmodule.o -o zlibmodule.dxe -lz -lpython -ldl -lc -lgcc
: dl-djgpp.o

I'm not sure exactly what the problem is, but one thing I'm sure of:
you need to put your .o files before the libraries.


Right,

						MartinS