Hi Michael, Michael Gebetsroither <[email protected]> writes: > Can you please provide go cross-compilers as separate packages? > As go has native support for cross-compiling it would be very handy to > not have to build all the cross-compiler ourself from upstream source. > > eg. we used to build > CGO_ENABLE=1 ./all.bash > GOOS=linux GOARCH=386 CGO_ENABLED=0 ./make.bash --no-clean > GOOS=linux GOARCH=arm CGO_ENABLED=0 ./make.bash --no-clean > GOOS=windows GOARCH=amd64 CGO_ENABLED=0 ./make.bash --no-clean > GOOS=windows GOARCH=386 CGO_ENABLED=0 ./make.bash --no-clean > > clarification: this is for building a toolchain to cross-compile go > executables for other plattforms, not cross-compiling the go toolchain > for another plattform. > > idea: as from #go-nuts @ freenode, all cross-compilers can be build on > all plattforms. Thus why not create golang-go-$GOOS-$GOARCH packages and > let the debian arch native golang-go packages depend on the right one > for each architecture. I had planned to look into this anyway, but thanks for your detailed bugreport.
Andrew, do you see any issues with this or anything to watch out for? Or does this sound sane to you? -- Best regards, Michael -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
