OESF | ELSI | pdaXrom | OpenZaurus | Zaurus Themes | Community Links | Ibiblio

IPB

Welcome Guest ( Log In | Register )

Profile
Personal Photo
Options
Options
Personal Statement
jh doesn't have a personal statement currently.
Personal Info
jh
Age Unknown
Gender Not Set
Location Unknown
Birthday Unknown
Interests
No Information
Statistics
Joined: 20-November 03
Profile Views: 884*
Last Seen: 3rd July 2008 - 09:34 PM
Local Time: May 4 2015, 09:13 PM
115 posts (0 per day)
Contact Information
AIM No Information
Yahoo No Information
ICQ No Information
MSN No Information
Contact Private
* Profile views updated each hour

jh

Members


Topics
Posts
Comments
Friends
My Content
21 Sep 2005
Hi,

I've got rc11 running on my C1000 and I'm trying to get some things recompiled that I had working on rc10. I've got the new SDK but it has a requirement for libiconv.so.2 which I don't have installed and wasn't in the previous SDK. So, a couple questions:

Is there a reason for the new dependency?

Can I use the previous SDK for rc11?

Thanks!

jason
22 Aug 2005
Hi:

Just looking for any tips/tricks/hints, etc... for cross-compiling.

I've had pretty good luck so far using the latest sdk from the pdaXrom folks... well-behaved configure scripts work fine. I've compiled and packaged the latest libxml2, libxslt, some python modules, etc...

Every now and then, though, I find a configure script that doesn't behave well... specifically, it tries to compile test applications which, of course, fail because I'm cross-compiling. What do folks usually do to get around this? In the past I've edited by hand the configure script, but in the library I'm trying to compile now, that's pretty painful (there are a lot of them).

Also, has anyone looked at using scratchbox for pdaxrom compiling? I played around with it a little bit trying to setup a gpe compile environment and it seemed pretty slick. It might be worth pursuing as it lets you compile "natively" inside the environment. Pretty slick.

jason
2 Jun 2005
Hi,

With some help from the #oe folks a little while ago I've been tweaking the keymap for my C1000 running OZ/Opie 3.5.3. My modifications are:

* Enable right shift key
* Remap the two japanese keys near the bottom left of the keyboard: the left one is mapped to tilde and the right one is mapped to / (slash). I found this to be helpful when typing directories.
* 'Home' key mapped to F12 so it works in Opie
* Scroll switch on the side (used in portrait mode) is mapped to up and down and the "Ok" key is mapped to 'Return' and the "Cancel" key is mapped to Escape

Unfortunately I still haven't gotten the on/off button to work... I tried mapping it to F34 which seems to be the 'Power' key in qte, but that didn't work. In the meantime I've mapped the 'mail' key in the Buttons applet to the suspend call which works just fine.

I've attached my 'full-keys' output. In order to install the keymap you need to have the console-utils ipk installed. In order to install that ipk you'll have to enable force-overwrite since it includes a couple binaries that will replace the busybox version (chvt is one, can't remember the others). You can always relink those binaries to busybox if you have problems.

And finally, I modified my /etc/init.d/bootmisc.sh and added a call to loadkeys which loads up the keymap before opie is started (anytime you change the keymap you must restart opie). That addition:
CODE
if test -e /home/root/full-keys    
then                                
   /usr/bin/loadkeys /home/root/full-keys
fi                                                                


Someday I'll generate a config that can be used as a patch to the kernel, I just haven't quite gotten there yet.

Hope this is helpful for folks...

jason
Attached File(s)
Attached File  full_keys.txt ( 12.27K ) Number of downloads: 104
 
2 Jun 2005
Hi,

I'm writing an app for my C1k + OZ 3.5.3 with python and have stumbled across a few things that needed tweaks, and one thing I can't get past:

I'm using urllib which imports cookielib which imports logging which imports calendar which imports datetime (whew!) all of which are missing (other than urllib) from the python-2.4.1-manifest.inc for the netclient package.

Adding them to the package has been easy (patch is trivial but I can generate it if needed) except for datetime which is a compiled library. I noticed that none of the .so files that should be in lib-dynload are actually there. Checking the log reveals:

CODE
ccache arm-linux-gcc -march=armv5te -mtune=xscale -shared -L/data/openembedded/akita/tmp/staging/arm-linux/lib -Wl,-rpath-link,/data/openembedded\
/akita/tmp/staging/arm-linux/lib -Wl,-O1 -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -I. -I/data/openembedded/akita/tmp/work/python-2.4.1-ml1/Pytho\
n-2.4/Include build/temp.linux-i686-2.4/data/openembedded/akita/tmp/work/python-2.4.1-ml1/Python-2.4/Modules/datetimemodule.o build/temp.linux-i6\
86-2.4/data/openembedded/akita/tmp/work/python-2.4.1-ml1/Python-2.4/Modules/timemodule.o -L/data/openembedded/akita/tmp/staging/arm-linux/lib -lm\
-o build/lib.linux-i686-2.4/datetime.so                                                                                                          
*** WARNING: renaming "datetime" since importing it failed: build/lib.linux-i686-2.4/datetime.so: ELF file OS ABI invalid                        


This is an up-to-date (r237) bitbake, latest pull from bk, using openzaurus-3.5.3 as the distro in my local.conf.

Thanks!

jason
22 Sep 2004
Hi folks,

Not sure what the best way of getting this first into OE and then into OZ is, but...

In order to use the micro-emacs app (and maybe other stuff), you'll need an /etc/terminfo directory with some terminfo files. I've tar'ed up the directory from my OZ 3.3.6p1 image here:

terminfo.tar.gz

jason
Last Visitors


11 Jan 2010 - 9:27


12 Jan 2008 - 7:46

Comments
Other users have left no comments for jh.

Friends
There are no friends to display.
RSS Lo-Fi Version Time is now: 4th May 2015 - 08:13 PM