> On Oct 5, 2016, at 5:21 PM, Mick Jordan <[email protected]> wrote:
>
> I have several libraries installed via MacPorts (that also exists in /usr/lib
> FWIW), e.g, libpcre and libz. I was rather surprised to see that these
> resolve to the MacPorts location,i.e., /opt/local/lib even though I am not
> passing -L/opt/local/lib to the link step. I thought this might be because I
> was using gcc to do the compilation/linking and that is also installed via
> MacPorts, but I get the same behavior when using clang. I added -Wl,-v to the
> link step and it lists the directories it is searching and /opt/local/lib is
> not included in the list. So my question is how is ld resolving to
> /opt/local/include. I have no environment variables such as LDFLAGS set,
> although /opt/local/bin is on my PATH.
>
> I'm running MacPorts 2.3.4 in El Capitan.
I'm not able to reproduce this problem.
$ echo 'int main(void) { return 0; }' > main.c
$ clang main.c -lz
$ otool -L a.out
a.out:
/usr/lib/libz.1.dylib (compatibility version 1.0.0, current version
1.2.5)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
version 1226.10.1)
_______________________________________________
macports-users mailing list
[email protected]
https://lists.macosforge.org/mailman/listinfo/macports-users
