1
edit
Changes
→Acknowledgements and Links
= Description of work + goals =
* Goal
Our Primary Goal and Focus was to package the DXR 'viewsource' web application tool and dependencies, (Dehydra and Jshydra), as a first step towards packaging the full DXR system for wide, reliable distribution. DXR contains components such as Dehydra, Jshydra, Viewsource, and a Modified GCC compiler. We had to essentially build each of these from scratch in DXR was originally created by David Humphrey as an attempt to put it all together and finish in timeexperiment.
*Definition of Packaging
Packaging is defined as the process of archiving files together along with information about the package, like its current version, a description of what the package is meant to do, etc. Packages are deployed in order to solve a software issue or resolve a package dependency. New version of packages are constantly coming out with new features, patches, and fixes that improve upon the last. Packages are what make up any Linux system and as such are a very fundamental part of any open source project.
Packages are all grouped together in what are called "Package Repositories" developed and maintained by "Repo Masters". This is where the packages come from when you "yum install" any package off your machine. The DXR repository is located on scotland and can be accessed through the web browser - [http://scotland.proximity.on.ca/DXR/ DXR]
* GCC –
The challenge we face on the final part of the project is to build on a beta release of a compiler. Luckily for us we are able to reference our work with an earlier version of this compiler.
The first task was to create a SPEC file. A SPEC file is file that has a list of instructions that will be used by a building tool to build our packages. The problems we faced with our build are a bunch or errors linking back to libraries that it cannot find and incorrect path names. After lots of Google searching and communication on Seneca’s Channel on IRC, we were able to fix that issue. The solutions to our problems are using the correct options to build and use patches that will alter the code. After solving the issue we continued to build but this time we came across an issue, that even Google cannot help us with. To try to fix our issue we tried to email the package create of GCC, but sadly we did not hear back from them.
Since our attempt to create a SPEC file was a disaster, we copied the SPEC file from the previous release of an older package and modified it to fix our needs. With the numerous amount of modification to the SPEC file we started the build process, unlike our scratch SPEC file, the build times were significantly less. The errors would happen in the earlier stage of the build. These errors consist of missing dependencies, missing files, missing paths to directories. The missing dependencies are a easy fix, I just needed to install them, but the missing files, and other errors we had trouble solving. Again with communication in the Fedora community, we were unable to solve it. A suggestion was to do a command line build.
After speaking with the Fedora community, they suggested that we try to do a command line build from the GCC 4.5 tarball. With their advice, we extracted the GCC 4.5 file and started building from command line. The result of the compile the source and install it successfully into our system.
Now our remaining task is to compare the configuration settings between the source and our build tool and work around our findings. Until we can figure this problem, our project is on a stand still.
(build-failure-64bit.png) + (build-failure-32bit.png)
= Acknowledgements and Links =
* Chris Tyler - http://blog.chris.tylers.info/
* Boris Chao Blog - http://blog.bchao.ca
* Jonathan Deni Blog - http://jonathandeni.blogspot.com/
* JSHydra - https://developer.mozilla.org/en/JSHydra
* Project Repo - http://scotland.proximity.on.ca/DXR/
= Logos =