bug-gettext
[Top][All Lists]
Advanced

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

[bug #61769] building libasprintf does not honour RPATH configure option


From: Bruno Haible
Subject: [bug #61769] building libasprintf does not honour RPATH configure option --disable-rpath
Date: Sat, 25 Jun 2022 16:08:51 -0400 (EDT)

Update of bug #61769 (project gettext):

                  Status:               Need Info => Works For Me           
             Assigned to:                    None => haible                 
             Open/Closed:                    Open => Closed                 

    _______________________________________________________

Follow-up Comment #3:

1) When I build, on Ubuntu 22.04, gettext 0.21
  - once with CC=gcc, CXX=g++,
  - once with CC="gcc -fuse-ld=gold", CXX="g++ -fuse-ld=gold",
I obtain identical results: --disable-rpath has the desired effect.

$ readelf --dynamic
build-64.ld/gettext-runtime/libasprintf/.libs/libasprintf.so | grep PATH
$ readelf --dynamic
build-64.gold/gettext-runtime/libasprintf/.libs/libasprintf.so | grep PATH


Therefore, I'm closing this ticket as "works for me".

Nevertheless, here are two more findings:

2) When I look at your gettext-runtime/libasprintf/config.log, I see the
lines

configure:11347: checking for ld used by
/var/media/DATA/home-rudi/LibreELEC.tv/build.LibreELEC-Generic.x86_64-11.0-devel/toolchain/bin/x86_64-libreelec-linux-gnu-g++
configure:11414: result:
/var/media/DATA/home-rudi/LibreELEC.tv/build.LibreELEC-Generic.x86_64-11.0-devel/toolchain/bin/x86_64-libreelec-linux-gnu-ld
-m elf_x86_64 -m elf_x86_64

That is, the libtool configuration guessed wrong about the linker. The reason
is that you have put the -fuse-ld=gold option into the LDFLAGS, not the CC and
CXX variables. The documentation at
https://www.gnu.org/savannah-checkouts/gnu/autoconf/manual/autoconf-2.71/html_node/Preset-Output-Variables.html
says "one approach is to put the option into CC. Another is to put it into
both CPPFLAGS and LDFLAGS, but not into CFLAGS." But apparently for this
particular option, putting it into CC and CXX is the better choice.

3) In the same file, I also see the lines

configure:13157: checking if
/var/media/DATA/home-rudi/LibreELEC.tv/build.LibreELEC-Generic.x86_64-11.0-devel/toolchain/bin/x86_64-libreelec-linux-gnu-g++
static flag -static works
configure:13185: result: no

That result should be 'yes'. This points to an issue with your cross-compiler
installation.



    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?61769>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/




reply via email to

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