GCC 4.5 - RPM Packaging Stage 1 - Update

From my previous post, I encountered a build error while building doing a rpmbuild on gcc 4.5.

So today, I went to ask my professor Chris Tyler for his opinion. Here is his answer

19:50 @ctyler BoChao-Work: yes, not uncommon. Search the Fedora wiki for it.

The problem is that it's trying to strip out the debug info

into a separate package, but there's no build ID in the binary,

so it won't be able to check that it's matched the right binary

and debuginfo.

Also I went onto the Fedora Development channel (#fedora-devel) on IRC (irc.freenode.net) and also asked for their advice.

Just as my Chris said, there is a patch that I needed to help bypass that error.

Here is a snippet of my conversation in the Fedora Development Channel

19:59 BoChao-Work - Hi All, wonder if anyone can help me with the follow

error: http://pastebin.com/vv9jh2Yp

20:07 -!- daMaestro [~jon@fedora/damaestro] has joined #fedora-devel

20:08 nirik - BoChao-Work: a gcc devel channel might be better? I don't think

fedora has any 4.5 package yet.

20:08 tibbs|h - Generally happens when you use gcc to do the final link

instead of ld.

20:09 tibbs|h - Fedora gcc carries a patch for this. I needed to apply it in

my gpc packages.

20:09 tibbs|h - gcc44-build-id.patch

I went on Google and did a search for the gcc patch and found this site that hosted the patch.

Since I never had to deal with a patch before in a spec, I again did a quick search on Google using the following phrase "patch in spec files" the first result was from redhat which showed how to integrate a patch file into the spec file.

So here is my new modified temp spec file.

Also a little note, I had to put the patch file in rpmbuild/SOURCES/ directory, didn't know that. Took me a while to figure it out.

Now time to build and see what happens... Cheers