PyGTK- installation?

2008-08-03 Thread Arne Zachlod
Hello!

i want to install some software and need PyGTK for this. i have 2 
questions: why isn't it in the repos anymore? and has anyone a build for 
me? this would be very nice, because i don't have a mokoMakefile thanks 
a lot,

Arne

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: PyGTK- installation?

2008-08-03 Thread Dimitri

I was able to install it, a few days ago, by typing this in the terminal:

opkg install python-pygtk

D


Arne Zachlod wrote:
 
 Hello!
 
 i want to install some software and need PyGTK for this. i have 2 
 questions: why isn't it in the repos anymore? and has anyone a build for 
 me? this would be very nice, because i don't have a mokoMakefile thanks 
 a lot,
 
 Arne
 
 ___
 Openmoko community mailing list
 community@lists.openmoko.org
 http://lists.openmoko.org/mailman/listinfo/community
 
 

-- 
View this message in context: 
http://n2.nabble.com/PyGTK--installation--tp667208p667342.html
Sent from the Openmoko Community mailing list archive at Nabble.com.


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: PyGTK- installation?

2008-08-03 Thread Arne Zachlod
yes, but since is isn't in the repos anymore this doesn't work. thats 
why if you need i now you have to pack it by yourself. because i have no 
MokoMakefile installed on my machine, i can't build the package by 
myself as described in the wiki and because of this i can't install mofi 
or lint-wifi or some other packages. i dont know why they aren't in the 
repos, but i miss them :(

bye, Arne


Dimitri schrieb:
 I was able to install it, a few days ago, by typing this in the terminal:

 opkg install python-pygtk

 D


 Arne Zachlod wrote:
   
 Hello!

 i want to install some software and need PyGTK for this. i have 2 
 questions: why isn't it in the repos anymore? and has anyone a build for 
 me? this would be very nice, because i don't have a mokoMakefile thanks 
 a lot,

 Arne

 ___
 Openmoko community mailing list
 community@lists.openmoko.org
 http://lists.openmoko.org/mailman/listinfo/community


 

   


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: PyGTK- installation?

2008-08-03 Thread arne anka
see
 http://www.ginguppin.de/node/20

since i switched to an 64bit t61 recently it gave me another package to  
test -- minimo does not compile anymore ... (gripes about cannot access  
nsBuildID.h: Invalid argument, whatever that means -- the file is there)

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


building minimo Re: PyGTK- installation?

2008-08-03 Thread arne anka
 since i switched to an 64bit t61 recently it gave me another package to
 test -- minimo does not compile anymore ... (gripes about cannot access
 nsBuildID.h: Invalid argument, whatever that means -- the file is there)


just for the records (since this problem came up a while ago already):
minimo does not compile out of the box w/ amd64 -- the oe bugtracker [1]  
has an still open ticket about that from 2006-09-06 ...
at least there's one step in the right direction in comment #21, add

export HOST_CC = ${BUILD_CC}
export HOST_CXX = ${BUILD_CXX}
export HOST_CFLAGS = ${BUILD_CFLAGS}

to the existing bb recipe. (the next make update will fail because  
mokomakefile or oe fails to either respect or simply overwrite the recipe,  
for what reason ever).
this will immediately make you hit another snag:

In file included from js/jsarena.c:49:
js/jsbit.h:173: error: size of array 'js_static_assert_line_173' is  
negative
make[1]: *** [js/jsarena.o] Error 1
make: *** [src] Error 2

go to jsbit.h line 173 and kill one long from [2]
JS_STATIC_ASSERT(sizeof(unsigned long long) == sizeof(JSUword));

i am no c genius but i suppose minimo/firefox defines unsigned long long  
in some incompatible way -- i sincerely hope unsigned long is still long  
enough (can somebody shed some light?)
anyway, after this minimo builds even on amd64.

[1] http://bugs.openembedded.org/show_bug.cgi?id=1391
[2] http://forum.developers.facebook.com/viewtopic.php?id=15902p=1


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: building minimo Re: PyGTK- installation?

2008-08-03 Thread Cesar Eduardo Barros
arne anka escreveu:
 to the existing bb recipe. (the next make update will fail because  
 mokomakefile or oe fails to either respect or simply overwrite the recipe,  
 for what reason ever).

To make mokomakefile respect your change (including automatically 
merging it when needed), just commit it (the openembedded directory is a 
normal git working tree). Mokomakefile does a sequence where it will 
merge your local changes instead of overwriting them, but it fails 
without a clean working tree (i.e. you cannot have uncommited changes; 
see http://www.kernel.org/pub/software/scm/git/docs/gitglossary.html for 
details).

 this will immediately make you hit another snag:
 
 In file included from js/jsarena.c:49:
 js/jsbit.h:173: error: size of array 'js_static_assert_line_173' is  
 negative
 make[1]: *** [js/jsarena.o] Error 1
 make: *** [src] Error 2
 
 go to jsbit.h line 173 and kill one long from [2]
 JS_STATIC_ASSERT(sizeof(unsigned long long) == sizeof(JSUword));
 
 i am no c genius but i suppose minimo/firefox defines unsigned long long  
 in some incompatible way -- i sincerely hope unsigned long is still long  
 enough (can somebody shed some light?)
 anyway, after this minimo builds even on amd64.

Defeating a static assert is not a good idea (size of array is 
negative is what happens when a static assert fails). The assert being 
there probably means the programmers assumed sizeof(unsigned long long) 
== sizeof(JSUword) in the code, and wanted the build to abort in case 
something went wrong and that wasn't true.

The real error should be elsewhere, in the definition of JSUword (it 
should have the same size as unsigned long long (i.e. 64 bits), but not 
necessarily the same type). Since you are on arm, unsigned long is 
probably 32 bits, which means the variable has half the size it should have.

I'm guessing it's confusing native and cross compilers; it is using the 
native compiler to find out that unsigned long is enough (64 bits on 
the AMD64 architecture), but using the cross compiler to actually 
compile the code (where unsigned long is 32 bits).

-- 
Cesar Eduardo Barros
[EMAIL PROTECTED]
[EMAIL PROTECTED]

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community