Getting expat compiled properly

Alex Martelli aleax at
Fri Sep 7 12:03:02 CEST 2001

"Magnus Lie Hetland" <mlh at> wrote in message
news:9na244$gc0$1 at
> > I see (I did not take your previous statement that there might be a
> > somewhere for definite). In that case, specifying the full
> > libexpat.a path to the linker (instead of using a -l option) will do
> > the trick.
> OK. That's useful to know... But how do I express that instead of
> using -l? Can I use -L? Or?

Just give the full path to libexpat.a, including this very
name and extension, as you would give it to a whatever.o file.
No switch needed -- non-option arguments to the linker are
paths to object OR library files.


More information about the Python-list mailing list