gpib-modules-source will not compile

Bug #242986 reported by pdevries
28
This bug affects 4 people
Affects Status Importance Assigned to Milestone
gpib (Ubuntu)
Confirmed
Undecided
Unassigned
Nominated for Hardy by Felix Jaeckel
Nominated for Intrepid by Felix Jaeckel

Bug Description

Binary package hint: gpib-modules-source

gpib-modules-source in 8.04 is version 3.2.09. Kernel in 8.04 is 2.6.24. gpib-modules-source-3.2.09 won't compile with kernel versions > 2.6.22 due to kernel symbol changes. (This is also documented in the gpib-modules-source version 3.2.10)

development version gpib-modules-source-3.2.10 works for me in 8.04.

Revision history for this message
Mark Kahrs (mark-kahrs) wrote :

The current debian version is 3.2.11 although it is labeled "unstable". That being said, the source directory is much more complete than the current package in Hardy.

I would recommend pulling the debian package over and starting from that, in spite of the "unstable" label.

Revision history for this message
pdevries (pdevries) wrote :

3.2.11 won't compile on Ubuntu 8.10. One of the source files calls the kernel "kill_proc" function, which has been removed as of linux kernel 2.6.27. This is an upstream problem with gpib-modules source 3.2.11.

Revision history for this message
Don Levin (don-m-levin) wrote :

I had gpib working with older vers Ubuntu but ran into this problem. Communicating with instruments is essential for engineering applications. Can someone please fix this? Thanks!

Revision history for this message
burn (ubuntu-radzio) wrote :

Compilation fails using the module-assistant with gpib 3.2.11-0.2ubuntu3 and kernel 2.6.28-14 in 7.02, even when I change the kill_proc to kill_pid in sys/ibinit.c
( http://sourceforge.net/tracker/?func=detail&aid=2547889&group_id=42378&atid=432940 )

But strangly it compiles when I download the files from http://linux-gpib.sourceforge.net/ (after changing the kill_proc to kill_pid). Comparing the two files ( cb7210/cb7210_cs.c ) shows no diffrerence

Revision history for this message
scott_selberg (sselberg) wrote :

I replaced the kill_proc(...) call with send_sig( SIGKILL, find_task_by_vpid( board->autopoll_pid), 1 ); and all seems to work great on Jaunty.

Note, there may be a need to use a different function rather than find_task_by_vpid() based on name spaces. I'm not an expert and the call I used assumes the process is in the same name space which I suspect is valid and seems to work.

Revision history for this message
Don Levin (don-m-levin) wrote : Re: [Bug 242986] Re: gpib-modules-source will not compile

Thank you. I purchased an Agilent 5810 LAN/gpib gateway and use LAN
commands, which are converted to GPIB. I later learned of a $150
USB/GPIB converter. I've had too much trouble from GPIB in the past on
Fedora and Ubuntu.

On Tue, 2009-09-15 at 21:37 +0000, scott_selberg wrote:
> I replaced the kill_proc(...) call with send_sig( SIGKILL,
> find_task_by_vpid( board->autopoll_pid), 1 ); and all seems to work
> great on Jaunty.
>
> Note, there may be a need to use a different function rather than
> find_task_by_vpid() based on name spaces. I'm not an expert and the
> call I used assumes the process is in the same name space which I
> suspect is valid and seems to work.
>

Revision history for this message
Per Uddén (p-udden) wrote :

Hello,

Look at this bug report i think this is a duplicate but i could get the source to compile under karmic.

https://bugs.launchpad.net/ubuntu/+source/gpib/+bug/508130

Revision history for this message
pdevries (pdevries) wrote :

I agree that bug 508130 is a duplicate.

I also note per bug 508130 that I can get gpib 3.2.14 to compile, but I don't know whether those modules *work* in Karmic. I'm not able to upgrade the OS version on the computer(8.04) using the gpib until I know gpib will work, because I use it every day. For me 3.2.14 compiles on the 8.04 version, but those modules do not work with the gpib library in 8.04.

I also am ready to give up per comment #6. This package does not seem like it is maintained.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gpib (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.