Re: lib dependency confusion

On Jan 12, 2018, at 5:22 PM, Bill Cole wrote: > All very well and good for a machine running an OS version that got the > ShellShock update from Apple. people probably shouldn't be running an OS version that hasn't been patched for a 4 year old

Re: lib dependency confusion

On Jan 12, 2018, at 3:27 PM, Dave Horsfall wrote: > Whether Apple wants to admit that its machines can crash and thereby cream > the filesystem is another question... presumably that's what macOS Recovery is for: https://support.apple.com/en-us/HT201314 -- Daniel J. Luke

Re: lib dependency confusion

On Jan 11, 2018, at 11:31, Vincent Habchi wrote: > Alternatively to what Ryan just mentioned, you can statically link the > executable, which means that you embed all the code the executable and its > dependencies need into the main code. This result in a bigger executable > (more code) but

Re: lib dependency confusion

On Jan 11 06:23:11, ryandes...@macports.org wrote: > >>> $ port installed depends:libressl > >>> None of the specified ports are installed. > >> > >> This result means: of the ports that specify a dependency containing the > >> substring "libressl", you don't have any installed. > > > > OK,

lib dependency confusion

On Jan 10 20:49:21, h...@stare.cz wrote: > path:lib/libssl.dylib:openssl > > This means a 'lib/libssl.dylib' needs to be present in $prefix, > and if it's not, it gets installed by installing openssl. > The point of specifying the dependency this way is that > some port other than openssl