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

19990517: make mcx on Slackware Linux

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: 19990517: make mcx on Slackware Linux
  • Date: Mon, 17 May 1999 17:09:40 -0600
>From: Jim Heimbach <address@hidden>
>Organization: UNCA
>Keywords: 199905141945.NAA27523 McIDAS-X ADDE

Jim,

>     Appreciate your comprehensive response to my ADDE question.  
>I'm starting to feel archaic enough that I should plan on attending
>one of your workshops again.

Things have progressed in the McIDAS world in the past few years.
I think that the tutorial should get you going pretty painlessly,
but attending a workshop can never hurt :-)

>     O.K., now on to the installation of McIDAS-X on a LINUX box.
>Things went as advertised by your web instructions until the 
>make mcx.  Below is the /home/mcidas/mcidas7.5/src/makelog file:
>
>
>##########################################
>Mon May 17 12:08:37 EDT 1999: BUILD BEGIN
>##########################################
>
>./mccomp -I. -I../netcdf/libsrc -c convdlmf.f
>mcfc -c -O -I. -I../netcdf/libsrc convdlmf.f
>/usr/lib/f2c: syntax error near unexpected token `!<arch>'
>/usr/lib/f2c: /usr/lib/f2c: line 1: `!<arch>'
>compile        convdlmf.f:             FAILED

Weird!

>     I grep'd everything looking for '!<arch>' without success.
>I'm using Slackware because that is what I was brought up on,
>and I'm hoping that my problem is not because of this particular
>flavor of UNIX.  
>
>     Sometimes you ask to check out my system, so with that
>contingency in mind, this machine is:
>
OK, I logged onto your machine and found the following:


cd /usr/lib
ls -l f2c
lrwxrwxrwx   1 root     root            8 May 14 14:47 f2c -> libf2c.a*

file f2c
f2c: symbolic link to libf2c.a

'f2c' is a link to libf2c.a???  'f2c' should be a program executable, not
a link to a library.

The next thing I did was:

which f2c
f2c: Command not found.

It looks like you are still lacking the 'f2c' executable that is needed for
the build.  I tried FTPing over a copy of f2c from our RedHat Linux
5.2 box to the ~mcidas/bin directory and then rerunning 'make all'
(should work since ~mcidas/bin is the first directory in your PATH),
but I get the same error as you reported above.

I believe that the f2c link in /usr/lib needs to be removed before you
can proceed, but I was unable to do this since I did not have root
access to your machine.  I verified that I can run the copy of 'f2c'
that I FTPed over "by hand":

<ftp 'f2c' to ~mcidas/bin>
cd ~mcidas/mcidas7.5/src
rehash
f2c < convdlmf.f > convdlmf.c

So, try removing the erroneous f2c link in /usr/lib and then running
'make all' again.  If this doesn't work, I will be suspicious of
libf2c.a in /usr/lib.

Tom