Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionZenon Panoussis
2011-03-12 18:47:27 UTC
Building the 2.26.0-5.el6 SRPM breaks:
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -DXP_UNIX -I/usr/include/xulrunner-sdk-1.9.2 -DBINDIR=\"/usr/bin/\" -pthread -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -MT moz-plugin.lo -MD -MP -MF .deps/moz-plugin.Tpo -c moz-plugin.c -fPIC -DPIC -o .libs/moz-plugin.o
moz-plugin.c:42:19: error: npupp.h: No such file or directory
moz-plugin.c also includes npapi.h. Completely different versions of npapi.h are provided by qt3-devel and by xulrunner-devel. libsvgr2 picks npapi.h from xulrunner-devel if it can find it; otherwise it takes the one from qt3-devel.
npupp.h comes with qt3-devel but conflicts with npapi.h from xulrunner-devel.
Solution: BuildConflicts: xulrunner-devel
However, the mozilla plugin is deleted during install anyway, so the whole exercise of making it build is useless.
Better solution:
--- librsvg2.spec.orig 2010-05-27 17:01:06.000000000 +0200
+++ librsvg2.spec 2011-03-12 19:43:11.921562851 +0100
@@ -76,7 +76,7 @@
--enable-gtk-theme \
--enable-gnome-vfs \
--with-croco \
-
+ --disable-mozilla-plugin
make
See also bug #617309.
Comment 2RHEL Program Management
2011-03-12 19:17:36 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
The bot says "This request was evaluated ... for inclusion in the current release", but the bug is filed against 6.1, which is not the current release. That's a bug in the bot: it does not read or does not respect the "Version" field.
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.
The official life cycle policy can be reviewed here:
http://redhat.com/rhel/lifecycle
This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:
https://access.redhat.com/