lcd4linux-users

[lcd4linux] release lcd4linux-0.10.0 this weekend, wishlist

[Michael R. <re...@eu...>]

Hi all,

looks like we solved the two outstanding issues 'compile i2c support'
and 'compile without python', so version 0.10.0 of lcd4linux could be
released this weekend.

It would be great if if some people could do final tests with the latest
code from CVS. It should

- compile cleanly (without any warnings) without the need of specifying
special options to 'configure'

- work :-)

Any feedback (positive and negative) would be very appreciated!


As soon as 0.10.0 is released, there are lots of things I want to start
with (keypad support, GPO's, events, timers, ...), and there sould be a
*much* shorter release cycle in the future.

To allow us to discuss and design some of the new features, I added a
new area to the wiki called "Wish List", and added one entry as a
starting point. I will glance over the tickets in the next days, and add
my own ideas there. Please have a look, and contribute!


bye, Michael

-- 
Michael Reinelt <re...@eu...>
http://home.pages.at/reinelt
GPG-Key 0xDF13BA50
ICQ #288386781

Re: [lcd4linux] release lcd4linux-0.10.0 this weekend, wishlist

[Paul K. <pau...@xs...>]

Hi Michael,

Good to hear we are now very close to an official release. :-)
But I do want to remind you, that I still have a problem with that 
AC_PYTHON_PATH macro.
If I leave the AC_PYTHON_DEVEL macro call in the configure.in file, and 
trigger a recreate of make and configure files. The whole thing blows 
up. =-O
I guess it wouldn't effect 'normal' users who only build the standard 
set of code. But someone doing a modification could end up in trouble.

cheers,

Paul

Michael Reinelt wrote:

