I did not. Go built successfully after enabling the v9fs mmap caching on mount!
- started diod like this: sudo ./diod -f -d 1 -n -e /home/fst/SRC/tmp - mounted it like this: sudo mount -t 9p -n 127.0.0.1 /mnt/overdiod -o aname=~/SRC/tmp,version=9p2000.L,uname=root,access=user,cache=mmap - and built go $ cd /mnt/overdiod/go/src/ $ mkdir /tmp/go1.17 $ GOROOT_FINAL=/tmp/go1.17 GOROOT_BOOTSTRAP=~/SRC/go1.4 GOOS=plan9 GOARCH=386 ./make.bash Building Go cmd/dist using /home/fst/SRC/go1.4. (go1.4-bootstrap-20170531 linux/amd64) Building Go toolchain1 using /home/fst/SRC/go1.4. Building Go bootstrap cmd/go (go_bootstrap) using Go toolchain1. Building Go toolchain2 using go_bootstrap and Go toolchain1. Building Go toolchain3 using go_bootstrap and Go toolchain2. Building packages and commands for host, linux/amd64. Building packages and commands for target, plan9/386. --- Installed Go for plan9/386 in /mnt/overdiod/go Installed commands in /mnt/overdiod/go/bin The binaries expect /mnt/overdiod/go to be copied or moved to /tmp/go1.17 $ On Wed, Oct 27, 2021 at 1:28 AM Richard Miller <9f...@hamnavoe.com> wrote: > > I think the question is why mmap works over 9p from linux up to a point but > > then fails in some context: what's the difference? > > Skip, did you specify -o cache=mmap when mounting diod service > for the go build experiment? > ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Tb065f4df67a8bab9-M356c116a7b0042098c4c3b89 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
