Re: devel/libuuid/buildin.mk is not used

[maya%NetBSD.org@localhost]

On Fri, Jul 31, 2020 at 12:47:32PM +0200, Aleksej Lebedev wrote:
> Hi!
> 
> Last time I tried to build anything from pkgsrc on DragonFly BSD was more than a year ago.
> I remember that python didn't build so not much else could be built because of that.
> 
> Today I looked quickly at what was the reason. Turned out it was simply because devel/libuuid doesn't build on DragonFly.
> However DragonFl has its own libuuid, moreover devel/libuuid has builtin.mk in it, but for some reason no packages include it.
> 
> lang/python37 for exmaple directly includes devel/libuuid/buildlink3.mk.
> 
> Does anyone know whether it's intentional or not?
> 
> Ideally devel/libuuid should be fixed for DragonFly, but that shouldn't stop anyone from using pkgsrc as the native libuuid seems to work: replacing buildlink3.mk with builtin.mk in lang/python37/Makefile gave me a working python3.


I think libuuid is a bad fit for a builtin.mk.

util-linux libuuid offers similar functionality but doesn't follow the
same structs/function definitions used by other implementations.

Note that they all say "compatible with DCE 1.1 RPC specification" but
util-linux doesn't say this and uses different function signatures.

Sometimes packages support both, but there's no guarantee that they are
interchangeable.

I suspect the same is also true for dragonflybsd uuid_* functions.