Oh I do run a MUCH newer dpkg so that might be why I do not see this issue at
all.
---
TS
http://www.southofheaven.org/
Life begins and ends with chaos, live between the chaos!
> On Jan 7, 2019, at 9:09 PM, Leigh Smith wrote:
>
> So digging further, the problem installing perl5162-core appears
So digging further, the problem installing perl5162-core appears to be due to a
bug in dpkg handling directories that differ in capitalisation when installing
on a case sensitive file system.
/sw/lib/perl5-core/5.16.2/version/Internals.pod
was unable to be installed because /sw/lib/perl5-core/5
Hmm, no I don’t have /usr/lib/libgcc_s.10.5.dylib either. I realised I had
screwed up the order of the ln command in my previous post, but the refusal by
MacOS X for me to create the symlink manually remained when the source and
destination file references were reversed. I was however able to ma
We have been noticing that the missing symlinks form 10.0 are not always being
created on update to 10.1 and haven’t figured out why. That or maybe they are
only being created on upgrade and not for ppl that install 10.1 directly.
Either way the current symlink is
lrwxr-xr-x 1 root wheel 19 O
Thanks for the reference.
I should have mentioned that I’m building with Xcode 10.1 and
Command_Line_Tools_macOS_10.14_for_Xcode_10.1.dmg and I’m only seeing the
symlink for libgcc_s.1.dylib@ -> libSystem.dylib, not a symlink of
libgcc_s.10.4.dylib -> libSystem.dylib.
To verify there wasn’t a
