OESF Portables Forum
Model Specific Forums => Sharp Zaurus => Zaurus - pdaXrom => Topic started by: lekter on January 19, 2004, 01:08:35 pm
-
Release Notes for Gentoo For Zaurus 0.2.1
------------------------------------------------
Welcome to this new release of Gentoo For Zaurus. This time there are only minor changes to the distribution.
More \"real\" packages instead the busybox ones. Merged bison, procps, patch, bash, grep and coreutils into the main system. The system should compile some more packages without errors or warnings.
At the moment don\'t expect to \"emerge portage\" or to \"emerge system\" without problems. We need to update glibc and gcc before we can emerge those packages. I hope the next release will include those updated versions.
Remember that the official feed of compiled packages for zaurus is in http://zaurus.spy.org/lekter/gentooforzaurus/packages (http://zaurus.spy.org/lekter/gentooforzaurus/packages). If you compile a package and works, please send me a note (fmonera at opensistemas dot com) so I can upload to the main site.
Have fun.
Gentoo For Zaurus URL\'s
-----------------------
HOMEPAGE: http://www.opensistemas.com/Gentoo_for_Zau...urus.715.0.html (http://www.opensistemas.com/Gentoo_for_Zaurus.715.0.html)
HOWTO-DOCS: http://zaurus.spy.org/lekter/gentooforzaur...2.1/HOWTO-0.2.1 (http://zaurus.spy.org/lekter/gentooforzaurus/0.2.1/HOWTO-0.2.1)
RELEASE NOTES: http://zaurus.spy.org/lekter/gentooforzaur...EASENOTES-0.2.1 (http://zaurus.spy.org/lekter/gentooforzaurus/0.2.1/RELEASENOTES-0.2.1)
CHANGELOG: http://zaurus.spy.org/lekter/gentooforzaur...CHANGELOG-0.2.1 (http://zaurus.spy.org/lekter/gentooforzaurus/0.2.1/CHANGELOG-0.2.1)
BUGS: http://zaurus.spy.org/lekter/gentooforzaur....2.1/BUGS-0.2.1 (http://zaurus.spy.org/lekter/gentooforzaurus/0.2.1/BUGS-0.2.1)
-
awesome! keep up the great work!
Scott
-
For which architecture it is compiled? I tried to use it on my zaurus sl550 and got \"Invalid instruction\" message on any binary that I try to run from mounted partition.
-
The first packages were compiled with CFLAGS=\"-mtune=xscale -O2 -pipe\", so those packages may not work with 5000 and 5500 (only 5600+).
Easy Solution: Now I am not using any optimization flag so the current packages should work ok on 5500. Tell me the binary which fails and I will re-create the package.
Greetings.
-
Things to expect in 0.2.2:
- glibc 2.3.2-r9 ;-)))) (with threads, so mysql will be \"emergeable\")
- kernel sources
- more cleanups
- I will try to put a recent gcc too.
-
Easy Solution: Now I am not using any optimization flag so the current packages should work ok on 5500. Tell me the binary which fails and I will re-create the package.
I think all binaries. The shell dies when I try to chroot. When I try to run pwd from mounted distribution it also dies.
Rgrds
-
Ok, so it\'s bash and it\'s friends. Seems easy. I am compiling glibc, once it finishes, I will generate it. We haven\'t got a 5500 so it\'s hard to test it. Please, once you try it (I will post here) post the results.
-
I couldn\'t do anything once chrooted into the new environment until I changed the path to use /bin and /usr/bin before /usr/local/bin ,etc.
But I still couldn\'t get emerge or anything interresting to run.
Are these built from somewhere else or extracted from a rom?
Any chance of getting these new packages you referred to?
-
Hi, this project looks awesome. Been a Gentoo user for 1.5 years now...after hearing about this from the Gentoo newsletter I\'m planning on Ebaying my Ipaq and getting a Zaurus.
A question: how much memory is optimal? I only have a 128mb SD card right now to add onto the default.
-
I\'ve also just heard of it in the Gentoo Weekly Newsletter.
Since I am using Gentoo Linux for about 2 years now
and beeing pretty unsatisfied of the current OpenZaurus ROM
Distro I\'ll give this damn pretty leet gentoo on zaurus thingie a try !
YEAH ! GREAT WORK (if it works) :-)
*Zaurus 5500SL / Netgear WLAN / 128 SD*
-
Sounds like a great project, and now that I\'ve got my 2.6.1 love kernel running smoothly, I\'m all for trying this out. I have a question/suggestion, would using dietlibc make this an even better venture? (as it would allow smaller/faster/ binaries)
-
What is dietlibc for?
-
What is dietlibc for?
According to the dietlibc homepage:
Diet Libc is a libc that is optimized for small size. It can be used to create small statically linked binaries for Linux on alpha, arm, hppa, ia64, i386, mips, s390, sparc, sparc64, ppc and x86_64.
Basically, it is a compiler that makes smaller binaries (less ROM) that use up less RAM, ideal for embedded systems, and our mini-computers:lol: .
-
Using \"tiny\" versions of real applications is a bad idea for Gentoo For Zaurus IMO. This will break the package deps system. I am in the process of replacing every \"tiny\" version of an application with the corresponding \"complete\" one. This way everything is working better now.
-
(It was me)
-
Statically build binaries are great because it removes dependencies. However, on a very limitted system such as the zaurus, dynamically linked libraries can be a huge plus. With dynamically linked binaries, you can cram more applications in the same space as statically linked ones.
-
I have a couple rally stupid questions. I don\'t have a Z yet, but plan on buying a 5600 in a week or 2. But I want to understand how this works. The howto doesn\'t tell you to actually move anything to the Zaurus, and it seems as though it\'s all done over NFS. so does the Zaurus actually have gentoo on it at all? or is it just running gentoo through a chrooted NFS?
Can it be put onto a storage card?
Another stupid question: Can software be compiled right on the Zaurus without distcc, or is distcc required? this doesn\'t necessarily only mean for gentooZaurus but any Z software.
Thanks and sorry for the dumb Q\'s, I\'m just a bit confused.
-
Hi,
First Question: Gentoo For Zaurus works OK on a storage card. This way, everything will go faster, but you will have more space limitations.
Second question: Of course, software can be compiled without distcc (but this will be slow). By the way, some packages refuse to build using distcc (due to some distcc bugs).