From: Romano <unobe@cpan.org>
To: 9front@9front.org
Subject: Re: [9front] Cannot build system on latest rpi4 (libbio errors)
Date: Sat, 21 Nov 2020 14:27:29 -0800 [thread overview]
Message-ID: <B29181C6DC13B8181E5034BCEC55EF51@smtp.pobox.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 297 bytes --]
Not sure if it was meant to be required after Amavect's latest mk
changes, but I had to do this after updating to the latest commit. I
had followed FQA 5 to just do mk install under /sys/src, which wasn't
sufficient. I'll comment again if I need to do it down the road but
thought I'd mention it.
[-- Attachment #2: Type: message/rfc822, Size: 9445 bytes --]
From: ori@eigenstate.org
To: unobe@cpan.org, 9front@9front.org
Subject: Re: [9front] Cannot build system on latest rpi4 (libbio errors)
Date: Mon, 02 Nov 2020 12:55:12 -0800
Message-ID: <40159D135FE3FAB9F9029B243CC5BEF1@eigenstate.org>
> I ran sysupdate last night and attempted to rebuild the system, but it fails with some errors about libbio:
>
> cpu% cd /sys/src
> cpu% mk install
> ...
> 7l -o 7.out aliasmail.7 ../common/libcommon.a7
> ??none??: incompatible type signatures c0a3cfae(../common/libcommon.a7(sysnames_read)) and 9dd3ea4c(/arm64/lib/libbio.a(Bseek)) for Bseek
> badd: incompatible type signatures e8001435(../common/libcommon.a7(sysnames_read)) and 34728a43(/arm64/lib/libbio.a(Brdstr)) for Brdstr
> Binits: incompatible type signatures ac447a74(../common/libcommon.a7(sysnames_read)) and ce449e92(/arm64/lib/libbio.a(Bopen)) for Binit
> Bfdopen: incompatible type signatures 29f5223c(../common/libcommon.a7(sysnames_read)) and 63f5472a(/arm64/lib/libbio.a(Bopen)) for Bopen
> Bopen: incompatible type signatures bb9b2306(../common/libcommon.a7(sysnames_read)) and f9b3864(/arm64/lib/libbio.a(Bopen)) for Bterm
> ??none??: incompatible type signatures bb9b2306(../common/libcommon.a7(sysnames_read)) and f9b3864(/arm64/lib/libbio.a(Bfildes)) for Bfildes
> mk: 7l -o ... : exit status=rc 420270: 7l 420272: error
> mk: for (i in ... : exit status=rc 420228: rc 420265: mk 420266: error
> mk: for(i in 1a ... : exit status=rc 403330: rc 420225: mk 420227: error
> mk: test -e 7._cp ... : exit status=rc 401470: mk 403313: error
> mk: date for (i ... : exit status=rc 392586: rc 401452: mk 401453: error
> cpu%
>
> I attempted to resolve by first rebuilding /sys/src/cc, then /sys/src/7c, as mentioned in FQA 5. I then tried 'mk clean', and 'mk libs', and still no success. I would have thought that a 'mk clean' would have worked, but from the message above it looks like the build is using the system's libbio and it's expecting different type signatures. I looked at the commit log for 9front but didn't see anything recently that would modify libbio.
>
> The only reference I found on google is here, with a different project: https://github.com/Orc/discount/issues/193
Let me guess, that's upas? I think the mkfiles there need
another look -- I don't think we rebuild libcommon when
we should.
Try 'cd /sys/src/cmd/upas && mk nuke'.
next reply other threads:[~2020-11-21 22:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-21 22:27 Romano [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-11-22 4:07 Romano
2020-11-21 22:31 Romano
2020-11-22 2:29 ` ori
2020-11-22 3:29 ` Amavect
2020-11-22 4:07 ` Amavect
2020-11-02 21:00 Romano
2020-11-02 20:55 Romano
2020-11-02 20:49 Romano
2020-11-02 20:55 ` [9front] " ori
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=B29181C6DC13B8181E5034BCEC55EF51@smtp.pobox.com \
--to=unobe@cpan.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).