From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@9fans.net
Subject: [9fans] v9fs vs mmap
Date: Sun, 24 Oct 2021 12:03:21 +0100 [thread overview]
Message-ID: <9b84409d162620992983e1eea6171490@hamnavoe.com> (raw)
I'm trying to cross-compile go for plan9-386 using go-linux-amd64
(on a linux laptop) with the source tree mounted from a plan 9 server
via v9fs (mount -t 9p).
All goes well up to a point, then this happens:
/mnt/sys/lib/go1.17/pkg/tool/linux_amd64/link: mapping output file failed: invalid argument
It appears the go linker is now using mmap on its output file,
so it can write to different object code sections at multiple
offsets.
Should this be expected to work? Or is mmap not supported over v9fs?
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T386b893f614f2b23-Ma99850de6a262031ebd727dc
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next reply other threads:[~2021-10-24 11:03 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-24 11:03 Richard Miller [this message]
2021-10-24 19:50 ` [9fans] v9fs vs mmap (SOLVED) Richard Miller
2021-10-24 22:31 ` Conor Williams
2021-10-25 11:04 ` [9fans] v9fs vs mmap (not quite SOLVED) Richard Miller
2021-10-25 23:53 ` Conor Williams
2021-10-26 9:22 ` Richard Miller
2021-10-26 10:51 ` Richard Miller
2021-10-26 15:53 ` Dan Cross
2021-10-26 16:06 ` Conor Williams
2021-10-26 16:51 ` Richard Miller
2021-10-26 18:17 ` Skip Tavakkolian
2021-10-26 18:54 ` Conor Williams
2021-10-26 19:09 ` Richard Miller
2021-10-26 19:33 ` Skip Tavakkolian
2021-10-26 19:36 ` Skip Tavakkolian
2021-10-26 23:45 ` Skip Tavakkolian
2021-10-26 23:57 ` Charles Forsyth
2021-10-27 8:27 ` Richard Miller
2021-10-27 10:55 ` Richard Miller
2021-10-27 12:31 ` Dan Cross
2021-10-27 13:15 ` Richard Miller
2021-10-27 13:20 ` Dan Cross
2021-10-27 14:10 ` Richard Miller
2021-10-27 14:14 ` arnold
2021-10-27 14:39 ` Richard Miller
2021-10-27 14:45 ` arnold
2021-10-27 14:31 ` Dan Cross
2021-10-27 15:02 ` Bakul Shah
2021-10-27 15:37 ` Charles Forsyth
2021-10-27 16:34 ` Skip Tavakkolian
2021-10-27 18:37 ` Richard Miller
2021-10-27 19:12 ` Skip Tavakkolian
2021-10-27 19:30 ` [9fans] v9fs vs mmap (now SOLVED, we hope) Richard Miller
2021-10-27 20:18 ` Skip Tavakkolian
2021-11-03 14:44 ` Conor Williams
2021-11-03 16:39 ` Conor Williams
2021-11-01 2:58 ` [9fans] v9fs vs mmap (not quite SOLVED) Conor Williams
2021-11-04 0:32 ` Conor Williams
2021-11-04 3:15 ` Conor Williams
2021-11-04 11:49 ` Conor Williams
2021-11-05 3:16 ` Conor Williams
2021-11-05 10:21 ` Kenji Okamoto
2021-11-05 13:44 ` Conor Williams
2021-11-05 13:56 ` Conor Williams
2021-11-21 4:21 ` Conor Williams
2021-10-27 0:34 ` Conor Williams
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=9b84409d162620992983e1eea6171490@hamnavoe.com \
--to=9fans@hamnavoe.com \
--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).