Re: LD_LIBRARY_PATH_RPATH

2019-02-01 Thread Andrew Gierth
> "Tom" == Tom Lane writes: >> Is there some reason why ld_library_path_var is defined using a >> bunch of $(if) constructs rather than putting the value (if not >> LD_LIBRARY_PATH) in the individual port makefiles? Tom> I might be wrong, but I think that code is Peter's. I agree that

Re: LD_LIBRARY_PATH_RPATH

2019-02-01 Thread Tom Lane
Andrew Gierth writes: > Is there some reason why ld_library_path_var is defined using a bunch of > $(if) constructs rather than putting the value (if not LD_LIBRARY_PATH) > in the individual port makefiles? I might be wrong, but I think that code is Peter's. I agree that having the per-port make

Re: LD_LIBRARY_PATH_RPATH

2019-02-01 Thread Andrew Gierth
> "Tom" == Tom Lane writes: >> At least on my FreeBSD 11 box, the current definition of >> $(with_temp_install) is not sufficient to ensure that the various .so >> files are loaded from tmp_install and not from the compiled rpath (which >> will be the final install dir, which may of cours

Re: LD_LIBRARY_PATH_RPATH

2019-01-31 Thread Andrew Gierth
> "Tom" == Tom Lane writes: >> At least on my FreeBSD 11 box, the current definition of >> $(with_temp_install) is not sufficient to ensure that the various >> .so files are loaded from tmp_install and not from the compiled >> rpath (which will be the final install dir, which may of cours

Re: LD_LIBRARY_PATH_RPATH

2019-01-31 Thread Tom Lane
Andrew Gierth writes: > At least on my FreeBSD 11 box, the current definition of > $(with_temp_install) is not sufficient to ensure that the various .so > files are loaded from tmp_install and not from the compiled rpath (which > will be the final install dir, which may of course contain old > lib