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

20040220: linker errors with mcidas 2003 on linux (cont.)

>From: Steve Ochani <address@hidden>
>Organization: SUNY Nassau
>Keywords:  200402182003.i1IK3BrV028667 McIDAS-X SuSe 9.0 libsdi.a make

Hi Steve,

re: make all VENDOR=-g77

>I had modified the makefile and changed the vendor line, that's why i
>just did a "make all"

Thanks for reminding me of that.  You were correct in doing the simple
'make all' after modifying the makefile VENDOR= setting.

re: wnvblk_ is contained in Bk11Data.c ...
>I tried the above commands with the same  results.

>----
> /home/mcidas> cd mcidas2003/src/
> mcidas2003/src> ar r libsdi.a Bk11Data.o
> mcidas2003/src> ranlib libsdi.a
> mcidas2003/src> make all VENDOR=-g77
>
>##########################################
>Fri Feb 20 10:34:15 EST 2004: BUILD BEGIN
>##########################################
>
>link    decoder:                FAILED (See '/home/mcidas/mcidas2003/src/makel
> og' for details.)
>
>make: *** [decoder] Error 1
> mcidas2003/src> tail makelog
>Fri Feb 20 10:34:15 EST 2004: BUILD BEGIN
>##########################################
>
>./mccomp -O -s -g77 -o decoder decoder.o -L. -lsdi -lmcidas
>mccomp: Using default optimizations
>g77 -s -O -o decoder decoder.o -L. -L/usr/X11R6/lib -lsdi -lmcidas -ldl -lm
>decoder.o(.text+0x1592): In function `end_of_line':
>: undefined reference to `wnvblk_'
>collect2: ld returned 1 exit status
>link    decoder:                FAILED
> mcidas2003/src> 
>----

What does the output of the following look like on your system:

nm Bk11Data.o

Is there an entry point named wnvblk_ in the listing?  If not, is it
possible that there is one named wnvblk__?

>I think I will go with my backup plan of having the suse linux machine
>only as a ldm machine outside the firewall feeding a ldm machine behind
>the firewall which will be rh fedora.

OK.  I would love to find the real reason for the link failures on
SuSe 9.0, however.  Does SuSe 9 have a v2.6 kernel by any chance?
If yes, the failure to correctly create libsdi.a matches the experience
I had this morning on a dual Athlon 2400+ system that is running the
brand new Fedora Core 2 release.

>Thanks for your help.

Sorry for the problems....

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.