From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] Error compiling libc/amd64/main9.s and/or main9p.s
Date: Tue, 26 Mar 2024 12:46:11 -0400 [thread overview]
Message-ID: <C99FD9DAAB224E9A46C051572FA96121@eigenstate.org> (raw)
In-Reply-To: <6bdb9a35-067c-41b6-a415-8845cc27f10e@app.fastmail.com>
https://inbox.vuxu.org/9front/d9bdf2b5-8da3-4cc7-8f18-40bc3a5d0a84@posixcafe.org/T/#u
note, you can also grab the latest compilers from the nightly builder:
9fs iso
cp /n/iso/amd64/bin/6^(a c l) /amd64/bin
Quoth Scott Flowers <flowerss@cranky.ca>:
> I ran a sysupdate this morning and it won't build on amd64. It's hanging on /sys/src/libc/amd64/main9.s with an error like below.
>
> 6a main9.s
> 6a main9p.s
> main9.s:6 main9p.s:6 syntax error, last name: _callmain
> syntax error, last name: _callmain
> line: LNAME.: $$5 line
> inst: LNAME.= expr
> line: LNAME.: $$5 line
> inst: LNAME.= expr
> saw LNAME
> saw LNAME
> mk: 6a main9.s : exit status=6a 692473: error
> mk: for(i in 9sys ... : exit status=rc 691919: mk 692470: error
> mk: date for (i ... : exit status=rc 691888: mk 691918: error
>
> I tried doing mk nuke, and then mk libs, and it fails at the same place, like this.
>
> 6a main9.s
> main9.s:6 6a main9p.s
> syntax error, last name: _callmain
> line: LNAME.: $$5 line
> inst: LNAME.= expr
> main9p.s:6 saw LNAME
> syntax error, last name: _callmain
> mk: 6a main9.s : exit status=6a 703834: errorline: LNAME.: $$5 line
> inst: LNAME.= expr
>
> saw LNAME
> mk: for(i in 9sys ... : exit status=rc 703070: mk 703825: error
> mk: date for (i ... : exit status=rc 702782: rc 702983: mk 703068: error
>
> Any suggestions?
>
> Thanks!
>
> Scott Flowers
next prev parent reply other threads:[~2024-03-26 16:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 16:37 Scott Flowers
2024-03-26 16:46 ` ori [this message]
2024-03-26 16:51 ` Jacob Moody
2024-03-26 17:15 ` Scott Flowers
2024-03-27 0:22 ` sl
2024-03-27 14:55 ` Scott Flowers
2024-03-27 15:16 ` Jacob Moody
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=C99FD9DAAB224E9A46C051572FA96121@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.org \
/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).