Re: How to fix duplicate rpath in existing library files

Default means to revbump all ports which is affected. A lot of heavy ports. I really not sure how safe is it, so, I prefer to be on safe side. -- wbr, Kirill > On 18. Dec 2023, at 22:41, Dave Allured - NOAA Affiliate > wrote: > > Thanks, that seems to be working well. I hope this can be made

Re: How to fix duplicate rpath in existing library files

Thanks, that seems to be working well. I hope this can be made default, so that we do not need to visit every port that makes a library and uses the PG. I do not know how widespread the LC_RPATH problem is. On Mon, Dec 18, 2023 at 12:28 PM Kirill A. Korinsky wrote: > If your port using compil

Re: How to fix duplicate rpath in existing library files

If your port using compilers PG you may control it via compilers.add_gcc_rpath_support option. See: https://github.com/macports/macports-ports/commit/760f4f8df2b90a6e31bd960f9768bf086c35b19f -- wbr, K

How to fix duplicate rpath in existing library files

Now that the LC_RPATH issue is better understood, is there a simple way to fix a duplicate rpath in a Macports previously built library file? Will a simple rev bump clear out the duplicate, or is a deeper approach needed? CI on OS13 keeps failing when it installs one of these pre-built libraries,