Build SUCCESS!

Finally I completed my OOo_m40 build on the CDot computers. Now I just need to get it up and running on my local machine which I will work on after dinner. The problem I was having was solved by my classmate Daeson, he emailed me a patch he wrote to solve the error, unfortunatly when I tried the patch a part of it failed. I figured it was because I tried a variety of different patches from the internet that didn't solve my problem so I removed my current build and started again from scratch. My build still crashed in the same place, but at least now I knew I was only going to apply 1 patch instead of the 3 or 4 I tried earlier. After the patch was complete I attempted to build again but got an error saying that "dict-ru:: No such file or directory" I found the file in my filesystem so I tried building it again and it finally worked.

If anyone is still working on the build and crashes in the same spot as I did here is a link to Daeson's patch

OOo Still not Building

Well after trying for a couple days to build Open Office M40 I am still having problems. My last blog post talked about an error which was fixed pretty easily, turned out I was using the wrong -p number for the patch provided(-p0 should have been -p1). This error is a little trickier. Here is a pastebin of my CDot error.

I assume that the build should be close to completing once this bug is fixed since the build lasts a really long time, but I'm not 100% sure.

I am also building OOo M40 on my local machine, and that is going much worse then my build on the CDot computer. Here is a pastebin of the output of my make build.

Still Building

Well I finally had my problem of no disk space on the CDot computers sorted out, so I was able to begin building. Thus far the build hasn't treated me too badly and I've only ran into 1 problem that I haven't yet been able to solve. Luckily for me my classmate Daeson seemed to run into the same problem. Unfortunately his solutions didn't help me out, so I am waiting on irc for some help. The exact error message reads:

rpmbuild: /home/bbarcick/DEV300_m40/solver/300/unxlngx6.pro/lib/libnss3.so: version `NSS_3.10' not found (required by /usr/lib64/librpmio-4.6.so)
dmake:  Error code 1, while making '../unxlngx6.pro/bin/noarch/fake-db-1.0-0.noarch.rpm'

ERROR: Error 65280 occurred while making /home/bbarcick/DEV300_m40/setup_native/scripts
rmdir /tmp/26213
dmake:  Error code 1, while making 'build_instsetoo_native'

I guess while I wait I can start my Mac build. Hopefully that goes a little bit better

Building Open Office Attempt 1 of Many

I was attempting to build Open Office recently unfortunately it has not gone well, at least not yet. I tried building on one of the CDot computers, this did not work and I couldn't figure out why. To check out the source code I was using the nLogTime bash script that my professor Fardad provided so that I would know how long it took to complete the checkout. This script also takes the output and saves it into an output log. Unfortunatly when checking out I didn't check the output log. I assumed that any errors would still be shown on the screen, so no errors meant the svn must have finished checking everything out.

This did not happen, after hours of trying to figure out why my build didn't work I decided to check the output log and there was an svn error, which makes sense that I wasn't able to build it. The error said there was no more room on the device, so I tried working on another machine, I got the exact same error so I will have to look into that tomorrow when I am in school. If anyone else had this problem I would greatly appreciate if you told me how you fixed it.

Instead of waiting around I checked out the code on my local machine, and while the build seems to be working for now it sure is taking an extremly long time, mostly because I rarely boot into Ubuntu and I need to install a lot of different packages/updates. Hopefully I'll have it fully built on my home machine before Thursday night, and hopefully I can do the build on the CDot machines before Friday.

The Cathedral Builder

I was reading The Cathedral and the Bazaar by Eric Raymond and it got me thinking that in my years of schooling I have been trained to be a cathedral builder. Every thing we developed in school was something we worked on alone, or in small groups. We would even have competitions to see who could write better AI, when if we all worked together we could have easily written something that was not only better but something that would have taken a fraction of the time to write and debug.

The thing that stuck out to me the most in the reading was Linus' Law "Given enough eyeballs, all bugs are shallow." This quote is very significant because of how true it is. Often times we look at code trying to debug it and miss bugs because we are reading what we expect to be there and not whats actually written there. Also, with how flexible coding is, having a lot of people staring at the code will produce many different ways of fixing the bug, one way would definitely be the easiest.

I also agreed with the part about how the open source software is so good because people do it because they genuinely like what they are doing. All the programs I write, if I am not into writing them then I'll do the bare minimum but if I am excited about a certain project I will not only do what is required, I will put even more effort into it to make it that much better.

Mozilla Developer Days

This past Monday and Tuesday my school hosted the Mozilla Developer Days. Since I didn't have any classes on Monday, and only 1 class on Tuesday I thought it would be a good idea to go, and I'm glad I did.

Being new to the open source world, this was a good opportunity to talk to people who have a bit more experience then I do. I met one of the creators of Songbird. He mentioned in his presentation that when he started working on the project and initially felt overwhelmed with it all. Since I felt the same way I thought he'd be a good person to talk to. He re-assured me that it is fairly easy to jump in and start coding. There is a lot of documentation on the internet to help out plus you can always find people on IRC.