Re: problems building sa-exim on ia64

Marc MERLIN <[email protected]>
Newsgroups gmane.mail.exim.spamassassin
Message-ID <[email protected]>
On Thu, Jan 20, 2005 at 02:51:27AM +0100, Patrick von der Hagen wrote:
> Hi all,
> 
> I just spent some time trying to build exim-src-rpms (taken from 
> ftp.exim.org) on one of my ia64-systems. Sadly, sa-exim caused problems.
> 
> Building sa-exim-4.1+cvs.so
> gcc -I../../src -I./eximinc -DDLOPEN_LOCAL_SCAN 
> -DSPAMASSASSIN_CONF=\"/etc/exim/sa-exim.conf\" 
> -DSPAMC_LOCATION=\"/usr/bin/spamc\" -O2 -Wall -shared -o 
> sa-exim-4.1+cvs.so sa-exim.c
> sa-exim.c:512:2: warning: #warning you should not worry about the "might 
> be clobbered by longjmp", see source
> /usr/bin/ld: /tmp/cc37rnoO.o: @gprel relocation against dynamic symbol 
> version
> collect2: ld returned 1 exit status

Honestly, I have no idea why it says that, you'll need help from someone who
knows more about gcc than I do.

> The rpm-changelog mentions "Updated to sa-exim+cvs (2004-08-23 
> version)", so the changes vor sa-exim 4.1 (2004/08/16) that mention 
> "made hopefully 64 bit clean" and a mistake preventing sa-exim from 
> building should not apply in this case.
 
that patch wasn't to fix a build problem but a pointer problem in the code.
It shouldn't have affected this.
 
> Since my ia64-hardware will never run sa-exim (just internal 
> mail-routing, no connection to the "bad world outside"), this is 
> acutally no problem for me, so I won't investigate it further. However, 
> if you need more information of if I could try some patch I'll certainly 
> try to help.

Can anyone offer a suggestion?

Marc
-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems & security ....
                                      .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/   |   Finger [email protected] for PGP key
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.