On Tue, 2008-11-04 at 15:10 +0000, Ken Moffat wrote:
> On Tue, Nov 04, 2008 at 09:06:38PM +1300, Simon Geard wrote:
> > On Mon, 2008-11-03 at 16:54 +0000, Ken Moffat wrote:
> > > 1. libxul-embedding.pc needs -L${sdkdir}/sdk/lib to be able to find
> > > libxpcomglue which is a *static* lib (yeugh!) - used by yelp. I
> > > think there is similar breakage in other .pc files, but I don't
> > > have anything that uses them (and, $DEITY, what a mess! - stripped
> > > libs below xulrunner-1.9.0.3/ and unstripped below
> > > xulrunner-devel-1.9.0.3, a maze of stable and unstable files).
> > >
> > Interesting... I don't recall encountering anything like that. I've got
> > Yelp 2.24.0 built against Xulrunner without any patches or special
> > flags...
> >
> Curious, I needed that for 2.24.0.
Looking at libxul-embedding.pc, it already contains the following:
Libs: -L${sdkdir}/lib -lxpcomglue
And ${sdkdir}/lib is a symlink to ${sdklib}/sdk/lib, so that would
explain why my build is able to see the static library without any
problem. Is your .pc file different in this regard?
> > One qualification, actually - my NSS/NSPR version is built according to
> > the BLFS instructions (including the Fedora patch), but applied to a
> > newer version. Nothing hacky, at least...
> >
>
> Hmm, I'm starting to think it might be a good idea for me to use
> system nss/nspr (they seem to get updated a bit quicker).
Well, I'd assume Firefox stable releases always package the latest
versions of components like those. But I've never really paid much
attention to them... I'm using a newer version than BLFS purely because
there was a newer one when I went to get the sources.
> > The problem here, from memory, was that either Yelp or Epiphany found
> > Xulrunner, and assumed it provided NSS. I don't know whether they're at
> > fault or whether Xulrunner is, but the above change was enough to make
> > it work.
>
> Right. In my case xulrunner does provide it.
Probably. As I said, I tried building them as part of Xulrunner, but had
issues with other things not being able to find them - probably the kind
of thing you mentioned patching...
> > Actually, my own build does include --enable-optimize, but I trimmed it
> > to avoid anyone accidentally copying anything gcc-4.3 specific. As for
> > --enable-svg, I think it's the default these days - certainly, I have
> > SVG support on a Firefox built this way.
> >
> I think you are right,
Actually, I checked after I sent the email. The --help output lists
--disable-svg instead of --enable-svg in FF3, so yeah, looks like the
default.
> > As for the .pc file being missing, what version of SQLite are you using?
> > I have 3.6.2 installed, and it provides an sqlite3.pc file already.
> sqlite-amalgamation-3.6.3 - should I not be using the 'amalgamation'
> version ?
Interesting. Their download page says people should use the amalgamation
versions in most cases - they're smaller, and maybe quicker to build.
But comparing the content of the two tarballs, the amalgamation is
missing things like .pc files, making it somewhat useless for our
purposes...
Simon.
signature.asc
Description: This is a digitally signed message part
-- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
