[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug ld/23889] New: ld should prepend the sysroot path to absolute paths
From: |
andrew-swbz at shadura dot me |
Subject: |
[Bug ld/23889] New: ld should prepend the sysroot path to absolute paths in include directives |
Date: |
Thu, 15 Nov 2018 13:53:18 +0000 |
https://sourceware.org/bugzilla/show_bug.cgi?id=23889
Bug ID: 23889
Summary: ld should prepend the sysroot path to absolute paths
in include directives
Product: binutils
Version: 2.32 (HEAD)
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ld
Assignee: unassigned at sourceware dot org
Reporter: andrew-swbz at shadura dot me
Target Milestone: ---
Created attachment 11398
--> https://sourceware.org/bugzilla/attachment.cgi?id=11398&action=edit
fix-absolute-includes-with-sysroot.patch
According to the current code of ldconfig and ld, there's subtle
difference in parsing of /etc/ld.so.conf by these two tools:
* ldconfig interprets relative paths in includes relatively to the
current directory it run in, and absolute path relatively to the
current "chroot" directory, if set
* ld interprets relative paths in includes relatively to the directory
the parsed file is in, and apparently ignores the --sysroot setting
for absolute paths and does not relativise them to this sysroot.
Using relative paths in ld.so.conf breaks ldconfig (if the sysroot is chrooted
into), using absolute paths there breaks ld. The following patch changes the
behaviour of ld in this situation to match that of ldconfig.
--
You are receiving this mail because:
You are on the CC list for the bug.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Bug ld/23889] New: ld should prepend the sysroot path to absolute paths in include directives,
andrew-swbz at shadura dot me <=