On May 9, 2024, at 01:03, Smith wrote:
>
> I occasionally run into a problem where I'm building software from a tarball
> or a git clone outside of MacPorts, and the build process somehow ends up
> linking or trying to link against libraries in the MacPorts space
> (/opt/local). How can I prev
On 2024-05-09 at 02:03:15 UTC-0400 (Thu, 9 May 2024 00:03:15 -0600)
Smith via macports-users
is rumored to have said:
Hello,
I occasionally run into a problem where I'm building software from a
tarball or a git clone outside of MacPorts, and the build process
somehow ends up linking or tryin
> > Sometimes I just end up deleting /opt/local to get it to build and
> > then re-install MacPorts, which can be painful or at least tiresome.
The question has since been answered, but what was wrong with merely
renaming /opt/local temporarily? That's what I would've done...
-- Dave
One could also `sudo port deactivate …` the ports which are problematic. I
occasionally have to do this with certain Rust tools through `cargo build`
(especially if they use libiconv).
-a
On Thu, May 9, 2024 at 4:13 PM Dave Horsfall wrote:
> > > Sometimes I just end up deleting /opt/local to ge
