Skip Menu |

This queue is for tickets about the Math-Pari CPAN distribution.

Report information
The Basics
Id: 54200
Status: open
Priority: 0/
Queue: Math-Pari

People
Owner: Nobody in particular
Requestors: mark_kacanda [...] qvc.com
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: error: unknown opcode "usr" & error: statement syntax
Hello Ilya, Have successfully built Math::Pari and hence Net::SFTP on two additional systems but am still being challenged by a remote system with the following errors during make, I thought the "perl Makefile.PL machine=none" option from the README file would help. Any suggestions are appreciated, Kind Regards, Mark # cd Math-Pari-2.01080603 # perl Makefile.PL machine=none # make cd libPARI && make LIBPERL_A="libperl.a" LINKTYPE="dynamic" OPTIMIZE="- O" PREFIX ="/usr/local" PASTHRU_DEFINE="" PASTHRU_INC="" make[1]: Entering directory `/home/staff/billmast/Math-Pari- 2.01080603/libPARI' gcc -c -I ../../pari-2.3.4/src -I ../../pari-2.3.4/src/headers - I ../../pari-2. 3.4/src/graph -I . -fno-strict-aliasing -pipe -Wdeclaration-after- statement -I/u sr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O - DVERSION=\"\" -DXS_VERSION=\"\" -fPIC -Derr=pari_err -DSOLARIS -DASMINLINE - DGCC_INLINE -DDYNA MIC_PLOTTING -o es.o ../../pari-2.3.4/src/language/es.c /usr/ccs/bin/as: "<stdin>", line 1: error: unknown opcode "usr" /usr/ccs/bin/as: "<stdin>", line 1: error: statement syntax make[1]: *** [es.o] Error 1 make[1]: Leaving directory `/home/staff/billmast/Math-Pari- 2.01080603/libPARI' make: *** [libPARI/libPARI.a] Error 2
CC: undisclosed-recipients: ;
Subject: Re: [rt.cpan.org #54200] error: unknown opcode "usr" & error: statement syntax
Date: Mon, 1 Feb 2010 12:41:31 -0800
To: mkacanda via RT <bug-Math-Pari [...] rt.cpan.org>
From: Ilya Zakharevich <nospam-abuse [...] ilyaz.org>
On Mon, Feb 01, 2010 at 02:18:12PM -0500, mkacanda via RT wrote: Show quoted text
> # cd Math-Pari-2.01080603 > # perl Makefile.PL machine=none
This should never happen. There is always output. Yours, Ilya