Skip site navigation (1)Skip section navigation (2)
Date:      07 Apr 2006 13:58:16 -0400
From:      Lowell Gilbert <freebsd-questions-local@be-well.ilk.org>
To:        Heinrich Rebehn <rebehn@ant.uni-bremen.de>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: exim does not compile on amd64
Message-ID:  <441ww9p8sn.fsf@be-well.ilk.org>
In-Reply-To: <44366296.60005@ant.uni-bremen.de>
References:  <44366296.60005@ant.uni-bremen.de>

next in thread | previous in thread | raw e-mail | index | archive | help
Heinrich Rebehn <rebehn@ant.uni-bremen.de> writes:

> Hi list,
> 
> i installed 6.1-BETA4-amd64 on an AMD64 and it works fine so far.
> However i cannot compile exim[-ldap2] from ports:
> 
> root@fbsd64 [~] # portupgrade exim-ldap2
> --->  Upgrading 'exim-ldap2-4.60' to 'exim-ldap2-4.61_1' (mail/exim-ldap2)
> --->  Building '/usr/ports/mail/exim-ldap2'
> ===>  Cleaning for perl-5.8.8
> ===>  Cleaning for openldap-client-2.2.30
> ===>  Cleaning for libiconv-1.9.2_2
> ===>  Cleaning for exim-ldap2-4.61_1
> ===>  Vulnerability check disabled, database not found
> ===>  Extracting for exim-ldap2-4.61_1
> => MD5 Checksum OK for exim/exim-4.61.tar.bz2.
> => SHA256 Checksum OK for exim/exim-4.61.tar.bz2.
> ===>   exim-ldap2-4.61_1 depends on file: /usr/local/bin/perl5.8.8 - found
> ===>  Patching for exim-ldap2-4.61_1
> ===>   exim-ldap2-4.61_1 depends on file: /usr/local/bin/perl5.8.8 - found
> ===>  Applying FreeBSD patches for exim-ldap2-4.61_1
> Ignoring previously applied (or reversed) patch.
> 1 out of 1 hunks ignored--saving rejects to OS/Makefile-FreeBSD.rej
> => Patch patch-OS::Makefile-FreeBSD failed to apply cleanly.
> *** Error code 1
> 
> Stop in /usr/ports/mail/exim-ldap2.
> ** Command failed [exit code 1]: /usr/bin/script -qa
> /tmp/portupgrade3499.0 make DEPENDS_TARGET=package
> ** Fix the problem and try again.
> ** Listing the failed packages (*:skipped / !:failed)
>          ! mail/exim-ldap2 (exim-ldap2-4.60)     (patch error)
> --->  Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed
> root@fbsd64 [~] #
> 
> 
> Is this a known problem?

No, it's strictly on your end.  You have a stale patch in the port
skeleton.  The easy approach is to delete the whole port and re-cvsup.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?441ww9p8sn.fsf>