From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: [9fans] Failure building Inferno
Date: Sat, 10 Jan 2015 08:33:50 +0200 [thread overview]
Message-ID: <d6e4b64ba1db894e986e6745f78c5bf2@proxima.alt.za> (raw)
The eventual objective is to have the MIPS(EL) toolchain in place on
my Yeeloong notebook, but it's quite promising that building Inferno
can progress as far as it did with minimal adjustments (Linux/spim).
The GCC compiler, however, complains:
asm-spim.S: Assembler messages:
asm-spim.S:50: Error: opcode not supported on this processor: mips1 (mips1) `ll $2,0($4)'
asm-spim.S:52: Error: opcode not supported on this processor: mips1 (mips1) `sc $9,0($4)'
mk: gcc -c asm-spim.S : exit status=exit(1)
I had to drop the -mips32 command line flag to gcc because iyacc
failed on an invalid instruction. I compared mk (which worked, of
course) and iyacc and the architectures were MIPS-I and MIPS32
respectively. Then everything up to the assembly above worked fine.
I added -march=native and -mtune=native (which the compiler translates
to -march=loongson2f and -mtune=loongson2f) and the inferno
installation completed successfully. There may be one or two warnings
worth fixing, but first I want to do some testing.
Lucio.
reply other threads:[~2015-01-10 6:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d6e4b64ba1db894e986e6745f78c5bf2@proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).