bug-gnu-libiconv
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bug-gnu-libiconv] rpath still set by libtool for iconv build even w


From: fred.heinecke
Subject: Re: [bug-gnu-libiconv] rpath still set by libtool for iconv build even with disable-rpath configuration flag is set
Date: Mon, 13 Nov 2023 13:27:42 -0600

Good catch. However, I get (effectively) the same results when using objdump
or readelf:

> objdump -x /tmp/build_output/usr/local/bin/iconv | grep "RUNPATH"
  RUNPATH              /tmp/build_output/usr/local/lib

> readelf -d /tmp/build_output/usr/local/bin/iconv | grep "RUNPATH"
0x000000000000001d (RUNPATH)            Library runpath:
[/tmp/build_output/usr/local/lib]

Thanks, Fred

-----Original Message-----
From: Bruno Haible <bruno@clisp.org> 
Sent: Monday, November 13, 2023 9:53 AM
To: bug-gnu-libiconv@gnu.org; Fred Heinecke <fred.heinecke@yahoo.com>
Subject: Re: [bug-gnu-libiconv] rpath still set by libtool for iconv build
even with disable-rpath configuration flag is set

Fred Heinecke wrote:
> strings /tmp/build_output/usr/local/bin/iconv | grep "/tmp/build_output"
# This shows "/tmp/build_output/usr/local/lib"

'strings' is not a reliable way to check for an RPATH in a binary.
Instead, you need to use
  objdump -x /tmp/build_output/usr/local/bin/iconv | grep RUNPATH or
  readelf -d /tmp/build_output/usr/local/bin/iconv | grep RUNPATH

Bruno






reply via email to

[Prev in Thread] Current Thread [Next in Thread]