-
Notifications
You must be signed in to change notification settings - Fork 17.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dist: build binary distros with oldest possible glibc #5203
Labels
Milestone
Comments
FWIW, I looked at this again: http://stackoverflow.com/questions/8823267/linking-against-older-symbol-version-in-a-so-file You can replace all direct memcpys with memmoves in cmd/* to try to avoid the 2.2.5 -> 2.14 issue. However, you still run into problems, e.g., Bconv calls strcat which gets inlined as a call to memcpy by gcc. |
Owner changed to @adg. |
Dave, at the risk of murking the waters some more, I can say the 1.0.3 release tarball is working for me (but not the 1.1beta1) on a Scientific Linux 6 host (which is, as CentOS, based on a RHEL-6) $ uname -a Linux voatlas04.cern.ch 2.6.32-279.11.1.el6.x86_64 #1 SMP Tue Oct 16 17:21:52 CEST 2012 x86_64 x86_64 x86_64 GNU/Linux $ objdump -p /lib64/libc-2.12.so /lib64/libc-2.12.so: file format elf64-x86-64 [...] Version References: required from ld-linux-x86-64.so.2: 0x0963cf85 0x00 19 GLIBC_PRIVATE 0x0d696913 0x00 18 GLIBC_2.3 hth, sebastien. |
Care to try this one? https://code.google.com/p/go/downloads/detail?name=go1.1beta2.linux-amd64.tar.gz |
go1.1beta2.linux-amd64.tar.gz works for me on CentOS 5.9 and 6.4. It segfaults on one of the servers running 5.9, but works fine on two others. The same thing happens when I run all.bash: ... pkg/go/doc pkg/go/build cmd/go ./make.bash: line 137: 31048 Segmentation fault "$GOTOOLDIR"/go_bootstrap clean -i std It's a fairly old server and I'm not familiar with its configuration. It's probably a separate issue, but the the gdb backtrace is below: (gdb) run Starting program: /usr/local/go/bin/go warning: no loadable sections found in added symbol-file system-supplied DSO at 0x2aaaaaaab000 [Thread debugging using libthread_db enabled] Program received signal SIGSEGV, Segmentation fault. 0x00002aaaaaaab767 in ?? () (gdb) bt #0 0x00002aaaaaaab767 in ?? () #1 0x000000000046a02a in runtime.nanotime () at /usr/local/go/src/pkg/runtime/sys_linux_amd64.s:140 #2 0x0000000000458355 in MHeap_FreeLocked (h=void, s=void) at /usr/local/go/src/pkg/runtime/mheap.c:311 #3 0x000000000045812d in MHeap_Grow (h=void, npage=void) at /usr/local/go/src/pkg/runtime/mheap.c:230 #4 0x0000000000457e8d in MHeap_AllocLocked (h=void, npage=void, sizeclass=void) at /usr/local/go/src/pkg/runtime/mheap.c:108 #5 0x0000000000457b0e in runtime.MHeap_Alloc (h=void, npage=void, sizeclass=void, acct=void, zeroed=void) at /usr/local/go/src/pkg/runtime/mheap.c:77 #6 0x000000000045255d in MCentral_Grow (c=void) at /usr/local/go/src/pkg/runtime/mcentral.c:203 #7 0x000000000045200e in runtime.MCentral_AllocList (c=void, n=void, pfirst=void) at /usr/local/go/src/pkg/runtime/mcentral.c:47 #8 0x0000000000451c53 in runtime.MCache_Alloc (c=void, sizeclass=void, size=void, zeroed=void) at /usr/local/go/src/pkg/runtime/mcache.c:24 #9 0x0000000000464835 in runtime.mallocgc (size=void, flag=void, dogc=void, zeroed=void) at /usr/local/go/src/pkg/runtime/malloc.goc:55 #10 0x0000000000464b2e in runtime.malloc (size=void) at /usr/local/go/src/pkg/runtime/malloc.goc:125 #11 0x000000000046534e in runtime.mallocinit () at /usr/local/go/src/pkg/runtime/malloc.goc:410 #12 0x000000000045bbb0 in runtime.schedinit () at /usr/local/go/src/pkg/runtime/proc.c:129 #13 0x000000000046929a in _rt0_amd64 () at /usr/local/go/src/pkg/runtime/asm_amd64.s:81 #14 0x0000000000000001 in ?? () #15 0x00007fffffffe3e8 in ?? () #16 0x0000000000000001 in ?? () #17 0x00007fffffffe3e8 in ?? () #18 0x0000000000000000 in ?? () |
I think this is the same issue: https://golang.org/issue/4402 The kernel in question is 2.6.18-238.1.1.el5. I wouldn't worry too much about it. I just picked a box at random to run the glibc test. Not using it for anything go-related otherwise. |
This issue was closed.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
by elij.mx:
The text was updated successfully, but these errors were encountered: