[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #54842] [octave forge] (instrument-control) in

From: Mike Miller
Subject: [Octave-bug-tracker] [bug #54842] [octave forge] (instrument-control) installation error on macOS with 'rpcgen -M'
Date: Tue, 16 Oct 2018 16:17:23 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36

Follow-up Comment #5, bug #54842 (project octave):

The code doesn't seem to compile without the '-M' option because the generated
API is different. With GNU rpcgen, I get errors like the following if I try to
build without '-M'

vxi11_class.cc: In member function ‘int octave_vxi11::read(char*, unsigned
vxi11_class.cc:151:37: error: cannot convert ‘Device_ReadResp*’ to
       if(device_read_1(&read_parms, &read_resp, client) != RPC_SUCCESS)

So the code that uses the rpcgen API is bound to the '-M' option.

The errors in the log file using the BSD 'rpcgen-mt' program (file #45207)
seem to indicate that the generated code is very different from what is
expected with GNU rpcgen. It seems to me that 'rpcgen' is not really a
portable standard. Maybe the program should be run on the maintainer's system
and the generated source files included in the release (similar to what Octave
does with bison and flex generated sources).


Reply to this item at:


  Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]