-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 03 Apr 2003 12:02:30 -0800, Gordon Messmer wrote: [GCC -g] > > I've thought it is only enabled for beta versions and disabled > > for final releases? Am I wrong? > > I think it's being used for the "debuginfo" packages. I might need > correction, but I believe that all binaries are built with debugging > symbols, and then RPM runs a script to extract the debugging symbols, > and packages them separately. This way, your binaries are stripped in > the application package, and you also have the debugging symbols > available in another package that you can install if you need to. Yes, I assumed someone would point me back to that debuginfo stuff. It is mentioned in the release notes and how to turn this off has been mentioned on this list before. My ~/.rpmmacros file has the necessary line added as a comment already. The solution is here somewhere. What I'm seeing is a non-root rpmbuild environment that messes up the debuginfo macros and everything else that is different compared with older versions of the RPM package. I don't get any debuginfo packages at all. :) I just get ordinary packages which contain binaries and object files with debug info within and which are not stripped fully. Test-building as root works correctly and creates separate debuginfo packages. I'm going to look into bringing my ~/.rpm* up-to-date, because somehow they are the cause of it. Most likely they don't include enough files. - -- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+jJ2E0iMVcrivHFQRAn4VAJ4wQ7R+R8dF7lesxUXc5rtwUf8FggCgh5wU dGxd6B9HivcB44YYK7U9YzA= =7oYR -----END PGP SIGNATURE-----
