Processed: Re: Bug#787227: broken on armel due to broken RUNPATH: /usr/lib/ghc/bin/ghc: error while loading shared libraries: libHShaskeline-0.7.1.2-ghc7.8.4.so: cannot open shared object file: No suc
Processing control commands: > retitle -1 ld-linux.so fails to expand relative RPATH when /proc is not > mounted Bug #787227 [libc6] ld-linux.so loads libraries from . when /proc is not mounted Changed Bug title to 'ld-linux.so fails to expand relative RPATH when /proc is not mounted' from 'ld-linux.so loads libraries from . when /proc is not mounted'. > tag -1 - security Bug #787227 [libc6] ld-linux.so fails to expand relative RPATH when /proc is not mounted Removed tag(s) security. -- 787227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787227 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Re: Bug#787227: broken on armel due to broken RUNPATH: /usr/lib/ghc/bin/ghc: error while loading shared libraries: libHShaskeline-0.7.1.2-ghc7.8.4.so: cannot open shared object file: No such file or d
control: retitle -1 ld-linux.so fails to expand relative RPATH when /proc is not mounted control: tag -1 - security Hi, On 2015-05-30 18:56, Helmut Grohne wrote: > Control: severity -1 wishlist > Control: reassign -1 libc6 > Control: retitle -1 ld-linux.so loads libraries from . when /proc is not > mounted > Control: affects -1 + ghc > Control: summary -1 0 > > When /proc is not mounted, a relative RPATH causes ld-linux.so to fall > back to using the working directory as the base directory for RPATH > resolution instead of using the (unknown) location of the executed > binary. This issue is hard to diagnose, because the error message does > not make it clear that fallback code is in use due to readlink > /proc/self/exe failing. Furthermore, it may pose a security risk by > loading libraries from unintended locations. The fact that it replaces $ORIGIN by the current directory when /proc is not mounted is one part of the issue. It has already been tracked and fixed in #884615. > On Sat, May 30, 2015 at 11:54:26AM -0400, Joey Hess wrote: > > Sorry, I meant the linker should be fixed, not ghc. > > Let's codify that in the bts. > > Steps to reproduce (for glibc maintainers): > > Create an unstable chroot. Install ghc. Do not mount /proc in that > chroot. Execute /usr/bin/ghc. You shall see that it fails loading > libraries. > > I assume that any binary with a relative RPATH is affected. This is the second part of the issue. The dynamic loader has no way to find the location of the binary without a mounted /proc, that's why it fails to find the GHC libraries. Retitling / tagging the bug accordingly. Regards, Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
[Git][glibc-team/glibc][glibc-2.33] debian/patches/any/submitted-localedef-check-magic.patch: rename into...
Aurelien Jarno pushed to branch glibc-2.33 at GNU Libc Maintainers / glibc Commits: 856bb24e by Aurelien Jarno at 2021-12-10T21:53:51+01:00 debian/patches/any/submitted-localedef-check-magic.patch: rename into git-localedef-check-magic.patch. - - - - - 3 changed files: - debian/changelog - debian/patches/any/submitted-localedef-check-magic.patch → debian/patches/any/git-localedef-check-magic.patch - debian/patches/series View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/commit/856bb24ec367f8e2f31cb4c15c93e2a2aa63fbc0 -- View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/commit/856bb24ec367f8e2f31cb4c15c93e2a2aa63fbc0 You're receiving this email because of your account on salsa.debian.org.
Bug#1001352: libc6-dev: pthread.h, setjmp.h: Include order matters (__sigsetjmp compilation error)
On 2021-12-08 23:46, Alejandro Colomar wrote: > Package: libc6-dev > Version: 2.32-5 > Severity: normal > Tags: upstream > X-Debbugs-Cc: alx.manpa...@gmail.com, libc-al...@sourceware.org, > u...@nginx.org > > Dear Maintainer, > > Building Nginx Unit from source results in a compilation error. > I tried both Debian 11 and Debian Sid (12), > and the bug is reproducible in Sid only. > > To reproduce the problem, install the following packages: > > git, build-essential, libpcre2-dev > > Then execute the following commands: > > git clone https://github.com/nginx/unit.git > cd unit/ > ./configure > make > > You will see the following error: > > > --- > > cc -c -pipe -fPIC -fvisibility=hidden -O -W -Wall -Wextra > -Wno-unused-parameter -Wwrite-strings -Wmissing-prototypes -Werror -g -I src > -I build \ > \ > \ > -o build/src/nxt_thread.o \ > -MMD -MF build/src/nxt_thread.dep -MT build/src/nxt_thread.o \ > src/nxt_thread.c > In file included from src/nxt_unix.h:187, > from src/nxt_main.h:31, > from src/nxt_thread.c:7: > src/nxt_thread.c: In function ‘nxt_thread_trampoline’: > src/nxt_thread.c:114:5: error: ‘__sigsetjmp’ accessing 200 bytes in a region > of size 72 [-Werror=stringop-overflow=] > 114 | pthread_cleanup_push(nxt_thread_time_cleanup, thr); > | ^~~~ > src/nxt_thread.c:114:5: note: referencing argument 1 of type ‘struct > __jmp_buf_tag *’ > /usr/include/pthread.h:734:12: note: in a call to function ‘__sigsetjmp’ > 734 | extern int __sigsetjmp (struct __jmp_buf_tag *__env, int __savemask) > __THROWNL; > |^~~ > cc1: all warnings being treated as errors The problem you encounter is due to the use of GCC 11. glibc headers need to be adapted for that. This has been done upstream in glibc 2.33, which is already available in experimental. It should arrive soon in sid. Using GCC 10 is another alternative. Regards, Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
[Git][glibc-team/glibc][glibc-2.33] debian/control.in/libc: drop ${locale-compat:Depends} leftover from Provides.
Aurelien Jarno pushed to branch glibc-2.33 at GNU Libc Maintainers / glibc Commits: 11bc360c by Aurelien Jarno at 2021-12-09T23:59:22+01:00 debian/control.in/libc: drop ${locale-compat:Depends} leftover from Provides. - - - - - 3 changed files: - debian/changelog - debian/control - debian/control.in/libc View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/commit/11bc360c6d1a048980a012a864d8182aa9e7dc43 -- View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/commit/11bc360c6d1a048980a012a864d8182aa9e7dc43 You're receiving this email because of your account on salsa.debian.org.