title: (MacOS Mojave 10.14.6) - Why 'lib' inside /usr/local is a Unix Executable file and not anymore a folder?
body: <p>I have a very fresh and clean install of Mojave 10.14.6 on my 'Late 2013 MacBook Pro' (I haven't just updated from High Sierra 10.13), and I noticed that where there used to be the folder 'lib' inside path /usr/local now there is a Unix Executable file, also named 'lib', of about 7.6MB.</p>
  
  <p><a href="https://i.stack.imgur.com/SGLfB.jpg" rel="nofollow noreferrer">current situation in Mojave</a></p>
  
  <p>Now, for a project requirement, I'd need to copy 3 dynamic libraries inside /usr/local/lib/ folder, but obviously I'm prevented from creating a folder with the same name of the Executable. I tried to look for a solution or any insight into this question, although it looks like no one really experienced this problem.</p>
  
  <p>Does anyone know why there has been such change, or if this is only my odd problem?
  Is there any workaround so that I can add *.dylib files to path: /usr/local/lib/ if I can't create a folder with that same name?</p>
  
  <p>I would really appreciate any advice, thanks!</p>