[go-nuts] wrong ELF class error: How to compile 64 bit binary on Solaris 11 using gccgo

Hi, I am trying to compile a 64bit executable using gccgo on Solaris 11/10. Following is what I have tried: CGO_LDFLAGS='-m64' go build hello_world.go GOARCH=sparc64 CGO_LDFLAGS='-m64' go build hello_world.go Below is the output of the first command: amandeep@s113ldom1:~/workspace$

Re: [go-nuts] internal compilation error while compiling gccgo from source solaris 10

t > > /export/home/amandeep/gccgo-src/gcc/go/gofrontend/gogo.h:3200 > > #20 0x001ecd2c in Gogo::check_types (this=0x10f0438) at > > /export/home/amandeep/gccgo-src/gcc/go/gofrontend/gogo.cc:3316 > > #21 0x001e7700 in go_parse_input_files (filenames=0x10cf4a8, > &g

Re: [go-nuts] internal compilation error while compiling gccgo from source solaris 10

propriate. Please include the complete backtrace with any bug report. See <https://gcc.gnu.org/bugs/> for instructions. On Thursday, August 23, 2018 at 2:54:56 PM UTC-7, Amandeep Gautam wrote: > > Running inside the gdb worked. Seems like a problem with libmpfr. Will try > compiling it from

Re: [go-nuts] internal compilation error while compiling gccgo from source solaris 10

in toplev::main(int, char**) () at ./insn-modes-inline.h:38 #25 0x00e1e1e4 in main (argc=21, argv=0xffbffa44) at /export/home/amandeep/gccgo-src/gcc/main.c:39 On Thursday, August 23, 2018 at 2:25:38 PM UTC-7, Ian Lance Taylor wrote: > > On Thu, Aug 23, 2018 at 2:14 PM, Amandeep Gautam &g

Re: [go-nuts] internal compilation error while compiling gccgo from source solaris 10

bugging session? (y or n) n frame.c:472: internal-error: get_frame_id: Assertion `fi->this_id.p' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Create a core file of GDB? (y or n) y Command aborted. Have I steps mentioned correctly? Any suggestions on t

Re: [go-nuts] internal compilation error while compiling gccgo from source solaris 10

8 at 9:39 PM, Amandeep Gautam > > wrote: > > > gmake[3]: Entering directory > > '/export/home/amandeep/gccgo-obj/sparc-sun-solaris2.10/libgo' > > gmake[4]: Entering directory > > '/export/home/amandeep/gccgo-obj/sparc-sun-solaris2.10/libgo' > > /opt/csw/bin/

[go-nuts] internal compilation error while compiling gccgo from source solaris 10

I have been trying to install GCCGO on Solaris 10 with the following script: dir=/export/home/amandeep srcdir=$dir/gccgo-src objdir=$dir/gccgo-obj prefix=/usr/gnu # Create Directory mkdir -p $objdir sudo mkdir -p $prefix # Exports export

[go-nuts] unrecognized import paths error while using go get

Hi, I installed gccgo on Solaris 11.3 using: sudo /opt/csw/bin/pkgutil -y -i gcc5core Below is the output of go-5.5 env: amandeep@s113ldom1:~$ go-5.5 env GOARCH="sparc" GOBIN="" GOCHAR="" GOEXE="" GOHOSTARCH="sparc" GOHOSTOS="solaris" GOOS="solaris" GOPATH="/home/amandeep/" GORACE=""

[go-nuts] Pdeathsig alternate for other operating systems

I am writing a process monitoring solution in go for AIX. I would like to signal the child process when the parent dies so that it does not become orphaned. In linux, one can set PdeathSig (https://golang.org/pkg/syscall/#SysProcAttr) and Go will take care of the rest. However this attribute

[go-nuts] Is there an equivalent of telldir in go. If not what are the alternatives?

Is there a equivalent of telldir in golang which can page reading of a directory. Just using filepath.walk would be inefficient for large file systems. >From one of the answers to this question https://stackoverflow.com/questions/39583522/how-do-i-use-seekdir-telldir-in-golang it looks like

[go-nuts] Client and server stub not generated for grpc-go

I am trying to write a grpc server in go but am unable get the generated client and server stub in the file generated by plugin. Here is the paste of the file generated: https://pastebin.com/kfi99MxK >From what I have researched, it is because of faulty protobuf installation but I am not sure

Re: [go-nuts] gRPC go on AIX

I am using precompiled binaries for AIX. But will keep your suggestion in mind. For now it was fixed by installing ca certificates. On Thursday, December 21, 2017 at 3:12:50 PM UTC-8, Ian Lance Taylor wrote: > > On Thu, Dec 21, 2017 at 1:43 PM, > wrote: > > > >