Re: Hugo go-vendor-tools package

2025-06-04 Thread W. Michael Petullo via golang
> > Sorry for the late replies, I've been busier than expected last week. > > For that error I found that Brad already hit the same issue in > https://github.com/cri-o/cri-o/issues/8860#issuecomment-2558287657 and > fixed by applying "%global __golang_extldflags -Wl,-z,undefs" after > %build in

Re: Hugo go-vendor-tools package

2025-06-03 Thread Mikel Olasagasti via golang
Hi Mike, Sorry for the late replies, I've been busier than expected last week. For that error I found that Brad already hit the same issue in https://github.com/cri-o/cri-o/issues/8860#issuecomment-2558287657 and fixed by applying "%global __golang_extldflags -Wl,-z,undefs" after %build in https

Hugo go-vendor-tools package

2025-05-29 Thread W. Michael Petullo via golang
Mikel, I am still experimenting with building a Hugo package using go-vendor-tools. I have had some success, but the github.com/tetratelabs/wazero dependency is causing problems. Looking at the wazero .spec, the build has some special requirements, but I do not know how to apply these to wazero as