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

20040510: problems linking my sat_archive progr with libmcidas.a - mystery remains



>From: Marek Kmiecik <address@hidden>
>Organization: SUNYA/CESTM
>Keywords: 200405072017.i47KHdtK011466 McIDAS libmcidas.a link

Marek,

Sorry it has taken this long to get back to you.  I was at a conference
until this morning.

>Thanks for your suggestions. Though, I tried them all! I thoroughy went
>through
>on-line preinstallation and installation instructions, which you suggest. 
>But none of these were helpful unfortunately. I found a temporary solution,
>though, based on this:
>http://www.unidata.ucar.edu/projects/coohl/mhonarc/MailArchives/gempak/msg0513
> 8.html
>with a little twist which was my own invention, that oddly works!

So, you have gotten around the link failures you report below?

>But the mistery remains mystery. My basic questions remain unanswered.
>What I did, was that in my Makefile, I put this:
>LIBS    = -lmcidas -lutil -lm -lsocket -lnsl -lf77compat
>so, I added lf77compat libary link. Yet this wasn't working, either. But this 
> time
>the complain was different:
>__f90_io_master_lock                /asrcserv1/opt/Forte6u2/SUNWspro/lib/libf7
> 7compat.so
>__f90_small_unit_pointer_table      /asrcserv1/opt/Forte6u2/SUNWspro/lib/libf7
> 7compat.so
>__f90_start_time                    /asrcserv1/opt/Forte6u2/SUNWspro/lib/libf7
> 7compat.so
>__f90_default_output_unit           /asrcserv1/opt/Forte6u2/SUNWspro/lib/libf7
> 7compat.so
>__f90_units_max                     /asrcserv1/opt/Forte6u2/SUNWspro/lib/libf7
> 7compat.so
>__f90_flush_all                     /asrcserv1/opt/Forte6u2/SUNWspro/lib/libf7
> 7compat.so
>__f90_unit_number_mask              /asrcserv1/opt/Forte6u2/SUNWspro/lib/libf7
> 7compat.so
>__f90_release_unit                  /asrcserv1/opt/Forte6u2/SUNWspro/lib/libf7
> 7compat.so
>__f90_unit_number_table             /asrcserv1/opt/Forte6u2/SUNWspro/lib/libf7
> 7compat.so
>__f90_default_error_unit            /asrcserv1/opt/Forte6u2/SUNWspro/lib/libf7
> 7compat.so
>__f90_units_limit                   /asrcserv1/opt/Forte6u2/SUNWspro/lib/libf7
> 7compat.so
>__f90_unit_pointer_table            /asrcserv1/opt/Forte6u2/SUNWspro/lib/libf7
> 7compat.so
>__f90_no_of_units                   /asrcserv1/opt/Forte6u2/SUNWspro/lib/libf7
> 7compat.so
>__f90_expand_unit_table_a           /asrcserv1/opt/Forte6u2/SUNWspro/lib/libf7
> 7compat.so
>__f90_default_input_unit            /asrcserv1/opt/Forte6u2/SUNWspro/lib/libf7
> 7compat.so
>__f90_initio_done                   /asrcserv1/opt/Forte6u2/SUNWspro/lib/libf7
> 7compat.so
>__f90_cleanup                       /asrcserv1/opt/Forte6u2/SUNWspro/lib/libf7
> 7compat.so
>ld: fatal: Symbol referencing errors. No output written to sat-pixel
>*** Error code 1
>make: Fatal error: Command failed for target `sat-pixel'
>Then, after I replaced F77     = f77 with F77  = f90, I got succesfully compil
> ed my code(?)
>Why?

The -lf77compat library is for F90 compiled routines.  By specifying it,
you were in essence forcing yourself to start using the F90 compilre.

>Both my machines are using the same remote c/fortran compilers, both have
>I have the same, identical warning message (below) on both machines.
>Yet, on my sumblade100 it doesn't cause any further complications. It
>compiles smoothly.

I have to believe that there is some difference in how the libraries
are found (pathnames), and on the Sunblade100 they are recognized
and on the other(s) they are not.  Other than that, it is a mystery
to me also.

I am glad that you have a workaround...

Cheers,

Tom
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publically 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.


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.