>Hi all,
>
>looks like we solved the two outstanding issues 'compile i2c support'
>and 'compile without python', so version 0.10.0 of lcd4linux could be
>released this weekend.
>
>It would be great if if some people could do final tests with the latest
>code from CVS. It should
>
>- compile cleanly (without any warnings) without the need of specifying
>special options to 'configure'
>
>- work :-)
>
>Any feedback (positive and negative) would be very appreciated!
>
>
>As soon as 0.10.0 is released, there are lots of things I want to start
>with (keypad support, GPO's, events, timers, ...), and there sould be a
>*much* shorter release cycle in the future.
>
>To allow us to discuss and design some of the new features, I added a
>new area to the wiki called "Wish List", and added one entry as a
>starting point. I will glance over the tickets in the next days, and add
>my own ideas there. Please have a look, and contribute!
>
>
>bye, Michael
>
>  
>

Re: [lcd4linux] release lcd4linux-0.10.0 this weekend, wishlist

[Michael R. <re...@eu...>]

Hi Paul,

> But I do want to remind you, that I still have a problem with that
> AC_PYTHON_PATH macro.
> If I leave the AC_PYTHON_DEVEL macro call in the configure.in file, and
> trigger a recreate of make and configure files. The whole thing blows
> up. =-O

Really? AC_PYTHON_DEVEL should not be called unless you specify
"--with-python".... that's why I added thsi switch. Don't tell me that
this didn't help :-)


bye, Michael

-- 
Michael Reinelt <re...@eu...>
http://home.pages.at/reinelt
GPG-Key 0xDF13BA50
ICQ #288386781

Re: [lcd4linux] release lcd4linux-0.10.0 this weekend, wishlist

[Paul K. <pau...@xs...>]

Michael Reinelt wrote:

>Hi Paul,
>
>  
>
>>But I do want to remind you, that I still have a problem with that
>>AC_PYTHON_PATH macro.
>>If I leave the AC_PYTHON_DEVEL macro call in the configure.in file, and
>>trigger a recreate of make and configure files. The whole thing blows
>>up. =-O
>>    
>>
>
>Really? AC_PYTHON_DEVEL should not be called unless you specify
>"--with-python".... that's why I added thsi switch. Don't tell me that
>this didn't help :-)
>
>
>bye, Michael
>
>  
>
Mea culpa. I didn't test this changes yet. But anyway, if I do want 
python (and I *do* have python installed) I still would have the 
problem. right?

Paul

Re: [lcd4linux] AC_PYTHON_DEVEL (was: release lcd4linux-0.10.0 this weekend, wishlist)

[Michael R. <re...@eu...>]

Hi Paul,

>>> But I do want to remind you, that I still have a problem with that
>>> AC_PYTHON_PATH macro.
>>> If I leave the AC_PYTHON_DEVEL macro call in the configure.in file, and
>>> trigger a recreate of make and configure files. The whole thing blows
>>> up. =-O

>> Really? AC_PYTHON_DEVEL should not be called unless you specify
>> "--with-python".... that's why I added thsi switch. Don't tell me that
>> this didn't help :-)

> Mea culpa. I didn't test this changes yet. But anyway, if I do want
> python (and I *do* have python installed) I still would have the
> problem. right?

Maybe. I renamed the twy python macros to MY_... to ensure they don't
collide with somnething else.

I just checked in. Could you please try again with "--with-python"?


bye, Michael

-- 
Michael Reinelt <re...@eu...>
http://home.pages.at/reinelt
GPG-Key 0xDF13BA50
ICQ #288386781

Re: [lcd4linux] AC_PYTHON_DEVEL

[paul k. <pau...@xs...>]

Hi Michael,

Maybe. I renamed the twy python macros to MY_... to ensure they don't

>collide with somnething else.
>
>I just checked in. Could you please try again with "--with-python"?
>
>
>bye, Michael
>
>  
>
I just got the latest version from CVS.
running ./bootstrap
directly produces this error
tux lcd4linux # ./bootstrap
aclocal: macro `AM_PATH_PYTHON' required but not defined

./configure seems to work ok.

But make still gives the same problem

tux lcd4linux # make
cd . && aclocal-1.4
aclocal: macro `AM_PATH_PYTHON' required but not defined
make: *** [aclocal.m4] Error 1
tux lcd4linux #

As you can see I am not even using the --with-python option at moment

So I still do have a problem, and it is even worse then I thought. I am 
not able to build the CVS version directly. :-(

Ok, did some further checking and searching. Turns out that I swig 
(www.swig.org) installed on my system as part of a dependency to another 
package. I assume that swig installed a file swig.m4 in the 
/usr/share/aclocal/
This file contains a macro PYTHON_DEVEL which in turn requires 
AM_PATH_PYTHON

I still can't understand how this can affect the lcd4linux build, but 
removing the swig.m4 file solved the build process.
Attached is this swig.m4 file, so if anyone cares to have a look at it. 
Feel free.
Question remains, do we have a problem or does swig have a problem.

cheers,

Paul

Re: [lcd4linux] AC_PYTHON_DEVEL

[Michael R. <re...@eu...>]

Hi Paul,

> Ok, did some further checking and searching. Turns out that I swig
> (www.swig.org) installed on my system as part of a dependency to another
> package. I assume that swig installed a file swig.m4 in the
> /usr/share/aclocal/
> This file contains a macro PYTHON_DEVEL which in turn requires
> AM_PATH_PYTHON

Good investigations, paul!

I can confirm the problem here. As soon as I install the swig.m4 file to
/usr/share/aclocal, I get the same error.

"I've seen all the things in Heaven and Earth"
"I've seen many things in Hell"

The problem is that swig uses a macro called PYTHON_DEVEL, while
lcd4linux uses one called AC_PYTHON_DEVEL (or MY_PYTHON_DEVEL). Somehow
aclocal ignores the AM_ or MY_ prefix, and executes the swig.m4, where I
found a reference to AM_PATH_PYTHON.

I renamed the AC_PYTH_PYTHON to AC_PATH__PYTHON (note the double
underscore), now it works here.

please test!


bye, Michael

-- 
Michael Reinelt <re...@eu...>
http://home.pages.at/reinelt
GPG-Key 0xDF13BA50
ICQ #288386781

Re: [lcd4linux] AC_PYTHON_DEVEL

[Paul K. <pau...@xs...>]

Michael Reinelt wrote:

>Hi Paul,
>
>  
>
>>Ok, did some further checking and searching. Turns out that I swig
>>(www.swig.org) installed on my system as part of a dependency to another
>>package. I assume that swig installed a file swig.m4 in the
>>/usr/share/aclocal/
>>This file contains a macro PYTHON_DEVEL which in turn requires
>>AM_PATH_PYTHON
>>    
>>
>
>Good investigations, paul!
>
>I can confirm the problem here. As soon as I install the swig.m4 file to
>/usr/share/aclocal, I get the same error.
>
>"I've seen all the things in Heaven and Earth"
>"I've seen many things in Hell"
>
>The problem is that swig uses a macro called PYTHON_DEVEL, while
>lcd4linux uses one called AC_PYTHON_DEVEL (or MY_PYTHON_DEVEL). Somehow
>aclocal ignores the AM_ or MY_ prefix, and executes the swig.m4, where I
>found a reference to AM_PATH_PYTHON.
>
>I renamed the AC_PYTH_PYTHON to AC_PATH__PYTHON (note the double
>underscore), now it works here.
>
>please test!
>
>
>bye, Michael
>
>  
>
Michael in which file did you make that change? I assumed you did it in 
python.m4, but it is not in CVS. And when I try it myself, it doesn't 
work. :-(

cheers,

Paul