Hi! Please find attached linux-gpib-3.2.08.ebuild and a patch so that it will compile against 2.6.18 and newer kernels. The Linux GPIB Package is a support package for GPIB (IEEE 488) hardware. The GPIB interface is widely used in science for the communication between various experimental hardware and PC. The package contains kernel driver modules, and a C user-space library with Guile, Perl, PHP, Python and TCL bindings. The API of the C library is intended to be compatible with National Instrument's GPIB library. I suggest sys-apps/linux-gpib. Anton.
Created attachment 109189 [details] linux-gpib-3.2.08.ebuild main ebuild
Created attachment 109190 [details] files/linux-gpib-3.2.08-drivers-gpib-sys-osinit.c.patch patch to compile with 2.6.18 and newer kernels
Created attachment 109192 [details] ChangeLog ChangeLog
Created attachment 109303 [details] rewriten ebuild I rewrote the ebuild to aviod usage of the addwrite, making it transparrent to the sandbox.
Created attachment 109305 [details] new ChangeLog
Created attachment 109306 [details] files/linux-gpib-3.2.08-drivers-make.am.patch One of two new patches which are needed to make the ebuild transparrent to the sandbox.
Created attachment 109307 [details] files/linux-gpib-3.2.08-drivers-make.in.patch Second of two new patches which are needed to make the ebuild transparrent to the sandbox.
I rewrote the ebuild to aviod usage of the addwrite, making it transparrent to the sandbox. See new attachments.
Created attachment 116590 [details] linux-gpib-3.2.09.ebuild the ebuild for the recently released new version of the package.
Created attachment 116591 [details] files/linux-gpib-3.2.09-drivers-make.am.patch the patch needed to overcome the sandbox violation
Created attachment 116593 [details] files/linux-gpib-3.2.09-drivers-make.in.patch the patch needed to overcome the sandbox violation
Created attachment 116595 [details] ChangeLog updated ChangeLog
Created attachment 118700 [details] linux-gpib-3.2.09.ebuild Fixed bug which caused the sandbox violation when emerging for the first time (thanks to Felix for the bug report).
Created attachment 118701 [details] files/linux-gpib-3.2.09-drivers-make.am.patch Fixed bug which caused the sandbox violation when emerging for the first time (thanks to Felix for the bug report).
Created attachment 118703 [details] files/linux-gpib-3.2.09-drivers-make.in.patch Fixed bug which caused the sandbox violation when emerging for the first time (thanks to Felix for the bug report).
Created attachment 118705 [details] ChangeLog
Created attachment 135320 [details] ebuild which works with 2.6.23 kernels I prepared the patch for the 2.6.23 kernels (see next attachment) and rewrote the ebuild in accordance. Enjoy.
Created attachment 135322 [details, diff] patch for the 2.6.23 kernels the patch for kernels newer than 2.6.23. BTW, here earlier than on the official site..))
Created attachment 135324 [details] updated changelog updated changelog
Created attachment 143853 [details] linux-gpib-3.2.10.ebuild Version bump ebuild
Created attachment 143854 [details] files/linux-gpib-3.2.10-drivers-make.am.patch Patch required for the new ebuild to work
Created attachment 143855 [details] files/linux-gpib-3.2.10-drivers-make.in.patch Patch required for the new ebuild to work
Created attachment 143857 [details] ChangeLog Updated Changelog file.
Created attachment 165577 [details, diff] Patch to update the ebuild to 3.2.10-r1 This patch fixes two issues with the 3.2.10 ebuild: 1. The name of guile has changed from dev-util/guile to dev-scheme/guile 2. The python bindings fail to install properly, because the install procedure does not handle DESTDIR properly. Solving this issue requires two additional Makefile patches, both of which can and should be upstreamed (upstream is now active).
Created attachment 165579 [details, diff] Makefile patch required for 3.2.10-r1
Created attachment 165581 [details, diff] Other Makefile patch required for 3.2.10-r1
Also, the 3.2.10-r1 ebuild and associated patches works cleanly if the ebuild (and all 4 patches) are renamed for the 3.2.11 version bump. So, bump.
Thank you, Ben, for the patches. It is not likely that I will continue to work on this ebuild. Because at my new job the IT team cares about all low-level drivers, protocols, etc. Hope someone can maintain future versions of the ebuuild.
(In reply to comment #27) > Also, the 3.2.10-r1 ebuild and associated patches works cleanly if the ebuild > (and all 4 patches) are renamed for the 3.2.11 version bump. So, bump. Hello, can I download it anywhere? THX.
(this is an automated message based on filtering criteria that matched this bug) 'EBUILD' is in the KEYWORDS which should mean that there is a ebuild attached to this bug. This bug is assigned to maintainer-wanted which means that it is not in the main tree. Heuristics show that no Gentoo developer has commented on your ebuild. Hello, The Gentoo Team would like to firstly thank you for your ebuild submission. We also apologize for not being able to accommodate you in a timely manner. There are simply too many new packages. Allow me to use this opportunity to introduce you to Gentoo Sunrise. The sunrise overlay[1] is a overlay for Gentoo which we allow trusted users to commit to and all users can have ebuilds reviewed by Gentoo devs for entry into the overlay. So, the sunrise team is suggesting that you look into this and submit your ebuild to the overlay where even *you* can commit to. =) Because this is a mass message, we are also asking you to be patient with us. We anticipate a large number of requests in a short time. Thanks, On behalf of the Gentoo Sunrise Team, Jeremy. [1]: http://www.gentoo.org/proj/en/sunrise/ [2]: http://overlays.gentoo.org/proj/sunrise/wiki/SunriseFaq
See the following URL for newer developments (before this goes into the tree): http://git.overlays.gentoo.org/gitweb/?p=user/dilfridge.git;a=tree;f=sci-libs/linux-gpib;hb=HEAD
Added to the portage tree, package.masked for an initial testing and cleanup period. Please add feedback here to this bug (it will remain open until the package mask is removed).
Hi, Recent kernel headers (2.6.37 and higher) no longer have init_MUTEX, init_MUTEX_LOCKED and DECLARE_MUTEX defined in linux/semaphore.h. Because of this, compilation of agilent_82357a.c and ni_usb_gpib.c fails. In fact, no kernel modules be installed. The MUTEX functions should be replaced with sema functions: init_MUTEX(tmp) --> sema_init(tmp, 1) MUTEX_LOCKED(tmp) --> sema_init(tmp, 0) DECLARE_MUTEX(tmp) --> DEFINE_SEMAPHORE(tmp) I will attach 2 patches. Regards, Joop
Created attachment 272045 [details, diff] patch for agilent 82357 card
Created attachment 272047 [details, diff] patch for NI usb card
After notifying upstream about this issue, I was told there is a 3.2.16 version available, which fixes this. :-) http://sourceforge.net/projects/linux-gpib/files/linux-gpib%20for%202.6.x%20kernels/3.2.16/
(In reply to comment #36) > After notifying upstream about this issue, I was told there is a 3.2.16 version > available, which fixes this. :-) > > http://sourceforge.net/projects/linux-gpib/files/linux-gpib%20for%202.6.x%20kernels/3.2.16/ Is bumped in portage, give it a try! Please tell me if it works for you, if yes I will remove the package mask...
Thanks! Compiles okay with 2.6.37-gentoo-r4 kernel. Tested with a NI PCI-GPIB card, communicating with an agilent network analyzer. Works okay, in a quick test I wrote a little c-program using the gpib library which sets and reads frequencies from the analyzer. No problems. Platform is amd64, so you might want to unmask that also. :-)
Python bindings also working: ------------------------------------ #!/usr/bin/python import gpib na = gpib.find ("hp8753") gpib.write (na, 'PRES;') gpib.write (na, 'MARK1 1 GHZ;') gpib.write (na, 'OUTPMARK;') value = gpib.read (na, 256) print (value) ------------------------------------ $ ./hp8753_test.py 2.261621E-01, 2.470165E+32, 1.000000000E+09
OK great. Package mask removed, time to close this bug! :)
