compiling using native compiler
Michael Murphy
mpm at rohi.engr.sgi.com
Tue Oct 5 13:11:59 EDT 2004
More information about the Python-list mailing list
Tue Oct 5 13:11:59 EDT 2004
- Previous message (by thread): compiling using native compiler
- Next message (by thread): compiling using native compiler
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
In article <95650bb5.0410050819.2f34f323 at posting.google.com>, SS <sridhara at yahoo.com> wrote: >When I try to compile python 2.3.4 using SGI's native compiler >./configure --without-gcc >followed by >make > >I get error >make > c++ -o python \ > Modules/python.o \ > libpython2.3.a -ldl -lpthread -lmpc -lm >ld32: WARNING 84 : /usr/lib32/libdl.so is not used for resolving any symbol. >ld32: FATAL 9 : I/O error (-lmpc): No such file or directory >collect2: ld returned 32 exit status >*** Error code 1 (bu21) > >but I see it in /usr/lib > >ls -l /usr/lib/mpc >-rwxrwxr-x 1 root sys 598996 May 20 17:10 /usr/lib/mpc The other response tells you how to get python working, but I just wanted to point out that -lmpc means link with libmpc.{a,so} So /usr/lib/mpc has nothing to do with -lmpc -- -- Mike Murphy -- mpm at sgi.com -- quote of the day: -- "Never be afraid to try something new.
- Previous message (by thread): compiling using native compiler
- Next message (by thread): compiling using native compiler
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list