Opened 15 years ago

Closed 14 years ago

Last modified 13 years ago

#2957 closed task (fixed)

Firefox/Xulrunner *.pc files broken

Reported by: Marcel van den Boer Owned by: DJ Lucas
Priority: normal Milestone:
Component: BOOK Version: SVN
Severity: normal Keywords: xulrunner
Cc:

Description

There are some problems with the pkgconfig files in Xulrunner. These problems became apparent while trying to build libproxy and Yelp.

First, programs who are trying to include 'jsapi.h' are looking in the 'stable' folder, while the file is actually located in 'unstable'. Second, the 'sdkdir' is not referenced properly in any of the pkgconfig files.

To fix both issues apply this before compiling/installing:

sed -i 's@stable@unstable@' xulrunner/installer/mozilla-js.pc.in

sed -i 's@${sdkdir}@${sdkdir}/sdk@g' xulrunner/installer/*.pc.in

Change History (5)

comment:1 by DJ Lucas, 15 years ago

Owner: changed from blfs-book@… to DJ Lucas
Status: newassigned
Summary: Xulrunner *.pc files brokenFirefox/Xulrunner *.pc files broken

Yes, thanks for the thorough report. I was just looking into the libproxy issue when this came in. Fix needs to be the same for standalone firefox as well.

comment:2 by DJ Lucas, 15 years ago

After delving into thunderbird-3 and looking at this a bit more, I'm not sure the second command is correct. Following mozilla convention (taken from observing the TB build mechanics), the sdkdir is intended to be the top level installation directory. ${sdkdir}/sdk is what is used when building internal projects so that ${sdkdir}/xpcom-config.h can be found correctly, and symlinks in place to help misguided programs find at least libs and include dirs. I believe that yelp and libproxy are making incorrect assumptions here, however, I have yet to complete a build of TB3. The mozjs change is still needed.

comment:3 by DJ Lucas, 14 years ago

Fixed in r8276.

comment:4 by DJ Lucas, 14 years ago

Resolution: fixed
Status: assignedclosed

comment:5 by (none), 13 years ago

Milestone: 6.5

Milestone 6.5 deleted

Note: See TracTickets for help on using tickets.