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-01 22:05:17
Message-ID: 201103012305.19893.rumcic@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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?
--
Regards,
Rumko

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hiroshi Saito 2011-03-01 22:15:11 Re: OSSP gone missing? Fate of UUID?
Previous Message Tom Lane 2011-03-01 22:03:35 Re: toast tables on system catalogs