On Monday, 11 May 2020 16:37:31 UTC-4, Ian Lance Taylor wrote: > On Mon, May 11, 2020 at 8:45 AM Randall Becker <the....@gmail.com > <javascript:>> wrote: > > > > I know the subject has been covered for other platforms, but this one > (HPE NonStop TNS/X) has a few quirks. > > > > The platform does not support gcc at all. Many have spent years trying > unsuccessfully to port gcc. > > The platform does support a solid and POSIX compliant implementation of > c99 and C libraries. > > There are windows-based c99 cross-compilers that work well for the > platform. > > There is also a windows-based linker for the platform. > > Cross-compiled gcc code will not run on the platform. > > The platform is x86-64 bit, but it runs big-endian. > > Intermediate and executable object files are in ELF format, but with > some variation of values in the header that the linker handles. > > > > Is there a direction that I should take in looking at the port? Try > native or cross-compiling? > > > > I need GO because there is a really important package written in it that > I want to have on the platform. It is too big to port to another language, > but that might be my backup plan. Am I out of luck or is there hope for > this? > > Go only requires a C compiler if you want to support cgo. If the > package that you care about is pure Go, then the C compiler and linker > shouldn't matter. You won't need them. > > You'll have to start by cross-compiling from some other platform. The > Go tools are written in Go, so you need to bootstrap starting on some > other platform. > > You'll need to change cmd/link to generate an ELF file that your > platform can run. You'll likely need to change the compiler and > assembler for the fact that your platform is big-endian. That might > be simple, or it might be hard, I'm not sure. > > It's hard to answer general questions like "what direction should I > take," but we'll be happy to answer specific questions as best we can. > Thanks Ian.
I have the go repository with release-branch.go1.4 checked out on a Windows/cygwin64 installation. Looking for the bootstrap.bash and not finding one in that branch. Assuming that my eventual target will be called nsx (rather the standard name for other open source projects), would this be amd64 as a starting point, or does that not matter? Not sure about the next step. make.bat to build for Windows first? Regards, Randall -- 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/25aef544-0b72-425e-b003-af54c6b9cc89%40googlegroups.com.
