Re: rpm-4.0.2 build error

[fred anger <anger rightarm org>]

On Tue, 17 Jul 2001, Tim Mooney wrote:
> 4.0.2 won't work with 3.2.x or later, you need to stick with 3.1.x or
> earlier.

Ok.

> You're right, rpm's configure is specifically looking for the db3/db.h
> because that's how it's layed out on a Red Hat system.  It makes sense,
> it's just not optimum for non-RH systems.

Doesn't make sense to me.  Unless you only want to be able to build rpm on
redhat systems.  Why not look for db.h where the db-3 distribution
installs it?  And if that's not an option, why not include the special
layout instructions in the rpm distribution's INSTALL file?  I mean, if
you're going to implicitly require that things be done the Redhat way, why
not go all the way and include the instructions on how to set the db-3
installation up for the rpm source distribution?

> You have at least three options:
>
> 1) Hack your system, so that there is a db3/db.h, possibly by doing something
> like
>
> 	cd /usr/include
> 	mkdir db3
> 	cd db3
> 	ln -s ../db.h .
>
> (or whatever, depends on how things are layed out on your distribution)

There must be more to it, cuz that doesn't work.  Sorry, I didn't save the
errors.  My bad.

> 2) hack RPM's configure so that it searches other places.  The patch after
> my sig might help.  You will need to rebuild configure from configure.in.

I applied the patch and ran "autoconf" in the toplevel rpm source
directory.  That complains about "AC_ARG_PROGRAM invoked multiple times".
Then running configure yields:

...[snipped]
config.status: creating python/Makefile
config.status: creating perl/Makefile
config.status: error: cannot find input file: perl/Makefile.in

I assume I'm not doing the right thing with autoconf, as I'm not all that
familiar with it...

> 3) get a pre-release of RPM 4.0.3, where db 3.2.x is included right with
> RPM.

That'd be easier if they released the development snapshots as a tarball
;-)

whine, whine, whine...

-fa