[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20051031: Mcidas2005 on FreeBSD 5.4

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: 20051031: Mcidas2005 on FreeBSD 5.4
  • Date: Mon, 31 Oct 2005 16:55:39 -0700
>From: Brendon Hoch <address@hidden>
>Organization: Plymouth State
>Keywords: 200510312032.j9VKWr7s003036 McIDAS FreeBSD 5.4

Hi Brendon,
>
>Trying to build mcidas2005 on storm.plymouth.edu.  OS=FreeBSD5.4

I had problems building McIDAS on FreeBSD 5.3 previously, and
I don't remember exactly what I had to get things to work.

>Make 
>logs indicate something getting hung up on HDF (see attached makelog) 
>Give me a ring if you want mcidas password to log in and poke around.

I will want to get login information from you since we don't currently
have a FreeBSD 5.x machine in house.  This will have to happen sometime
tomorrow.

BTW, one thing I think is telling in the listing you sent comes
from the HDF configure output:

 ...
>checking for config freebsd5.4... no
>checking for config freebsd... found
 ...

Looks like FreeBSD 5.x might need a config file in the HDF subdirectory.

The actual error looks more serious:

>checking how to run the C++ preprocessor... /lib/cpp
>configure: error: C++ preprocessor "/lib/cpp" fails sanity check
>See `config.log' for more details.

Can you send the config.log file?  Actually, if I get the logon
for 'mcidas', I can better look at the file myself.

I can either call you tomorrow, or you can send me an email to 
my private account (address@hidden) that includes _ONLY_
the password (no machine name, no user name, etc.).

Cheers,

Tom
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publicly available
through the web.  If you do not want to have your interactions made
available in this way, you must let us know in each email you send to us.