RHEL5 has autoconf 2.59 and automake 1.9.6.
I've managed to build the whole Xapian family by reducing the
requirement to 2.59/1.9.6 in configure.ac.
Omega requires docdir which can be added by hand in docs/Makefile.am:
docdir = ${datadir}/doc/${PACKAGE}
if !MAINTAINER_NO_DOCS
dist_doc_DATA = $(RSTHTML)
endif
All I've done is get these packages compiled - I haven't tested in any
serious way.
All the best,
Tim.
On Mon, Aug 23, 2010 at 11:13:16AM +0100, Tim Brody wrote:> RHEL5 has autoconf 2.59 and automake 1.9.6. > > I've managed to build the whole Xapian family by reducing the > requirement to 2.59/1.9.6 in configure.ac. > > Omega requires docdir which can be added by hand in docs/Makefile.am: > docdir = ${datadir}/doc/${PACKAGE} > > if !MAINTAINER_NO_DOCS > dist_doc_DATA = $(RSTHTML) > endifXapian 1.2.x should no longer require autoreconf to be run in the spec file. Is it actually still needed for some reason? (And 1.0.x requires autoconf >= 2.59 and automake >= 1.9). Cheers, Olly
On Mon, 2010-08-23 at 11:13 +0100, Tim Brody wrote:> RHEL5 has autoconf 2.59 and automake 1.9.6. ><snip> rpmbuild calls "autoreconf --force". I *guess* this is intentional, as I haven't found a way to disable it. The solution may be to add a patch for building RPMs but life is easier if the core tarballs can be built without further changes. Cheers, Tim.
On Mon, 2010-08-23 at 13:21 +0100, Olly Betts wrote:> On Mon, Aug 23, 2010 at 12:08:15PM +0100, Tim Brody wrote: > > On Mon, 2010-08-23 at 11:13 +0100, Tim Brody wrote: > > > RHEL5 has autoconf 2.59 and automake 1.9.6. > > > > rpmbuild calls "autoreconf --force". I *guess* this is intentional, as I > > haven't found a way to disable it. > > Looking at /usr/lib/rpm/macros on an Ubuntu box, it looks like you just > need to create a file "NO-AUTO-GEN" in the same directory as configure.I just assumed it was rpmbuild calling autoreconf whereas it's a hack in the .spec files: (xapian-bindings/xapian-omega) %build # FC6 (at least) has a patched libtool which knows not to set rpath for # /usr/lib64, which upstream libtool fails to do currently. We can drop # this "autoreconf --force" and the "BuildRequires:" for the autotools # once upstream libtool is fixed. Note: this overwrites INSTALL, but # that doesn't matter here as we don't package it. autoreconf --force I'm not sure what "NO-AUTO-GEN" does but it doesn't stop autoreconf running above ^^ Was there a reason to not bundle a .spec in the Perl wrapper? All the best, Tim.
On Mon, 2010-08-23 at 16:11 +0100, Olly Betts wrote:> On Mon, Aug 23, 2010 at 03:40:20PM +0100, Tim Brody wrote: > > I just assumed it was rpmbuild calling autoreconf whereas it's a hack in > > the .spec files: > > (xapian-bindings/xapian-omega) > > > > %build > > # FC6 (at least) has a patched libtool which knows not to set rpath for > > # /usr/lib64, which upstream libtool fails to do currently. We can drop > > # this "autoreconf --force" and the "BuildRequires:" for the autotools > > # once upstream libtool is fixed. Note: this overwrites INSTALL, but > > # that doesn't matter here as we don't package it. > > autoreconf --force> But xapian-omega.spec.in hadn't been updated - I've just committed a fix for > that.And xapian-bindings.> > Was there a reason to not bundle a .spec in the Perl wrapper? > > No, just nobody has written one for that yet.Attached but hard-coded to "1.2.2.0". /Tim. -------------- next part -------------- A non-text attachment was scrubbed... Name: Search-Xapian.spec Type: text/x-rpm-spec Size: 4518 bytes Desc: not available URL: <http://lists.xapian.org/pipermail/xapian-discuss/attachments/20100823/1c07dc28/attachment.bin>