Insomnia Sucks too.
I plopped in front of BeOS for the first time in a long while today. I ended up downloading some sourcecode for a few things, and seeing if I could hack them together / successfully compile them. I’m tossing around the idea of actually working on something. Unfortunately, I wasn’t at _all_ tired.
Finally around 1:00AM today (that’s 05:00 for you GMT’ers out there) I laid down to try and sleep. I was sorta groggy. I rolled around in bed until about 3. Then I got up, because it was obviously totally useless. No sleep for me. I think I napped for about an hour total.
So I sat back down in front of the computer, and starting hacking through the stuff again.
Minus a working file-system poll() routine, I have glibc 2.12 compiled and passing all tests on BeOS R5. But it’s better than just passing the tests. This one has native beos symantics thread safety Yes. You read that right. This one is entirely thread-safe. I implemented the glibc thread-safety interface for R5. This was insanely easy using the condvar library that’s been in use on the JRE port. All I really had to actually write by hand were the methods for allocation / getting / setting thread local variables. Which is super-easy. All told, this took longer than it should have, mostly because of the autoconf changes to support the beos threading model with pthread-style mutex and condvars through libcondvar.
I also have a working pkg-config (v0.20) installed.
I started working on libtiff, but libtool is vomiting on of all things, the library versioning string. I’ll figure it out eventually. It’s all compiling without errors.
Once I get that linking I’ll probably move along to libpng, jpegsrc, and then ATK. I’m not sure how far I’ll get before I hit a major roadblock. As it is, I could really use a new version of autoconf… I’m not able to generate a new configure script for libtiff because I’m a release behind — I think.
So I didn’t sleep last night, but I had fun playing with semaphores, thread local stacks, and learning a good deal about glibc.
August 27th, 2006 at 12:37 pm
pkg-config is no biggie to get going, but its something I Do Not Want to have on BeOS installs by default – because a number of larger apps with poorly written configure setups die when they see it on BeOS. Can’t build VLC for one thing ;)
To use the current autoconf, you have to be on R5, no net_server, you have to have the flock server installed, and you have to build the latest PERL point release. If you feel like fixing the flock()-hack to work on BONE that’d be a good night of messing around :P
August 28th, 2006 at 10:20 am
I hate pkg-config as well. I think it is a horrible idea, horrible fix, horrible thing in general.
Personally, I am all for static linking.
August 28th, 2006 at 10:56 am
If you don’t add *real* bloat like what’s happening in the windows-world… : )
September 13th, 2006 at 3:58 am
Somehow I missed this post until now, guess who else is missing sleep :)
Libtiff, png and jpeg is a step towards a working WindowMaker. libffi or ffcall would be a biggish step toward GNUstep.
I don’t like pkg-config either. Or autoconfusion.
Is everyone here unanimous we don’t want Gnome on BeOS ? :)
I’ve been playing with Tenon MachTen, seems most of SunOS Openlook/XView apps like it.
Shame most so called GNU Unix sources are Linux, and take pkgconfig, autoconf and LD for granted. Who knows, maybe oneday I’ll actually be able to use MachTen to build BeOS PPC stuff for native and X11