From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030728
Description of problem:
Mozilla 1.0.1 installed the includes and libraries in /usr/include/mozilla and
Mozilla 1.0.2 (a security update) installs the includes and libraries in
/usr/include/mozilla-1.0.2 and /usr/lib/mozilla-1.0.2.
Nautilus gets very confused and refuses to build because it is looking for the
libraries in the old location. (As set in configure.in.)
This is a problem becuase you cannot rebuild the nautilus package using the
latest security fix for mozilla.
nautilus needs to use mozilla-config to determine correct library locations.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install source rpm for nautilus
2. rpm -ba nautilus.spec
3. Watch it go boom.
*** Mozilla 0.9.5 or greater is required to build the
*** Nautilus Mozilla component.
error: Bad exit status from /var/tmp/rpm-tmp.68042 (%build)
Line 145 of configure.in has the start of the offending section.
kdebindings probably has similar problems. (As well as anything assuming it
knows where the libraries for mozilla are located.)
Here is what it takes to fix the problem.
In the nautilus.spec file:
Add: "%define mozilla_version 1.0.2"
to the line:
CFLAGS="$RPM_OPT_FLAGS -g" %configure --disable-more-warnings
in the %build section.
The only problem with this fix is that it now binds nautilus to the version of
Mozilla. (Unavoidable considering the change to Mozilla's install.)
Did you file a separate bug about kdebindings?
No. I will do that. (My solution for that one is less than clean. It is caused
by the change in locations in both bugs.)
Chris, you seem to have done a nautilus errata for moz 1.0.1. Is 1.0.2 supposed
to need a new errata?
7.3 not supported anymore. This works in recent versions.