bash – Unusual “command not discovered” and “No such file or listing” errors

on

|

views

and

comments


Very unusual errors of a number of kinds:

  1. Working brew set up c-ares fails with command not discovered, seemingly not even executing brew:
    $ brew set up c-ares
    -bash: brew set up c-ares: command not discovered
    

    But brew set up cmake executes brew as anticipated:

    $ brew set up cmake
    Warning: Treating cmake as a method. For the cask, use homebrew/cask/cmake
    Warning: cmake 3.25.1 is already put in and up-to-date.
    To reinstall 3.25.1, run:
      brew reinstall cmake
    
  2. Can not prepend /usr/native/decide/qt5/bin to $PATH with the error No such file or listing:
    $ export PATH=/usr/native/decide/qt5/bin:$PATH
    -bash: export PATH=/usr/native/decide/qt5/bin:/usr/native/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/TeX/texbin:/usr/native/MacGPG2/bin:/decide/X11/bin:/Library/Apple/usr/bin: No such file or listing
    

    That folder does exist:

    $ [ -d /usr/local/opt/qt5/bin ] && echo "exists"
    exists
    

    As do all of the others on $PATH:

    $ echo $PATH
    /usr/native/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/TeX/texbin:/usr/native/MacGPG2/bin:/decide/X11/bin:/Library/Apple/usr/bin
    $ for i in $(echo $PATH | awk -F: '{for (i=1; i<=NF; i++) { print $i; }}'); do if [ -d "$i" ]; then echo "$i exists"; else echo "$i doesn't exist"; fi; performed
    /usr/native/bin exists
    /System/Cryptexes/App/usr/bin exists
    /usr/bin exists
    /bin exists
    /usr/sbin exists
    /sbin exists
    /Library/TeX/texbin exists
    /usr/native/MacGPG2/bin exists
    /decide/X11/bin exists
    /Library/Apple/usr/bin exists
    

    But including /tmp works:

    $ export PATH=/tmp/:$PATH
    $ echo $PATH
    /tmp/:/usr/native/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/TeX/texbin:/usr/native/MacGPG2/bin:/decide/X11/bin:/Library/Apple/usr/bin
    
  3. Similar errors with zsh:
    $ zsh
    % brew set up c-ares
    zsh: command not discovered: brew set up c-ares
    % brew set up cmake
    Warning: Treating cmake as a method. For the cask, use homebrew/cask/cmake
    Warning: cmake 3.25.1 is already put in and up-to-date.
    To reinstall 3.25.1, run:
      brew reinstall cmake
    % export PATH=/usr/native/decide/qt5/bin:$PATH
    zsh: no such file or listing: export PATH=/usr/native/decide/qt5/bin:/tmp/:/usr/native/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/TeX/texbin:/usr/native/MacGPG2/bin:/decide/X11/bin:/Library/Apple/usr/bin
    

I am fairly baffled and do not know how you can debug shell built-ins.

Nothing involves thoughts of what lately modified that might trigger this. I upgraded to Ventura 13.1 at present hoping this could go away, however it was taking place earlier than the improve and continues to occur.

I attempted restarting and it did not assist.

System data:

% system_profiler SPSoftwareDataType SPHardwareDataType | grep -v -e UUID -e UDID -e 'Consumer Title' -e 'Laptop Title' -e Serial
Software program:

    System Software program Overview:

      System Model: macOS 13.1 (22C65)
      Kernel Model: Darwin 22.2.0
      Boot Quantity: MainDisk
      Boot Mode: Regular
      Safe Digital Reminiscence: Enabled
      System Integrity Safety: Disabled
      Time since boot: 22 minutes, 2 seconds

{Hardware}:

    {Hardware} Overview:

      Mannequin Title: MacBook Professional
      Mannequin Identifier: MacBookPro15,1
      Processor Title: 6-Core Intel Core i7
      Processor Pace: 2.6 GHz
      Variety of Processors: 1
      Complete Variety of Cores: 6
      L2 Cache (per Core): 256 KB
      L3 Cache: 9 MB
      Hyper-Threading Know-how: Enabled
      Reminiscence: 16 GB
      System Firmware Model: 1916.60.2.0.0 (iBridge: 20.16.2059.0.0,0)
      OS Loader Model: 564.40.4~55
      Activation Lock Standing: Enabled

Share this
Tags

Must-read

Constructing the Torc Driverless Security Case

At Torc, we’ve structured our security case on three foundational pillars: Engineer It to Be Secure, Function It to Be Secure, and the...

What’s DL+S? Unlocking the Huge Information Required to Develop Autonomous Vans

Breakthroughs in AI for autonomous driving don't occur in isolation. They occur when information, simulation, machine studying, infrastructure, and car testing work as...

Why I can’t wait to get right into a driverless automotive | Self-driving automobiles

Adrian Chiles (Driverless automobiles are taking us on a street to nowhere, 10 September) needs to know who requested for driverless automobiles. I...

Recent articles

More like this

LEAVE A REPLY

Please enter your comment!
Please enter your name here