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: libpar2
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=190991
laurent.rineau__fc_extra(a)normalesup.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rc040203(a)freenet.de
------- Additional Comments From laurent.rineau__fc_extra(a)normalesup.org 2006-05-09 10:23
EST -------
Actually, here is a list of packages that include a generated config header,
on my FC-5¹:
gd-devel
glibmm24-devel
gtkmm24-devel
gtkmm2-devel
libjpeg-devel
libsigc++20-devel
libsigc++-devel
libtiff-devel
openldap-devel
postgresql-devel
Some come from FC-5 and other from FE-5.
¹) generated with:
rpm -qf $(grep -l Generated /usr/lib*/*/include/*.h /usr/include/*.h| grep -v
qt-3) | sort -u
However, I agree that autoheaders should not be installed in the system.
Perhaps should we fill a bug report for these different packages.
I am very willing to have libpar2 and gpar2 in FE. Can you explain what could
be a solution of a library that need autobuild tools to define some object
types and operations? libpar2 needs to know the endianess to define types
leu16, leu32, and leu64 (see letype.h). These three types are equal to
uint16_t, uint32_t and uint64_t, on little endian platforms, but are classes
with cast operations on big endian platforms. What mechanism could use libpar2
to avoid installing autoheader, so that letype.h is correct?
--
Configure bugmail:
https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.