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

20011010: trouble with building 7.8 on dec-alpha



>From: "Alliss, Randall J." <address@hidden>
>Organization: TASC
>Keywords: 200110101610.f9AGA0112754 McIDAS-X OSF/1

Randy,

>I am enclosing the makelog which was generated when my admin person tried to
>build mcidas7.8. Can you provide any clues?
>The operating system is OSF1 4.0

One thing that jumped out at me was:

cc -c -std -DFUNCPROTO=3D15 -I. -I../netcdf/libsrc -I../jpeg -I../zlib colors.c
cc: unrecognized option `-std'
compile        colors.c:               done

The '-std' flag has been in my build for OSF/1 for a long time.  I
just checked and verified that it was there in both my 7.6 and 7.7
releases, and, if I am not mistaken, you were able to successfully
build both of these releases on your machine(s).  This may not have
any relevance to the build dying on your machine, but I just thought
I would mention it.

The real problem comes from:

f77 -s -o colors.k colors.o -L. -lmcidas -nofor_main -lm
ld:
Unresolved:
__eprintf
fort: Severe: Failed while trying to link.
link   colors.k:               FAILED

I just did a quick look through all /usr/lib libraries on our OSF/1 5.1
machine (True64) and do not see an entry point named __eprintf (or eprintf).
Given this, I decided to build 7.8 from scratch and see if I run into
anything new.

The first thing I _don't_ notice is any comment about the '-std' flag for
C compiles.

OK, colors.k just got built.  Here is the relevant piece from makelog:

cc -c -std -DFUNCPROTO=15 -I. -I../netcdf/libsrc -I../jpeg -I../zlib colors.c
compile colors.c:               done
./mccomp -s -vendor -o colors.k colors.o -L. -lmcidas
f77 -s -o colors.k colors.o -L. -lmcidas -nofor_main -lm
link    colors.k:               done

So, we don't see the same kind of thing on our machine as you are seeing on
yours.

I chatted with my system administrator, and he reminded me that the
development environments for our OSF/1 set are exactly the same under
5.1 as they were under 4.0F.  Given this, I ran:

/home/mcidas% cc -V
Compaq C V6.3-028 on Compaq Tru64 UNIX V5.1 (Rev. 732)
Compiler Driver V6.3-026 (sys) cc Driver

What do you get when you run 'cc -V' as the user 'mcidas'?

Also, what is the result of:

/home/mcidas% which cc

We will get to the bottom of this...

Tom

>From address@hidden Fri Oct 12 07:39:29 2001
>Subject: Re: 20011010: trouble with building 7.8 on dec-alpha 

Tom,

Randy Alliss asked me to let you know that Mcidas7.8 has been successfully
built on our Alpha (Tru64 Unix 4.0f).  The problem, as you suspected,
was that the GNU compiler was being used.  I had forgotten to take
the directory where the GNU software was located out of the PATH,
as I had first tried building with GNU C since we had all forgotten that
we had used the native Alpha compiler for the last build (IIRC that
was the first Mcidas that built successfully with the Compaq compilers
rather than requiriing f2c and GNU C for Alpha).

Thanks for your help, and if you have any questions about this, please
let me know.

Martha Tonkin


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.