Reply
Thread Tools
Guest | Posts: n/a | Thanked: 0 times | Joined on
#1
Having some troubles getting alarmd to work on the vmware sdk.

Attempting to import alarm, alarmd, libalarm, etc all gives module not found errors.

So, I checked out python-alarm from garage.maemo.org/svn/pymaemo/packages/python-alarm/trunk, and tried to compile that, and this is what I got:

Code:
maemo@maemo-desktop:/scratchbox/users/maemo/home/maemo/0.1-0maemo1$ sudo -E python setup.py install
running install
running build
running build_ext
cythoning alarm.pyx to alarm.c

Error converting Pyrex file to C:
------------------------------------------------------------
...
                     ^
------------------------------------------------------------

/scratchbox/users/maemo/home/maemo/0.1-0maemo1/alarm.pyx:2:22: 'import *' not supported
building 'alarm' extension
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fPIC -I/usr/include/alarmd -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/python2.5 -c alarm.c -o build/temp.linux-i686-2.5/alarm.o -Werror
gcc: alarm.c: No such file or directory
gcc: no input files
error: command 'gcc' failed with exit status 1
Anyone know what the solution to this is? I don't really care how I do it, i'd just like to be able to import alarm

Thanks
 
Posts: 432 | Thanked: 645 times | Joined on Mar 2009
#2
Hi,

Originally Posted by code177 View Post
Having some troubles getting alarmd to work on the vmware sdk.
I have problems to understand your setup exactly. Do you want to run the python-program inside the sdk and use python-alarm for it? Then you could install python-alarm directly from extras repository and use it. Be aware to start python inside scratchbox with python2.5 otherwise it will use python 2.3.

If you want to build it inside scratchbox from the trunk, you can do that as well without problems. I doubt that you can build or use it outside scratchbox, as the libalarm is just available there. But I might be wrong.

Cheers Daniel
 
Guest | Posts: n/a | Thanked: 0 times | Joined on
#3
Originally Posted by danielwilms View Post
I have problems to understand your setup exactly. Do you want to run the python-program inside the sdk and use python-alarm for it?
That's right!

For some reason doing "import alarm" in python within scratchbox says it doesn't exist. I would have thought it would have come already working, but apparently not.

I couldn't find it in http://repository.maemo.org/extras/pool/fremantle/ so I used https://garage.maemo.org/svn/pymaemo.../python-alarm/ - which produces the error above.

Any ideas?
 
Posts: 631 | Thanked: 837 times | Joined on May 2007 @ Milton, Ontario, Canada
#4
Hmmm that's odd, I just tried it on my SDK VM box here... all I did was log into scratchbox, set the target for Fremantle_X86, then ran "apt-get install python-alarm".

It did a bunch of stuff, download python 2.5 and all the rest of it, and once done I just typed "python2.5" to bring up the cli... typed "import alarm" and it worked just fine, no errors or anything...

From inside scratchbox try running "apt-cache search alarm", see if it lists the python-alarm package (or any packages); when I first setup the SDK VM image I had all kinds of problems because some goofy Nokia proxy was setup for APT, so it never actually connected to the repositories or anything.
 
Guest | Posts: n/a | Thanked: 0 times | Joined on
#5
hm.. I tried this and no luck. Maybe I need to somehow fix my repositories. How would I do that?
 
Posts: 631 | Thanked: 837 times | Joined on May 2007 @ Milton, Ontario, Canada
#6
In scratchbox, type "ls /etc/apt/apt.conf.d/"

See if there's one that says 90proxy, or something along those lines... it'll contain the word proxy, and start with 90-something (I don't know exactly anymore because I deleted it from my scratchbox!). If it's there, that's your problem... move it somewhere else, run apt-get update, and this time all should work as expected...
 

The Following User Says Thank You to jolouis For This Useful Post:
Guest | Posts: n/a | Thanked: 0 times | Joined on
#7
This turned out to be the problem. Once I moved 99proxy and re-ran apt-get update everything worked fine

Thanks!
 
Reply


 
Forum Jump


All times are GMT. The time now is 06:55.