Lirc git master (0.10.0) on Raspberry PI

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Lirc git master (0.10.0) on Raspberry PI

Perse
This post was updated on .
CONTENTS DELETED
The author has deleted this message.
Reply | Threaded
Open this post in threaded view
|

Re: Lirc git master (0.10.0) on Raspberry PI

Alec Leamas
Hi!

Thanks for important feedback!

On 04/03/17 14:59, Saskia van Emst wrote:

> After running ./autogen.sh and ./configure (with --prefix=/usr because I read this somewhere and I never know which prefix I need/want on different systems T_T),
> then I ran make and ran into the following errors:

Hm... you did have the kernel headers package installed, right? If so,
this might be a bug caused by upstream not checking builds against older
kernels.  What is your kernel version?

> Checking where this was mentioned:

> --./tools/irpipe.cpp:#include "media/lirc.h"    <------------------------------- Changed


This file is not part of the core build, so no fix is required.

> Then on the next try I got syntax errors on python stuff like "async def" methods.
> After some Googling I found that this was supported on Python >= 3.5. Didn't really check further if there is something in testing/unstable (I am very new to the PI/Raspbian),
> but python 3 in Raspbian respository which I had installed is version 3.4.


So, we need to add tests in configure to disable python stuff if python
is < 3.5 - lirc should build also on python 3.4. Added this as a note on
#267

> This error I could replicate by trying to manually install the python-pkg package:
>
> --pi@raspberrypi:~/lirc-git/python-pkg $ sudo pip3.6 install .
> --Processing /home/pi/lirc-git/python-pkg
> --    Complete output from command python setup.py egg_info:
> --    Fatal Python error: PyThreadState_Get: no current thread
> --
> --
> --    ----------------------------------------
> --Command "python setup.py egg_info" failed with error code -6 in /tmp/pip-7fr71hae-build/
>
> Aparently, this error was caused by "import lirc.config". (This I found by adding some prints around it)
> Manually set version in python-pkg/setup.py (commented out original try except part importing lirc.config):

Hm... this is, as they say, odd. Can you reproduce it using:

   $ cd python-pkg;
   $ python3 -c "import lirc.config; print(lirc.config.VERSION)"


> PS. In some git commit I found a mention of an "irdroid" driver for Lirc. In current master this does not seem to exist.
> Were changes made to the irtoy driver to make it work with more hardware / fw versions or something? Or was I just lucky :)

Indeed, in master irdroid is supported  by the irtoy driver. See #269

Cheers!

--alec

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
Reply | Threaded
Open this post in threaded view
|

Re: Lirc git master (0.10.0) on Raspberry PI

Perse
This post was updated on .
In reply to this post by Perse
CONTENTS DELETED
The author has deleted this message.
Reply | Threaded
Open this post in threaded view
|

Re: Lirc git master (0.10.0) on Raspberry PI

Alec Leamas


On 05/03/17 17:04, Saskia van Emst wrote:

>
>> Hm... this is, as they say, odd. Can you reproduce it using:
>
>>    $ cd python-pkg;
>>    $ python3 -c "import lirc.config; print(lirc.config.VERSION)"
>
> Yes that causes the same problem in 'import lirc.config':
>
> --pi@raspberrypi:~/lirc-git/python-pkg $ python3 -c "import lirc.config; print(lirc.config.VERSION)"

Well, unless your system is really screwed up the config.py file which
only holds some constants shouldn't cause this.

However, importing config.py also implicitly imports __init__.py, and it
does some more things which might be the root of the trouble. Since the
reproducer is simple, you could perhaps hack this to verify the part, if
any, which is the culprit?

To be honest, I havn't thought hard enough on the cross-compile
scenario. This is not the first but of this kind.


Cheers!

--alec


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot