install issues Mac OS Sequoia 15.7.1 (& Linux)

[Claire Arthur]

Hi **huggers,

I have a student trying to install humdrum from these docs: https://github.com/humdrum-tools/humdrum-tools 

Everything proceeds appropriately and there are no warnings or errors. Make files run and the folders with all the functions are on his machine. In addition, humdrum-tools is correctly showing up in his PATH variable. However, we cannot get zshell to recognize any of the humdrum commands (running "$ which mint" or any humdrum function returns 'not found'). 

Opening the .zshenv file shows that it has been added to the path. I'm a bit at a loss on how to proceed. Any suggestions? 

Screen shots are attached.

-Claire

[Craig Sapp]

Hi Claire,

I just installed MacOS Tahoe (MacOS 26.1) and I see the compiler warnings and I will work on removing them...

-=+Craig

--
--
This is a message is from the **HUG newgroup.
To post to this group, send email to stars...@googlegroups.com
To unsubscribe from this group, send email to
starstarhug...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/starstarhug?hl=en
---
You received this message because you are subscribed to the Google Groups "starstarhug" group.
To unsubscribe from this group and stop receiving emails from it, send an email to starstarhug...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/starstarhug/a1a9b5ae-0e1e-4cd9-bbaf-fef054ce7c56n%40googlegroups.com.

[Claire Arthur]

Thanks Craig, I presume then, that these warnings are not garbage but actually are the clue to solving this install issue perhaps?

Claire

[Craig Sapp]

Hi Claire, et al.,

"which mint" seems to be a configuration problem in find $PATH variable setup: the makefile messages are warnings and not errors: If a makefile finds an error, it stops compiling immediately; however, all of Humdrum Extras command-line tools are compiled, but they cannot be found.  You can look manually in humdrum-tools/humextra/bin to see what is there.

The most likely problem is the $PATH environment variable: where it does not list that directory.  Basic checking:

      echo $PATH

Or more easier to read, placing one directory on each line:

     echo $PATH | tr : "\n"

Or list all of the paths that contain only the string "humdrum":

     echo $PATH | tr : "\n" | grep humdrum

Here are my results:

% echo $PATH | tr : "\n" | grep humdrum

/Users/csapp/git-cloud/humdrum-tools/humextra/bin

/Users/csapp/git-cloud/humdrum-tools/humdrum/bin

~/git-cloud/humdrum-tools/humdrum/bin/

~/git-cloud/humdrum-tools/humextra/bin/

I have two installations (only the first one is active):

 % which mint

/Users/csapp/git-cloud/humdrum-tools/humdrum/bin/mint

The first problem to suspect is that you have a space in the command path: do not include a space, or you are tempting fate.  Go into the same directory that you ran make from, and type pwd:

% pwd

/Users/csapp/git-cloud/humdrum-tools

Note there are no spaces in the path returned by pwd.

If there a no spaces, then the most likely problem is in .zshrc:

% cat ~/.zshenv 

export PATH="/Users/csapp/git-cloud/humdrum-tools/humdrum/bin:$PATH"

export PATH="/Users/csapp/git-cloud/humdrum-tools/humextra/bin:$PATH"

The quotations should allow spaces in the directory name (at least in theory), but again do not tempt fate.

My $PATH is correct and "which mint" returns:

% which mint

/Users/csapp/git-cloud/humdrum-tools/humdrum/bin/mint

I typically use bash, since that is a ubiquitous shell for linux, and I do not care for Apple's incessant quirkiness.   To switch to bash temporarily type "bash".  You can check on your current shell by printing the $SHELL environment variable

 % echo $SHELL

/bin/bash

Then try "which mint" since it uses a different setup file, and may possibly be correct even if zsh is not.  bash is a lot more complicated when setting up the $PATH variable, because there are many script filenames possible, but only ~/.zahenv should be correct (I tried in MacOS Tahoe).

If you are still having problems, add a debug statement to the script, ~/.zshenv in this case:

export PATH="/Users/csapp/git-cloud/humdrum-tools/humdrum/bin:$PATH"

export PATH="/Users/csapp/git-cloud/humdrum-tools/humextra/bin:$PATH"

echo "ZSH INIT PATH: $PATH"

then relog in a new shell and search for a ZAH INIT PATH..., which should have the correct path then run echo $PATH | tr : "\n" and it should match (strange problem if not).

-=+Craig

--
--
This is a message is from the **HUG newgroup.
To post to this group, send email to stars...@googlegroups.com
To unsubscribe from this group, send email to
starstarhug...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/starstarhug?hl=en
---
You received this message because you are subscribed to the Google Groups "starstarhug" group.
To unsubscribe from this group and stop receiving emails from it, send an email to starstarhug...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/starstarhug/96ffb63f-55ae-4b70-a9cf-52908a2f0610n%40googlegroups.com.