From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id D35D63858D39; Mon, 3 Apr 2023 19:09:18 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D35D63858D39 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1680548958; bh=Bg9siRwNeWWt8gdos8OZ1gVJKGQjS6O0ByU2NvI09Hg=; h=From:To:Subject:Date:In-Reply-To:References:From; b=VlPjQDDPKHdDzdFtO8/cpedad7XCXlmxf7PzReswE0o5PkRkk0lTxVl+aGZpf3HnH /CYm41wh/6juD6lMR5ovLN27fNq/6wu+V2GN4MVNWXH8ySm8fIvezJS4wwNa2tidRY BSLXD52W/CNtwiQkEYwSJjqBsESuDJLGwjw3GvOA= From: "jason.vas.dias at gmail dot com" To: glibc-bugs@sourceware.org Subject: [Bug libc/30306] ld.so.conf could easily / should support binary specific LD_PATH directory search path settings ? Date: Mon, 03 Apr 2023 19:09:18 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: libc X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: jason.vas.dias at gmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D30306 --- Comment #3 from Jason Vas Dias --- RE: Comment #2:=20 > Why can't you just add /usr/local/lib64 unconditionally to /etc/ld.so.con= f? Thanks, Andreas -=20 Because there may be many other libraries in /usr/local/lib64 - in fact, there is a libgcc-shared.so and a libstdc++.so.6 in /usr/local/lib64, which I'd rather not pick up at all - I want to be able to move libbpf's libraries to some /usr/local/libbpf-v1.1.0/lib64 directory , and specify that they apply ONLY to links needed for /usr/bin/perf, I do NOT want these updated libbpf* links to update the system libbpf at all, which MUST remain at v0.7.0, else everything that uses libbpf (except perf) will break . It just seems to me that having some very simple extra config in ld.so.conf, to apply a LD_PATH only to certain executables, would prevent a whole host of error prone disasters involved=20 with binary patching in of a DT_RUNPATH ELF note . --=20 You are receiving this mail because: You are on the CC list for the bug.=