Tuesday, March 30, 2010

gcc progress

Heh, funny title because that's exactly what we aren't having...progress lol.

Well recently me and Boris had a good scare when we tried building gcc on the cdot machine known as india and it was completely skipping all the steps and finishing the "build" in literally seconds. We thought that we completely messed something up in our spec files but I think it had to do with all the cdot machines being powered down last weekend.

Today, or rather yesterday, we tried building again and it worked....well the process was working, we still ran into the same errors as before. This is the error.

We decided to see if anyone in the fedora-devel channel knew anything about the error, only one person responded and he didn't have any idea. He, however, suggested that we try running rpmbuild on the spec file we got out of the gcc tarball just to see if its our system that is giving us the grief and not the spec file. Turns out it was a bit of both because although it did get further in the build process, it failed in the install process.

We tried asking about our problem in the gcc channel but either they were all busy or they just didn't like our question, whatever the case may be we are still progress-less lol.

We have a few options now, we could get in touch with a gcc developer and see what their package list is, to see what the difference is between our system and their system, and we can also ask about the spec file, basically get as much info out of them as possible.

Boris also suggested that we build the spec file from scratch, I can tell you all thats going to be a tough road but I guess since I am already along for the ride I might as well tackle it with him.

Well, thats all for now, until next time!

Tuesday, March 2, 2010

GCC progress

Continuing from my last blog post I fixed the error I was having by naming the directory gcc4.5 instead of gcc-4.5. After that I ran rpmbuild -ba gcc.spec and it was giving me hunk errors due to the patches so I decided to take all the patches out.

After the patches were completely gone the build ran longer and did its whole "matrix" compiling thing. I ran into errors that said gcc needs certain packages to build, gmp, mpfr, and mpc.

Building gcc requires
GMP 4.2+ - version on comp -> 4.3.1-5 (buggy but acceptable)
MPFR 2.3.1+ - version on comp -> 2.4.1-5 (buggy but acceptable)
MPC 0.8.0+ - needed updating -> 0:0.16-2

As you can see mpc needed updating so I decided to yum install mpc which seemed to download an updated version of mpc but the compile was still failing there. I had to manually download mpc from the ftp site, after that I had to extract the file and run ./configure, make, and make install on it. Make install would not run without admin privileges so I had to be root for that.

After that was installed I ran rpmbuild again and it compiled for about what seemed like half an hour until getting to an error "make: *** [profiledbootstrap] Error 2". I looked online and a lot of people seemed to get this error while building gcc and they said that disabling ccache would fix it.

Everywhere I looked online it seemed that the way to do that was to add "%configure --disable-ccache" inside the %build section but that still did not work. As of right now I am stumped, as soon as my friend Boris, who is working on this project with me, wakes up he will have a look.

Until next time, ciao.