Hi John,
Thanks for that - the rpms did indeed install fine with --nodeps & Exim is now 
upgraded to 4.72 & seems to be working fine on EL4!
  
The 4.69 spec file & the 4.72 spec files are exactly the same file. I just did 
a diff on them & it showed no differences.

 The line in the spec file that require the dependencies that failed is:

Requires: /etc/pki/tls/certs /etc/pki/tls/private

Don't understand it as the directories above exist on the box & seem to have 
the correct permissions.

At the moment I'm very happy to have Exim 4.72 working & a way of building it 
for other Centos 4.8 boxes if needed.
But yes it would be great if we could get a spec file that will work with both 
EL4 & 5 - a bit out of my skill range but don't mind helping!

I have cc'd the dev list as you did also.

I have just tried building it on my fresh Centos 4.8 system & the first thing 
it told me was I needed the following packages - not all of these are available 
from the EL4 repos AFAIK.

pcre-devel sqlite-devel  mysql-devel postgresql-devel libXaw-devel  
libXmu-devel   libXext-devel libX11-devel libSM-devel  libICE-devel  
libXpm-devel  libXt-devel  libspf2-devel  libsrs_alt-devel libdomainkeys-devel

I must have installed them on the other mail server (on which I just built Exim 
4.72)  when I installed 4.69 I guess - or late one night & forgot!

Anyway many thanks for your help on this - & I'd be interested as to what you 
come up with regarding a universal Exim spec file for EL4 & 5.

Cheers,

Mike.

-----Original Message-----
From: John Robinson [mailto:[email protected]] 
Sent: 12 January 2011 19:05
To: Mike Ridgers
Cc: 'User discussion about ATrpms.net'; ATrpms development list
Subject: Re: [ATrpms-users] Help rebuilding Exim 4.72 src rpm from EL5 for EL4

On 12/01/2011 18:46, Mike Ridgers wrote:
> Hi John,
> Just got it to build!
>
> I found this thread: 
> http://www.directadmin.com/forum/showthread.php?t=38586&page=2
> People trying to do the same thing.
>
> Quote:
>
>> During the rpm rebuild of src.rpm on CentOS 4.8, I got the following error 
>> due to pcre.h not found:
>>
>> It is strange, since pcre* package are installed, and pcre.h exists.
>> Any idea? Maybe exim.h need to use #include "pcre.h" instead of 
>> #include<pcre.h>?
>>
>> I found a bypass by setting a symbolic link:
>> ln -s /usr/include/pcre/pcre.h /usr/include/pcre.h "
>
> End Quote.
>
> I ran the " ln -s /usr/include/pcre/pcre.h /usr/include/pcre.h" command as 
> above&  that fixed it !

The proper answer is probably to use ./configure --with-pcre=/usr/include/pcre 
or something like that when building for EL4, i.e. make the spec vary the 
configure invocation depending on the target distro.

> I have just installed 
> http://dl.atrpms.net/all/atrpms-rpm-config-187-1.noarch.rpm as you sugested&  
> have rebuilt it again.
>
> However when I now go to update Exim:  rpm -Uvh 
> exim-4.72-41.RHL4.i386.rpm exim-greylist-4.72-41.RHL4.i386.rpm
>
> I get :
>
> error: Failed dependencies:
>          /etc/pki/tls/certs is needed by exim-4.72-41.RHL4.i386
>          /etc/pki/tls/private is needed by exim-4.72-41.RHL4.i386
>
> This has to be simple but both the listed directories are already there - I 
> can cd to them !?

Something in EL5 specifically provides them, but the equivalent package 
provides different directories in EL4. Again, looking at the Requires: 
stuff in the spec file should give guidance - it may also be worth checking the 
older spec file for 4.69 to see how it handles this.

For both of these, ideally we want to fix the 4.72 spec file to build correctly 
on both EL4 and EL5, and presumably other distros too, which
4.69 did. But you now have a rpm you can install with --nodeps or whatever, 
which I expect will work perfectly, so I guess you deserve a glass of something 
celebratory!

We probably ought to take any further discussion of this over to atrpms-devel, 
which I've cc'ed.

Cheers,

John.


_______________________________________________
atrpms-users mailing list
[email protected]
http://lists.atrpms.net/mailman/listinfo/atrpms-users

Reply via email to