Changes

Jump to: navigation, search

Winter 2010 Posters/GCC4.5 Packaging/ViewSource Packaging

1,282 bytes added, 01:49, 17 April 2010
Results + What we’ve accomplished
* GCC
Normal 0 false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4
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 SPEC file. A Spec SPEC file is file that has a list of instructions that will be used by a building tool to build our packages. The problem problems we faced with our build is are a bunch or errors linking back to libraries that it cannot findand 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.
After speaking with the Fedora communitySince our attempt to create a SPEC file was a disaster, they suggested that we try 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 do a command line the SPEC file we started the build process, unlike our scratch SPEC file, the build from times were significantly less. The errors would happen in the earlier stage of the GCC 4build.5 tarballThese errors consist of missing dependencies, missing files, missing paths to directories. With their adviceThe missing dependencies are a easy fix, I just needed to install them, but the missing files, and other errors we extracted had trouble solving. Again with communication in the GCC 4Fedora community, we were unable to solve it.5 file and started building from A suggestion was to do a command linebuild.
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)
1
edit

Navigation menu