On 09/05/2024 21:13, Dave Horsfall wrote:
The question has since been answered, but what was wrong with merely
renaming /opt/local temporarily? That's what I would've done...
$ cat ~/Builds/bare_build.sh
unset C_INCLUDE_PATH
unset CPLUS_INCLUDE_PATH
unset LIBRARY_PATH ; export LIBRARY_PATH=/
> On May 10, 2024, at 12:14 PM, Ryan Schmidt wrote:
>
> On May 10, 2024, at 09:57, Smith wrote:
>>
>> Thanks all for the replies. The software depends on openssl, libpng and
>> libjpeg.
>
> And the name and version of the software that depends on those?
https://github.com/istopwg/ippsample
On May 10, 2024, at 09:57, Smith wrote:
>
> Thanks all for the replies. The software depends on openssl, libpng and
> libjpeg.
And the name and version of the software that depends on those?
> In the past with other projects I left MacPorts in place but used Homebrew to
> install these depend
Thanks all for the replies. The software depends on openssl, libpng and
libjpeg. In the past with other projects I left MacPorts in place but used
Homebrew to install these dependencies, or just built those dependencies from
scratch. It's not a "bad" thing for them to link to MacPorts libraries
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
> > 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
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
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
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 trying to link against libraries in the MacPorts space (/opt/local). How can
I prevent this from happening? Sometimes I just e
