Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
29282 Discussions

.bashrc does not add compiler directives to path

anusiya
Beginner
‎09-16-2010 12:54 PM
938 Views
Hi y'all,

I have this peculiar problem. My compiler installation was without issues. When I added the line in my .bashrc "source /opt/intel/Compiler/11.1/073/bin/iccvars.sh intel64", ran "source ~/.bashrc" without any error and type "icc", I get an error "icc: command not found". Yet when I type out "source /opt/intel/Compiler/11.1/073/bin/iccvars.sh intel64" at terminal, then icc works.

If it helps my distro is Ubuntu 10.04 with 2.6.32-24 kernel.

Thanks!
Anusiya





0 Kudos

Link Copied

3 Replies
TimP
Honored Contributor III
‎09-16-2010 02:11 PM
938 Views
Did you set echo temporarily in .bashrc to see if the command actually executes (and that you don't mess up PATH later)?
0 Kudos
Copy link
anusiya
Beginner
‎09-17-2010 01:00 PM
938 Views
Hi tim18,

If you meant I added a line 'echo $PATH' at the end of my .bashrc, yes I did that before and it displays my path variables correctly. But the complier variables are not listed there.
0 Kudos
Copy link
TimP
Honored Contributor III
‎09-17-2010 08:48 PM
938 Views
No, for diagnostic purposes, you would want to see each command in .bashrc executing.
0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.