From: kokamoto@hera.eonet.ne.jp
To: 9front@9front.org
Subject: Re: [9front] 5l problem on python276 compilation
Date: Sun, 12 Jul 2020 09:22:24 +0900 [thread overview]
Message-ID: <5EB5AF0588D8EBB0BFFE4384BBA06D45@hera.eonet.ne.jp> (raw)
In-Reply-To: <91DD69073E2788CF105B0444B1B590CD@hera.eonet.ne.jp>
[-- Attachment #1: Type: text/plain, Size: 86 bytes --]
I forgot to update the 5l sources, obj.c was updated
at May 2020.
Sorry noise
Kenji
[-- Attachment #2: Type: message/rfc822, Size: 3024 bytes --]
From: kokamoto@hera.eonet.ne.jp
To: 9front@9front.org
Subject: Re: [9front] 5l problem on python276 compilation
Date: Sun, 12 Jul 2020 07:28:46 +0900
Message-ID: <91DD69073E2788CF105B0444B1B590CD@hera.eonet.ne.jp>
I forgot to include the 5l line which caused this error:
mk
pcc -o 5.out config-arm.5 python.5 libpython.a5 libz.a5 libbz2.a5 /arm/lib/ape/libmp.a /arm/lib/ape/libsec.a /arm/lib/ape/lib9.a
/5l 511: suicide: sys: alignment: pc 0x9cac va 0x1ff7c1
pc=0x9cac
pcc: 5l: 5l 511: sys: alignment: pc 0x9cac va 0x1ff7c1
pc=0x9cac
mk: pcc -o ... : exit status=rc 508: pcc 510: 5l: 5l 511: sys: alignment: pc 0x9cac va 0x1ff7c1
pc=0x9cac
mk: @{ cd ... : exit status=rc 450: rc 452: mk 453: error
term% acid 542 (542 is 5l process number)
/proc/542/text:arm plan 9 executable
/sys/lib/acid/port
/sys/lib/acid/arm
acid: stk()
ldobj(f=0x4,pn=0x3ffffd54,c=0x6d0)+0x8cc /sys/src/cmd/5l/obj.c:1054
objfile(file=0x3fffff55)+0x4f8 /sys/src/cmd/5l/obj.c:415
main(argc=0x9,argv=0x3fffff14)+0x32c /sys/src/cmd/5l/obj.c:242
_main+0x28 /sys/src/libc/arm/main9.s:19
acid:
Kenji
next prev parent reply other threads:[~2020-07-12 0:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-11 22:10 kokamoto
2020-07-11 22:28 ` [9front] " kokamoto
2020-07-12 0:22 ` kokamoto [this message]
2020-07-12 0:22 kokamoto
2020-07-12 5:29 ` kokamoto
2020-07-12 5:38 ` ori
2020-07-12 23:30 ` kokamoto
2020-07-13 2:42 ` kokamoto
2020-07-13 3:20 ` ori
2020-07-14 4:58 ` kokamoto
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=5EB5AF0588D8EBB0BFFE4384BBA06D45@hera.eonet.ne.jp \
--to=kokamoto@hera.eonet.ne.jp \
--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).