Re: [sr #109844] Do not override user's LD_LIBRARY_PATH in generated ltmain.sh for the build dir wrappers

Roumen Petrov <[email protected]>
Newsgroups gmane.comp.gnu.libtool.general
Message-ID <[email protected]>
anonymous wrote:
> URL:
>    <https://savannah.gnu.org/support/?109844>
>
>                   Summary: Do not override user's LD_LIBRARY_PATH in generated
> ltmain.sh for the build dir wrappers
>                   Project: GNU Libtool
>              Submitted by: None
>              Submitted on: Sat 13 Jul 2019 09:50:51 AM UTC
>                  Category: None
>                  Priority: 5 - Normal
>                  Severity: 3 - Normal
>                    Status: None
>                   Privacy: Public
>               Assigned to: None
>          Originator Email:
>               Open/Closed: Open
>           Discussion Lock: Any
>          Operating System: GNU/Linux
>
>      _______________________________________________________
>
> Details:
>
> ltmain.sh now (at least in Ubuntu 18.04) overrides the LD_LIBRARY_PATH with a
It seems to me libtool does not override path. It should prepend 
projects specific paths to environment variable.
Existing code:
...
     # Add our own library path to $shlibpath_var
     $shlibpath_var=\"$temp_rpath\$$shlibpath_var\"
...

> system library path, thus forcing the system libs over the user's custom path
> installed ones.
>
> I fixed this in TCE build by patching ltmain.sh in our build script generator
> script:
>
> https://github.com/cpc/tce/commit/820fe4475f65b38f4ec6c7013d1ddfe4510058c0#diff-36fd0e6bb489c013aa25e9a5fd4467a2
I'm not convinced that patch is correct.
Let project build new version of a system library and try to perform 
some tests. Executable from regression tests should use library from 
"build tree" not system one.

Regards,
Roumen Petrov


_______________________________________________
https://lists.gnu.org/mailman/listinfo/libtool
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.