[Bug 187243] Review Request: lazarus : IDE and RAD tool for the free pascal compiler (fpc)

bugzilla at redhat.com bugzilla at redhat.com
Wed Nov 28 17:19:40 UTC 2007


Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review Request: lazarus : IDE and RAD tool for the free pascal compiler (fpc)


https://bugzilla.redhat.com/show_bug.cgi?id=187243





------- Additional Comments From joost at cnoc.nl  2007-11-28 12:19 EST -------
Ok, I've tried it again. now fpc 2.2.0 is out I had to wait for lazarus 0.9.24
to be released. That's the case now. I've updated Lazarus to version 0.9.24, and
looked at the comments above.

srpm: http://www.cnoc.nl/fpc/lazarus-0.9.24-1.fc9.src.rpm

Changelog:
- Removed files specific for debian
- Updated to Lazarus v 0.9.24
- Changed desktop-file categories
- Disabled the debug-package for x86_64 again, see bug 337051
- If the debuginfo-packages is disabled, strip the executables manually
- Require fpc version 2.2.0
- Added -q to setup-macro
- Added OPT='-gl' option in build-section, to make sure that the debuginfo is
generated by the compiler
- Removed explicit creation of {buildroot}{_mandir}/man1 and
{buildroot}{_datadir}/applications
- Lazarus executable is renamed to lazarus-ide (changed upstream)

This time I also know what's wrong with the debuginfo and the
unstripped-binaries. fpc 2.2.0 contains a bug (bugzilla 337051) which causes
problems with building the debuginfo on x86_64. As long as this isn't fixed I've
disabled the debug-package as a workaround. Side effect of removing the
debug-package is that the executables are not stripped. So I added that manually.

About the older .spec files, I could remove them. But they are part of of the
upstream package. And can be used to build non-fedora rpm's.

In next releases the older .spec files will be updated according to this spec
file, btw.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.




More information about the package-review mailing list