Analyzers
Talk to fellow users of Intel Analyzer tools (Intel VTune™ Profiler, Intel Advisor)
5135 Discussions

OneAPI 2024.0.0 modulefiles/vtune/{2024.0,latest} bug

CFR
New Contributor II
2,241 Views

 

I think:

set scriptpath ""
set scriptpath "[file dirname [file normalize "/___"]]"

is supposed to be:

set scriptpath "${ModulesCurrentModulefile}"
set scriptpath "[file dirname [file normalize "$scriptpath/___"]]"

0 Kudos
8 Replies
SreedeviK_Intel
Moderator
2,163 Views

Hi,

Thank you for posting in Intel communities.

We were able to reproduce the issue from our end on linux machine with latest version of VTune (2024.0).

We are checking on it internally and will get back to you with an update shortly.

Could you please share your OS and hardware details?

Regards,

Sreedevi


0 Kudos
CFR
New Contributor II
2,150 Views

The install was done on a CentOS 7.9, Xeon E5-2637 machine.

0 Kudos
SreedeviK_Intel
Moderator
2,085 Views

Hi,


Thanks for reporting this issue.

We were able to reproduce it and we have informed the development team about it.


Regards,

Sreedevi


0 Kudos
nmnobre
Novice
1,549 Views

Hi, both the current and patched modules have unbalanced curly braces in:

set modulefilever "[file tail "$scriptpath}"]"

 

Cheers,

Nuno

0 Kudos
Jeffrey_R_Intel1
Employee
785 Views

Thank you for reporting this. The Intel(R) VTune(TM) Profiler module file has been fixed in the 2024.2 release.

CFR
New Contributor II
733 Views

Sadly it looks like 2024.02 is broke in a different way...

set script_path "[file normalize [exec readlink -f ${ModulesCurrentModulefile}]]"

...results is something like...

<installdir>/vtune/2024.2/etc/modulefiles/vtune/2024.2

and then...

set PRODUCT_INSTALL_DIR "[file dirname [file dirname $script_path]]"

... turns into ...

<installdir>/vtune/2024.2/etc/modulefiles

What's missing is something that takes off two more level of directories...

set PRODUCT_INSTALL_DIR "[file dirname [file dirname $PRODUCT_INSTALL_DIR]]"

... to get a PRODUCT_INSTALL_DIR to point at the right level...

<installdir>/vtune/2024.2

 (At least that's what I had to do....)

0 Kudos
yuzhang3_intel
Moderator
257 Views

This is one known issue, which will be fixed in a future release. Here is a workaround:

 

The target file is something like /opt/intel/oneapi/vtune/latest/etc/modulefiles/vtune/2024XX

set write permissions on the target file and edit the file

 

Old

set PRODUCT_INSTALL_DIR "[file dirname [file dirname $script_path]]"

 

New

set PRODUCT_INSTALL_DIR "[file dirname [file dirname [file dirname [file dirname $script_path]]]]"

 

Open a new shell and load the module again

0 Kudos
Reply