after upgrading to gcc 4.6.0 and recompiling @world and @system i get this error when trying to start libreoffice /usr/lib64/libreoffice/program/soffice.bin: relocation error: /usr/lib64/libreoffice/program/libmergedlo.so: symbol _ZSt11__once_call, version GLIBCXX_3.4.11 not defined in file libstdc++.so.6 with link time reference i think i repackage is needed to get this relocation error fixed. Reproducible: Always
If the RH bug is a pointer, then this is a weird interaction from rebuilding gcc against a newer glibc...
recompiling gcc fixed the error
okay i found out what is causing this: i use /proc/sys/kernel/yama/ptrace_scope with tthe value "2" 2 - admin-only attach: only processes with CAP_SYS_PTRACE may use ptrace with PTRACE_ATTACH, or through children calling PTRACE_TRACEME. and i use FEATURES="userfetch userpriv usersandbox" so it is not possible to use ptrace. but when i compile gcc i get errors like this when ptrace_scope == 2 checking whether the target supports thread-local storage... * /tmp/tmerge/portage/sys-apps/sandbox-2.10-r4/work/sandbox-2.10/libsandbox/trace.c:_do_ptrace():74: failure (Operation not permitted): * ISE:_do_ptrace: ptrace(PTRACE_TRACEME, ..., 0x0000000000000000, 0x0000000000000000): Operation not permitted i noticed the failures also sometimes when compiling other apps and some of them brake when compiling with ptrace_scope == 2
okay i found out what is causing this: i use /proc/sys/kernel/yama/ptrace_scope with tthe value "2" 2 - admin-only attach: only processes with CAP_SYS_PTRACE may use ptrace with PTRACE_ATTACH, or through children calling PTRACE_TRACEME. and i use FEATURES="userfetch userpriv usersandbox" so it is not possible to use ptrace. but when i compile gcc i get errors like this when ptrace_scope == 2 checking whether the target supports thread-local storage... * /tmp/tmerge/portage/sys-apps/sandbox-2.10-r4/work/sandbox-2.10/libsandbox/trace.c:_do_ptrace():74: failure (Operation not permitted): * ISE:_do_ptrace: ptrace(PTRACE_TRACEME, ..., 0x0000000000000000, 0x0000000000000000): Operation not permitted this happens a lot of times: # grep -i ptrace emerge.output|wc -l 56 i noticed the failures also sometimes when compiling other apps and some of them brake when compiling with ptrace_scope == 2 and FEATURES="userpriv usersandbox"
okay i found out what is causing this: i use /proc/sys/kernel/yama/ptrace_scope with tthe value "2" 2 - admin-only attach: only processes with CAP_SYS_PTRACE may use ptrace with PTRACE_ATTACH, or through children calling PTRACE_TRACEME. and i use FEATURES="userfetch userpriv usersandbox" so it is not possible to use ptrace. but when i compile gcc i get errors like this when ptrace_scope == 2 checking whether the target supports thread-local storage... * /tmp/tmerge/portage/sys-apps/sandbox-2.10-r4/work/sandbox-2.10/libsandbox/trace.c:_do_ptrace():74: failure (Operation not permitted): * ISE:_do_ptrace: ptrace(PTRACE_TRACEME, ..., 0x0000000000000000, 0x0000000000000000): Operation not permitted this happens a lot of times: # grep -i ptrace emerge.output|wc -l 56 i noticed the failures also sometimes when compiling other apps and some of them brake when compiling with ptrace_scope == 2 and FEATURES="userpriv usersandbox" compiling gcc with ptrace_scope set to 0 solves the relocation error for libreoffice-bin i think the user should at least get a warining when compiling gcc with FEATURES="userpriv usersandbox" and ptrace_scope == 2
sorry for the reposts - please ignore Comment 3 & 4
can someone please assign this to the portage and gcc people?
closing this bug and opened a new bug #640698 as this bug is connected to the wrong component
