Monday, November 16, 2009

Modified G++/C++ Error With Coin2 Package

Trying to stay off the bandwagon in terms of using the modified g++ / c++ to build Abiword like the rest of my class, I set a challenge to work on another package with an ample amout of C++ codes.

I used a script my Professor Chris Tyler had, that would would through a list of Fedora packages and basically exmaines each one and counts how many c / c++ codes there are.

Here is the script I used: FILE
Here is the script to get the modifed g++/c++: FILE (takes about 1 hour to compile)
So the package I decided to work on was Coin2

I was successfully able to build Coin2 without the modified g++ and c++

Command Issue: time rpmbuild -ba Coin2.spec

Checking for unpackaged file(s): /usr/lib/rpm/check-files /home/bchao/rpmbuild/BUILDROOT/Coin2-2.5.0-5.fc11.x86_64
Wrote: /home/bchao/rpmbuild/SRPMS/Coin2-2.5.0-5.fc11.src.rpm
Wrote: /home/bchao/rpmbuild/RPMS/x86_64/Coin2-2.5.0-5.fc11.x86_64.rpm
Wrote: /home/bchao/rpmbuild/RPMS/x86_64/Coin2-devel-2.5.0-5.fc11.x86_64.rpm
Wrote: /home/bchao/rpmbuild/RPMS/x86_64/Coin2-debuginfo-2.5.0-5.fc11.x86_64.rpm
Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.yINAzy
+ umask 022
+ cd /home/bchao/rpmbuild/BUILD
+ cd Coin-2.5.0
+ rm -rf /home/bchao/rpmbuild/BUILDROOT/Coin2-2.5.0-5.fc11.x86_64
+ exit 0

real 3m42.609s
user 2m49.487s
sys 2m53.814s


When trying to build with the modifed g++ and c++ I ran into the following problem.

Command Issued: time rpmbuild -ba Coin2.spec

Output:
extracting debug info from /home/bchao/rpmbuild/BUILDROOT/Coin2-2.5.0-5.fc11.x86_64/usr/lib64/libCoin.so.40.5.0
*** ERROR: No build ID note found in /home/bchao/rpmbuild/BUILDROOT/Coin2-2.5.0-5.fc11.x86_64/usr/lib64/libCoin.so.40.5.0
error: Bad exit status from /var/tmp/rpm-tmp.JARMMn (%install)

RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.JARMMn (%install)

real 2m44.161s
user 2m17.568s
sys 2m24.901s


I'm not sure why I got this issue, but my Professor Chris Tyler will look into this for sure as he said that this will hinder alot of what we are doing. Other than this setback of trying to stay away from the bandwagon, I will blog about my success results with abiword instead.

0 comments:

Post a Comment