Re: Porting PostgreSQL to DragonFly BSD

From: Rumko <rumcic(at)gmail(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Porting PostgreSQL to DragonFly BSD
Date: 2011-03-02 08:10:50
Message-ID: 201103020910.53434.rumcic@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

Attachment Content-Type Size
0001-DragonFly-BSD-support-linked-nbsd.patch text/plain 1012 bytes

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2011-03-02 10:40:21 Re: Sync Rep v17
Previous Message Tom Lane 2011-03-02 04:54:11 Re: Snapshot synchronization, again...