pkgsrc-Users archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: postfix 3.0.2, NetBSD 5.2.2 amd64 make error - shared libraries
On Wed, Oct 21, 2015 at 09:47:58AM +1100, Carl Brewer wrote:
> On 21/10/2015 9:30 AM, Carl Brewer wrote:
> >
> >G'day,
> >I figured it might be nice to update postfix on my 5.2 amd64 NetBSD
> >server, but I see this at make-time :
> >
> >ATTENTION:
> >ATTENTION: Shared libraries are requested, but not supported on this
> >platform
> >ATTENTION:
> >
> >
> >bash-4.3# uname -a
> >NetBSD 5.2.2 NetBSD 5.2.2 (GENERIC) #0: Sat Jan 18 17:26:19 UTC 2014
> >builds%b41.netbsd.org@localhost:/home/builds/ab/netbsd-5-2-2-RELEASE/amd64/201401181652Z-obj/home/builds/ab/netbsd-5-2-2-RELEASE/src/sys/arch/amd64/compile/GENERIC
> >amd64
>
>
> and building from pkgsrc, a CVS up from about 1 hour ago
>
> Carl
I've been working on a similar problem.
If it helps: I just managed to build a Postfix 2.11.6nb1 package
under NetBSD 5 by checking out a slightly older version of the
pkgsrc "postfix" files into a custom directory within a freshly
up-to-date pkgsrc hierarchy--and recompiling there instead of in
the stock postfix directory.
I don't necessarily recommend this method. I realize I should be
upgrading to NetBSD 6 or 7 and maybe even Postfix 3 for more
reliability, support and security[*]. Moreover, I haven't tested
the package at runtime yet; just got it built and am posting this
partly to archive how I did so before I forget. Plus, I don't know
how much longer this technique will even result in anything that
configures, compiles or packages... nevermind runtime... given the
sometimes-changing nature of the pkgsrc infrastructure.
That said, here's roughly what I did (I recommend caution if you
follow these steps--they delete files without confirmation):
% cd pkgsrc/mail
% cp -ipr postfix postfix2
% cd postfix2
% find . \( -name CVS -prune \) -o \( -type f -print0 \) | xargs -0 rm
% cvs update -dAP -D '2015-08-01' .
% make clean
% make package
-DLB
[*] For me this was an emergency measure for a server that's in
co-location--a server to which it's difficult to get console
access--and on which Postfix urgently needed a newer openssl.
Home |
Main Index |
Thread Index |
Old Index