[Top][All Lists]

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

Re: [Paparazzi-devel] Ivy-c on paparazzi-uav PPA & Ivy-python Python 3.x

From: Felix Ruess
Subject: Re: [Paparazzi-devel] Ivy-c on paparazzi-uav PPA & Ivy-python Python 3.x patch
Date: Wed, 30 Dec 2015 12:58:18 +0100

Hi Cindy,

In ivy-c it was basically it was assumed that you build the package on your system with same kernel version where you run it later...

I had the same problem on my BBB image some time ago and hence asked Alexandre (ivy-c maintainer) to change it to only print a warning and not exit with an error anymore...
So it's in SVN but (since the server is often not properly reachable) I never got around to update the Debian/Ubuntu packages...
The version on launchpad is 3.15.1 (SVN rev 3641), so only missing that change:

If at some point I can actually update my local ivy-c checkout without a connection timeout, I'll upload new packages so you can just use the armhf binaries even if your kernel version is older...
@Alexandre: maybe you could update the minor version and changelog in SVN first so that I don't start creating new versions myself...

Cheers, Felix

On Wed, Dec 30, 2015 at 10:51 AM, Gautier Hattenberger <address@hidden> wrote:

We have already a patch for ivy-python 3 at ENAC, just didn't pushed it upstream before leaving for vacation.
I'll check next week for the ivy-c issue.


Le 30/12/2015 03:27, cxiao a écrit :

I recently installed the ivy-c-dev package from the paparazzi-uav PPA on an
Odroid U3, an ARM-based single-board computer, running Ubuntu 14.04. When
calling IvyStart() and opening a socket, however, the ivy-c library attempts
to apply SO_REUSEPORT option to the socket, which is not supported by the
Odroid's kernel.

The version of ivy-c that I installed from the PPA immediately exits the
program upon SO_REUSEPORT not being successfully applied, as per  this code
. However, I then checked out the ivy-c source from SVN and recompiled the shared library on the Odroid; the version from SVN just  warns you
if setting SO_REUSEPORT fails
<>  , rather
than immediately crashing.

My questions are:
- What version of the ivy-c source code from SVN are the libraries in the
ivy-c-dev package from the PPA built from?
- What are the consequences of not being able to use SO_REUSEPORT for Ivy?
Would it be possible to update the PPA package to reflect the latter
behaviour of not immediately exiting when setting this port option?

In addition, another member of our group, Cameron Lee, forked from the ivy
SVN some time ago in order to complete porting ivy-python to Python 3.x.
His fork is here <>  . Would it be
possible to review and merge his changes into the SVN repository, as well as
update the ivy-python package on pypi?

(apologies if this is the wrong place to post this; the ivy mailing list
does not seem to be very active)


View this message in context:
Sent from the paparazzi-devel mailing list archive at

Paparazzi-devel mailing list

Paparazzi-devel mailing list

reply via email to

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