Intel® C++ Compiler
Community support and assistance for creating C++ code that runs on platforms based on Intel® processors.
7955 Discussions

Solution for Broken compilervars.sh with zsh (on MacOS 10.15.7) after latest compiler update.

FDuncanH
Beginner
1,760 Views

The most recent version of the shell script compilervars.sh added a section  to

remove duplicate paths.     Its fine for bash, but breaks zsh (whis no default in MacOS.

"echo $(!arg) "  is incorrect  syntax in  the zshell scripting.

 I found the fix below ,   It might be useful for anyone using zhell on macos.

 

 

Broken script

------------------function remove_duplicate_paths----------------------------

remove_duplicate_paths() {
local arg=$1

if [ "${INTEL_HOST_PLATFORM}" = "Darwin" ]; then
local arr=(`echo ${!arg} | sed 's/:/\'$'\n/g'`)
else
local arr=(`echo ${!arg} | sed 's/:/\n/g'`)
fi

fixed script below


# ------------------function remove_duplicate_paths----------------------------
remove_duplicate_paths() {
local arg=$1
eval "value=\"\${$arg}\""
if [ "${INTEL_HOST_PLATFORM}" = "Darwin" ]; then
local arr=(`echo ${value} | sed 's/:/\'$'\n/g'`)
else
local arr=(`echo ${!arg} | sed 's/:/\n/g'`)
fi

6 Replies
GouthamK_Intel
Moderator
1,743 Views

Hi,

Thanks for reporting this issue and providing the workaround.

We will forward this thread to the concerned internal team to verify and get it fixed accordingly if possible.

Have a Good day!


Thanks & Regards

Goutham


0 Kudos
Viet_H_Intel
Moderator
1,733 Views

I've reported this to our Developer.

Thanks,


0 Kudos
Kerry_K_
Novice
1,635 Views

Thanks, I confirm this worked for me on 10.15.7 with zsh.  Now onto the next problems with updating macos+intel+openmpi... 

0 Kudos
Minoru1
Beginner
1,572 Views

Thank you so much for your more beneficial advice so that I could work around the same as problem in my case.

$ source .zshrc (return)

After this command, there is nothing such as error messages at all.

0 Kudos
PrasanthD_intel
Moderator
1,337 Views

Hi,


Thanks for the confirmation.

As your issue has been resolved, we are closing this thread. We will no longer respond to this thread. If you require additional assistance from Intel, please start a new thread. Any further interaction in this thread will be considered community only


Regards

Prasanth


0 Kudos
Reply