Maybe a red herring, but you do have GOROOT='/usr/local/go122' in the output of go env in your original post.
..mark On Tuesday, September 3, 2024 at 10:40:58 AM UTC-7 Martin Stiemerling wrote: > > > > Am 03.09.2024 um 19:27 schrieb Ian Lance Taylor <ia...@golang.org>: > > > > On Tue, Sep 3, 2024 at 10:25 AM Martin Stiemerling > > <mstiem...@gmail.com> wrote: > >> > >>> Am 03.09.2024 um 19:19 schrieb Ian Lance Taylor <ia...@golang.org>: > >>> > >>> On Tue, Sep 3, 2024 at 10:07 AM Martin Stiemerling > >>> <mstiem...@gmail.com> wrote: > >>>> > >>>> > >>>> > >>>>> Am 03.09.2024 um 18:50 schrieb Ian Lance Taylor <ia...@golang.org>: > >>>>> > >>>>> On Tue, Sep 3, 2024 at 9:03 AM Martin Stiemerling > >>>>> <mstiem...@gmail.com> wrote: > >>>>>> > >>>>>> FreeBSD has since a while also support for the netlink facility, > similar to Linux. For Linux there is support in go via the syscall pkg for > working with Linux's netlink, but not yet for FreeBSD > >>>>>> > >>>>>> I have started to add the FreeBSD part to go's syscall package and > fixed some errors, but run into troubles when compiling go. Though my > approach is by now copying a lot form syscall_linux, as a first naive > approach. :-) > >>>>>> > >>>>>> When using make.bash these steps work: > >>>>>> Building Go cmd/dist using /usr/local/go122. (go1.22.6 > freebsd/amd64) > >>>>>> Building Go toolchain1 using /usr/local/go122. > >>>>>> Building Go bootstrap cmd/go (go_bootstrap) using Go toolchain1 > >>>>>> > >>>>>> However, after "Building Go toolchain2 using go_bootstrap and Go > toolchain1" this error turns out: > >>>>>> "go: cannot find GOROOT directory: /home/mls/goworks > >>>>>> go tool dist: FAILED: > /home/mls/goworks/pkg/tool/freebsd_amd64/go_bootstrap install -pgo=off > cmd/asm cmd/cgo cmd/compile cmd/link cmd/preprofile: exit status 2" > >>>>> > >>>>> Where does the directory /home/mls/goworks come from? Does it exist? > >>>> > >>>> /home/mls/goworks exists and under /home/mls/goworks/src is the go > source code. > >>>> > >>>>> > >>>>> Do you have GOROOT set in the environment? > >>>> > >>>> Nope, no environment set, as described under > https://go.dev/doc/install/source#environment. > >>>> > >>>> Interestingly does the whole process just run through, with the same > setting, i.e., no GOROOT set, without my modifications (master branch). > >>>> > >>>> I guess something goes wrong and the binaries under > /home/mls/goworks/bin are not generated. > >>>> > >>>> Thus the assumed GOROOT of the build process, i.e., /home/mls/goworks > and $GOROOT/bin, doesn’t work. > >>>> > >>>> However, I cannot see any error message or warning... > >>> > >>> Thanks. My conclusion is that this must have something to do with > >>> your changes. I saw that you posted your complete tree, but is there > >>> an easy way to see only what you changed? > >> > >> Here you go: > >> > https://code.fbi.h-da.de/m.stiemerling/go/-/compare/master...freebsd-netlink?from_project_id=36647&straight=false > > > > Thanks. I'm sorry, I don't see anything there that could be causing > > the problems you describe. I don't know what is happening. > > Thanks a lot! > > I am also clueless, especially as there is no error message etc telling > why, or where, it is breaking. > > Martin -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/6b004c80-7b34-4a01-b486-0ce5f8bc7a5cn%40googlegroups.com.
