[netCDF #DTX-704143]: netCDF 3.6.2 on mac OSX 10.5 with intel

Tim,

OK, since I don't have an icc compiler installed here I'm just guessing, but
here are
two more possibilities:

  1.  Putting an environment variable setting in your .cshrc file will cause it
  to be
      used in subshells, but I don't think it causes the new settings to apply
      to the
      current shell unless you either logout and log back in again or
      explicitly invoke
      "source .cshrc" to make sure the new setenv commands are invoked.  I
      don't use
      csh or tcsh, so I may be wrong about this ...

  2.  Several web postings I've seen about the icc/configure problem on Leopard
  have
      mentioned that they thought it was necessary to use
        setenv CC "icc -no-multibyte-chars"
      rather than
        setenv CC icc
        setenv CFLAGS -no-mulitbyte-chars
      I don't know why there would be a difference, but it might be something
      subtle.

The only other suggestion I have is to ask Intel support, via one of their
support forums,
about how to get around this problem.  It is not a netCDF problem, but an
icc/Leopard
problem, as far as I can see.

In you config.log file, I see evidence that the option is being used in some
cases (even twice!):

configure:3727: checking for suffix of executables
configure:3734: icc -o conftest -no-multibyte-chars  -no-multibyte-chars
conftest.c  >&5
configure:3737: $? = 0
configure:3761: result:
configure:3767: checking for suffix of object files
configure:3793: icc -c -no-multibyte-chars  conftest.c >&5
configure:3796: $? = 0
configure:3819: result: o

and the error message occurring when it is not used:

configure:3880: checking whether icc accepts -g
configure:3910: icc -c -g  conftest.c >&5
Catastrophic error: could not set locale "" to allow processing of multibyte
characters

compilation aborted for conftest.c (code 4)

Also it apparently is not a valid ifort option:

configure:5299: ifort -c -no-multibyte-chars conftest.F >&5
ifort: command line warning #10006: ignoring unknown option
'-no-multibyte-chars'

Note that many of the errors in config.log are expected, they do not
necessarily indicate
a problem with the configure script.  I don't know why the locale still seems
to be set
to "" despite your setting LANG, LC_ALL, and LC_CTYPE.

Sorry I can't be of more help ..

--Russ

Russ Rew                                         UCAR Unidata Program
address@hidden                     http://www.unidata.ucar.edu



Ticket Details
===================
Ticket ID: DTX-704143
Department: Support netCDF
Priority: Normal
Status: Closed