Sam Replied:
-----Original Message-----
From: cour...@lists.sourceforge.net
[mailto:cour...@lists.sourceforge.net] On Behalf Of Sam
Varshavchik
Sent: Wednesday, December 28, 2005 4:10 AM
To: 'courier Users List'
Subject: Re: [courier-users] Bilding Courier(-authlib) RPMs on Mandriva
2006.0
Egbert Jan writes:
Secondly rpmbuild 4.x stops on unpackaged files. For some reason
(Sam?) several libtldt... Files are created in {_libdir}. Should or
shouldn't these be packaged???
No, they shouldn't. You should already have them installed on the system
in
the first place. libtool adds these files if they are not installed, but
Courier's installation scripts expect those files to already be present on
your system.
You need to find an existing package called either libtool-libs,
libtool-ltdl-devel, or something of this sort, and install it before
building Courier.
Why compiling 'own' versions of these libltdt libraries when they seem
exist on the system already?
No, they don't exist. If they did exist, they wouldn't get built.
Yes they do exist but under a slightly different name, is that possible?
When installing the courier-authlib (with the packaged libtool stuff) rpm
with 'rpm -i', rpm bails out with a message about a conflict with a Mandriva
libltdt library/package. I'll investigate further. Shouldn't this be more
elegantly be solved by configure/make during the build/install phase
already? Alas, I learned a lot about rpm/rpmbuild and spec files for
pacackages with subpackages.
Building without the libltdst stuff does work now; I.ve added
'%unpackaged_files_terminate_build 0; to my .rpmmacros. The rpms are built
and authtest <user> works out of the box (no config files touched yet).
Its time now for the big work... Courier 0.52.2 itself. Fingers crossed!
13 messages in net.sourceforge.lists.courier-usersRE: [courier-users] Bilding Courier(-...
