Josh, Lawrence, Clemens, Brandon, Thanks for your responses. I was able to fish “LINKSHARED=...-install_name $libdir/\$(@F)” out of the configure.in file to be able to proceed.
-Sterling On Jun 2, 2015, at 12:45PM, Clemens Lang <c...@macports.org> wrote: > Hey, > > ----- On 2 Jun, 2015, at 19:53, Brandon Allbery allber...@gmail.com wrote: > >> I do wonder if something, perhaps as part of trace mode, might run over the >> generated destroot and warn about objects that appear to point to things in >> the >> build or destroot path. (Automatically fixing might not be viable though, >> since >> I can imagine a lot of things going wrong --- notably plugins.) > > There's a post-destroot check phase in a GSoC 11 branch that should be > modified to > use libmachista – it's the correct place for this kind of check, and there > are a > couple of more checks we could implement there. > > -- > Clemens Lang > _______________________________________________ > macports-dev mailing list > macports-dev@lists.macosforge.org > https://lists.macosforge.org/mailman/listinfo/macports-dev _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
