Intel® C++ Compiler
Support and discussions for creating C++ code that runs on platforms based on Intel® processors.
Announcements
Intel Customer Support will be observing the Martin Luther King holiday on Monday, Jan. 17, and will return on Tues. Jan. 18.
For the latest information on Intel’s response to the Log4j/Log4Shell vulnerability, please see Intel-SA-00646
7590 Discussions

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

FDuncanH
Beginner
723 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
706 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


Viet_H_Intel
Moderator
696 Views

I've reported this to our Developer.

Thanks,


Ron_Green
Moderator
683 Views
Kerry_K_
Novice
597 Views

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

Minoru1
Beginner
534 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.

PrasanthD_intel
Moderator
300 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


Reply