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

[Roland Illig <roland.illig%gmx.de@localhost>]

On 31.07.2020 12:47, 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.

It's correct that builtin.mk is not included directly.  The usual way is
to include the buildlink3.mk file, and the pkgsrc infrastructure then
includes the corresponding builtin.mk file.

Curiously, the pkgsrc guide doesn't mention this anywhere, but pkglint
would spit out an error if you tried to do that.

Have a look at the pkgsrc guide, it describes how to force pkgsrc to
select either the native or the pkgsrc variant of a package.

https://www.netbsd.org/docs/pkgsrc/pkgsrc.html#native-or-pkgsrc-preference

If that doesn't work, the builtin.mk file is probably broken.  If your
system has a working libuuid, it should be possible to select it.