Re: Porting PostgreSQL to DragonFly BSD
Rumko <rumcic@gmail.com>
From: Rumko <rumcic@gmail.com>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: Tom Lane <tgl@sss.pgh.pa.us>,
pgsql-hackers@postgresql.org
Date: 2011-03-02T08:10:50Z
Lists: pgsql-hackers
Attachments
- 0001-DragonFly-BSD-support-linked-nbsd.patch (text/plain) patch 0001
On Tuesday 1. of March 2011 23:05:17 Rumko wrote: > On Tuesday 1. of March 2011 22:44:16 Peter Eisentraut wrote: > > On tis, 2011-03-01 at 22:22 +0100, Rumko wrote: > > > Well, wouldn't consider it ugly, but the patch (attached and available > > > at http://www.rumko.net/0001-DragonFly-BSD-support-linked.patch ) is a > > > lot shorter. > > > > > > Uses freebsd's template and defines the linker in Makefile.shlib. > > > > The piece in Makefile.shlib you add is dead code because PORTNAME will > > never be "dragonfly" (it would be "freebsd"). > > Ah, good to know. > > > I see there is a > > difference between the existing freebsd code and what you propose to add > > in that freebsd doesn't use shared object minor versions. Is that also > > or not the case on DragonFly BSD? > > Due to pkgsrc being the default on NetBSD and DragonFly BSD, it should > create the libs in the same way ... maybe instead of using PORTNAME, we > could use host_os to differentiate? What about this patch ( http://www.rumko.net/0001-DragonFly-BSD-support-linked-nbsd.patch )? instead of linking to freebsd, it's linked to netbsd and It still compiles due to the two templates being similar enough. -- Regards, Rumko