rpm 5.3.10 (tarball from mdv svn) fails to compile on opensuse

[Robert Xu]

I have been trying to build rpm5 for opensuse, and I just end up with this error:
http://pastie.org/1845402

Current spec file is here:
http://pastie.org/1845678

I made a libdb-5_1 package because the libdb-4_8 package was not working.
If you would like to see the spec file, just ask me.

[Jeff Johnson (n3npq)]

The tarball (and rpm-5.3.10) expect to
find /usr/include/db51/db.h

This MUST be present (though there is no
reason whatsoever taht you cannot patch
out the 2 occurences of db51 to use any
recent version of Berkeley DB).

Verify when configuring (its in config.log in
your build tree) that Berekely DB was found.

You can also check config.h after running ./configure
(and you MUST add quite a few parameters, do not
expect rpm to Just Build with default options).

There are many examples of Known Good build options
in devtool.conf in the tarball. SuSE is there too.

[Robert Xu (bravoall1552)]

Thanks for the library pointer - I had /usr/include/db5 instead of db51.

Also, where can I find a copy of devtool.conf? I do not see it anywhere in the tarball.

[devzero2000 (pinto-elia)]

Hi

devtool.conf insn't in the tarball. Do an git clone https://github.com/devzero2000/RPM5.git, isn't uptodate, but devtool should be, but we @rpm5 have the istitutional rpm5.org, and the ufficial cvs repository, in maintenance these days.

Hope this help

[Jeff Johnson (n3npq)]

I mailed a copy of devtool.conf privately last night.

The underlying issue is still that RPM is a very hard build,
and end-users are expecting
    ./configure --prefix=/usr
to Just Work. There's so much "Have it your own way!"
AutoFu in place that one has to spend some serious time
just choosing the right options.

But its likely time to add devtool.conf as a form of de facto
documentation to assist choosing options.

[devzero2000 (pinto-elia)]

I Agree.

In fact I think today devtool no longer has its original function,
and perhaps should be put in the tarball and the INSTALL should describe its use, using a part of the procedure
USED to produce the final tarball. I'll do it when end the rpm5.org maintenance.

[Robert Xu (bravoall1552)]

Got the copy of devtool.conf, thanks!

It would be nice if devtool.conf was part of the tarball indeed. :)

Hmm... looks like rpm-4.8 has a bunch of files that aren't part of rpm-5.3.10... time to start merging and screwing around with it. :P

[Jeff Johnson (n3npq)]

Before you get too much further ...

There is _NO_ "compatibility" between the database format
in use by rpm-4.8 and rpm-5.3. There *IS* a relatively
simple (we are talking about a database schema change,
so ymmv) "conversion" both forwards and backwards
implemented in scripts/dbconvert.sh (and tools/dbconvert.c).

So I'd suggest _NOT_ typing "make install" until you are prepared
for the "conversion" and understand how to go forwards <-> backwards.

Instead, investigate rpm-5.3 in-tree, there's a quite complete set
of tests that can/will download a "full" distro and install into
a chroot wothout having to fight "compatibility" and "conversion"
issues whatsoever.

All I'm saying is do this when you have built rpm-5.3:

    cd tests
    make clean check

Otherwise you are in for a bit of a learning curve if trying to interoperate
with rpm-4.8 on the same box