On Sat, 19 Mar 2011 21:57:01 -0400 Chris Tyler <chris@xxxxxxxxxxx> wrote: > The debug information should be automatically separated into a > -debuginfo package near the end of the build, leaving you with > stripped binaries. > > There are several causes of variations between the distribution builds > and what you get from a local rpmbuild, but one of the main causes is > that rpmbuild uses the tools and libraries that are installed on your > system, while the distribution build is created using koji and mock > in a "cleanroom" environment where only core build tools plus the > BuildRequires specified in the .spec are present. This can make a > difference if (for example) a configure script detects the presence of > particular libraries on your system that aren't present in the mock > cleanroom (chroot) environment. > > Note that you can build locally using mock, or you can submit a > package to the Koji system for a remote build using your Fedora > credentials (assuming you have a Fedora account, > https://admin.fedoraproject.org/accounts/). To set up to use Koji, > install the "fedora-packager" package, then run > "fedora-packager-setup" to set up your certificates; to submit a Koji > scratch build, run this command: > > koji build dist-f14 --scratch nameOfTheSRPM > > This will submit the package to the remote primary arch koji builders. > You can see summary results on your screen, or you can follow the full > logs using the web interface (http://arm.koji.fedoraproject.org). At > the end of the build, you'll get full buildlogs plus the output RPMs. Thank you for this detailed response with all the good information it contains. -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
