nigpib-0.8.3 works, but...

[mike suchoff]

nigpib-0.8.3 doesn't crash under redhat 8 (kernel 2.4.18) when doing a findlstn as I previously reported.

However, it still requires an "insmod -f nigpib.o" to force it to load because it is compiled with gcc 2.xx instead of 3.xx.

Is this what you indent for this driver?

[AaronK]

Hi Mike,

I am certainly glad that it no longer crashes! I believe that it was in fact compiled with gcc 3.xx. I have not been able to reproduce this errer yet (I don't yet have acces to the equipment). It was also tested for RH8. Has anyone else run into this problem? Also mike. Make sure that your gcc compiler s 3.xx by doing a gcc -v.

Aaron K.
Application Engineer
National Instruments

[mike suchoff]

the problem isn't with my compiler. nigpib.o is supplied by NI already compiled. It is the insmod loader that says nigpib.o was compiled by you with a 2.0 compiler.

[AaronK]

Actually that is not true, if you take a look at the makefile you will notice that a good part of the driver is compiled on the target machine. You did not indicate the version of your compiler in your last post. Make sure that your compiler is the correct version and also make sure that you do not somehow have the older driver still laying around. On my redhat 8 test machine I had no trouble installing 0.8.3. I received no warning messages about compiler versions or anything of that nature.

If you have some methods by which I might be able to reproduce this problem, please let me know.

Regards,
Aaron K.
Application Engineer
National Instruments

[mike suchoff]

I'm running gcc version 3.2 - the one that comes with redhat 8.0.

To verify I hadn't done anything wrong, I just extracted nigpib-0.8.3.tar.gz to a new directory and ran make again. If I run "insmod ./nigpib.o" I get a message telling me that nigpib.o is compiled with a gcc version 2 compiler.

I then changed the makefile's use of "ld" (for linking objects together) to use "gcc" instead. But I still get the same problem.

It is not an old version of nigpib.o. I even tried renaming ./nigpib.o to x.o and if I try and "insmod ./x.o" I get the same message.

Please send me a copy of your nigpib.o so that I can verify yours is OK. (Or I'll be happy to send you mine)

[AaronK]

Hi Mike,

Ok, this is a strange problem. I tar'ed the directory that I use (post 'make clean') so that we can be sure to be using the exact same files. I am attaching them to this post. Try them out and see if you are getting the same problem. I am really at a loss for ideas at the moment.

Best Regards,
Aaron K.
Application Engineer
National Instruments