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

Steve,

>> 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__?
>
>Yes there is.
>----
> mcidas2003/src> nm Bk11Data.o 
 ...
>         U wnvblk_
 ...

The wnvblk_ entry point is contained in the wnvblk.for routine which
gets compiled into wnvblk.o and added to libmcidas.a.  The fact
that the linker can't find this entry point in your libmcidas.a
seems to say that the object module was not added to the library
in the first place.  This fits with libsdi.a not being created
correctly, and seems to point a finger at a problem with make.

re: I would love to find the real reason for the link failures

>If you wish I can give you ssh access to the system.

Thanks. I may take you up on this in the future, but right now I am
swamped with some other things.

>the kernel is 
>
>mcidas2003/src> uname -a
>Linux b225-image 2.4.21-166-default #1 Thu Dec 18 18:23:14 UTC 2003 i686 i686 
> i386 
>GNU/Linux

OK.  I don't see this problem on Fedora Core 1, and I was running the
2.4.22-xxxx kernels there.

>Thanks again,

I will attempt to spend some time with this issue next week, but I
will be on travel, so it may have to be put off until mid March.

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.

>From address@hidden  Fri Feb 20 16:41:56 2004

Tom,

Good news.  I got it to build after doing a upgrade of make. I upgraded
from

make-3.80-96

to 

make-3.80-101

Funny, when i ran yast to do a upgrade it did a lot of updates, I guess
they were only security updates.


I still had the initial problem of libsdi.a but I did what you
suggested in th first e-mail (that you also had to do on slackware) So
it seems there's still something wrong with that make.


Now to test mcidas and build ldm.

Thanks for your help.