down *by* the river. (I can't even get *that* right.) Cheers!
On Tue, Mar 3, 2015 at 5:00 PM, Rick Hanson <cryptor...@gmail.com> wrote:
> Duh! That's it! And it even says x86 in the name!!! (e.g.
> `x86-64.sunOs.tgz`) I hereby turn in any computing creds I've garnered over
> the years to be thrown into burning inferno where they belong, and I'll go
> live in a box down my the river. :) Thanks!
> On Tue, Mar 3, 2015 at 4:50 PM, Jakob Eriksson <ja...@aurorasystems.eu>
>> You are not by any chance on a Sparc platform?
>> On 03/03/15 20:57, Rick Hanson wrote:
>> > Sorry in advance if you’ve already covered this issue in the past.
>> > I’m on Solaris 10; I can build the 32-bit picolisp (3.1.9) with no
>> > Then, I go do a (cd src64; make) (which is GNU make btw); this builds
>> > x86-64.sunOS.base.s file via mkAsm, but it fails in the next step on gas
>> > --64 (which reads the .s file) with a bunch of errors of the form
>> > Error: Unknown opcode: `$OP'
>> > where $OP is any one of several opcodes, e.g. adc, addq, clc, ja, jbe,
>> > movb, mul, etc.
>> > FIrst, I thought that a very old version of gas might be causing the
>> > (i.e. maybe it was not able to understand some of the new (?) opcodes;
>> > I was very optimistic :); so I downloaded, built and installed binutils
>> > (2.24.51) which gave me a new gas. The new gas was of no avail — the
>> > types of errors occurred.
>> > So, I then downloaded the .s files for Solaris from here:
>> > http://software-lab.de/x86-64.sunOs.tgz and unarced them in the
>> > directory. As you can imagine, this didn’t work either — the same
>> > opcode messages were appearing.
>> > I suspect that I’m making a very fundamental mistake here, but I can’t
>> > quite put my finger on it. Am I using gas wrongly, or do I have the
>> > assembler?
>> > Thanks for any help.
>> > —Rick
>> > rick42 on #picolisp
>> UNSUBSCRIBE: mailto:email@example.com?subject=Unsubscribe