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

20051129: MciDAS-X 2005...new and improved with GCC 4.02-8?

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: 20051129: MciDAS-X 2005...new and improved with GCC 4.02-8?
  • Date: Wed, 30 Nov 2005 01:25:46 -0700
>From: Gilbert Sebenste <address@hidden>
>Organization: NIU
>Keywords: 200511300547.jAU5lY7s029076 McIDAS

Hi Gilbert,

re:
>I don't know what your intentions are about compiling McIDAS-X 2005 on my 
>machines yet.

Hmm...  I already built v2005 on weather3 and weather2 (I'll check
on weather), but I put off and then forgot to install them.  Sorry.

>But you should know, since we talked after I installed 
>Fedora Core 4...
>
>I just installed GCC 4.02-8, which fixes a number of bugs. I also have the 
>latest kernel, just released yesterday, and other miscellaneous programs 
>which should improve the performance on my machines, and maybe not allow 
>McIDAS to crash when compiling...?

The build doesn't "crash".  What happens is that object modules that
are supposed to be added to McIDAS libraries are not getting added.
This is a problem with the 'ar' utility bundled with FC4 that gets
tickled on fast machines.  I "solved" the problem by putting sleeps
after 'ar' and 'ranlib' invocations in mcar.sh.  Tomorrow I will be
cutting a McIDAS v2005 addendum that includes this fix and other mods
that I have made since the original release.

>Anyway, take care and I will catch you tomorrow, I am sure.

Later...

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.