Re: Re: Re: Octave in Google Summer of Code 2013 / Low Level I/O

[Juan Pablo Carbajal]

On Thu, Feb 28, 2013 at 3:43 PM, Stefan Mahr <address@hidden> wrote:
>>> warning: marking 'gpib' as not implemented
>>> warning: marking 'gpib_read' as not implemented
>>> warning: marking 'gpib_write' as not implemented
>>> warning: marking 'gpib_timeout' as not implemented
>>> warning: marking 'gpib_close' as not implemented
>>>
>>> Is gpib properly documented?
>>>
>>> I assume gpib cannot be build since linux-gpib is not installed. An option
>>> would be to make a dummy function if libs are not installed.
>>>
>>
>> The best would be to print a message telling the user they need that.
>> I am not talking about a big chekcing, just a message. Cause in the
>> case users use the system package manger it should it by itself
>>
>> Also, we will get some complaints from the Debian package managers, probably.
>
> Sorry, I did not understand.
>
> Where the warning "marking 'gpib' as not implemented" comes from? I assume 
> the release script doesn't build the gpib functions since linux-gpib is not 
> installed. That's why the documentation can't be build correctly, right?
>
> I could add some defines to instrument-control source, that gpib, gpib_read 
> a.s.o. is always build. Resulting functions would be dummy functions only 
> printing out a "not supported" message.
>
That sounds like a temporal solution, yes.

>
>> Alas, I can't find any package gpib in my Debian distribution. And I
>> see there are issues with the kernel version....
>> http://linux-gpib.sourceforge.net/
>>
>> I have 3.6 and probably it doesn't work here... mmm... maybe we aren't
>> done with GPIB.
>
> GPIB works with actual kernel. The svn is still active. I prepared a package 
> for Ubuntu 12.10:
> https://launchpad.net/~dac922/+archive/gpib

Ok, I will try to install from sources so I can test the package with
some agilent functions generators I have at hand these days.