Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <petr.vorel@gmail.com>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: "Yann E . MORIN" <yann.morin.1998@free.fr>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/nfs-utils: bump version to 2.6.4
Date: Tue, 5 Dec 2023 22:19:20 +0100	[thread overview]
Message-ID: <20231205211920.GA133652@pevik> (raw)
In-Reply-To: <27710fa6-7ff9-4775-8a20-4cb9ad7b5dc4@benettiengineering.com>

Hi Giulio,

> Hi Petr,

> On 05/12/23 21:39, Petr Vorel wrote:
> > Remove patches backported from this release.
> > Backport patch from upstream ML needed for uClibc-ng.

> > Require kernel 3.17 due getrandom() dependency.

> > Signed-off-by: Petr Vorel <petr.vorel@gmail.com>
> > ---
> > Hi Giulio, Yann,

> > I'm sorry, while I was able to reproduce the problem on nfs-utils master
> > Giulio reported [2], I'm not able to reproduce it on this patch due
> > failure on libressl (nfs-utils dependency):

> > buildroot/c5fde6099a8b228a8bdc3154d1e47dfa192e94ed/output/build/libressl-3.8.2/crypto/bn/bn_add.c:65:21: fatal error: bn_arch.h: No such file or directory
> >   #include "bn_arch.h"

> I can't honestly find out this build failure, can you point the autobuilder
> link?

This is when I try to reproduce the problem with this patch (nfs-utils updated
to 2.6.4).

> If sometimes you can't

I guess you wanted to write something.

> I've tried to apply and buildroot/utils/test-pkg -p nfs-utils
Thanks for testing! Hm, strange, I tested this. I'm going to retest it.

> but it fails due to missing uuid.h that has become mandatory during
> the building of host-nfs-utils. This is fixed by adding host-utils-linux
> to host-util-linux to HOST_NFS_UTILS_DEPENDENCIES.

I suppose you mean to add host-util-linux to HOST_NFS_UTILS_DEPENDENCIES.
I'll send v2 shortly.

> You can check host dependency issues while building using
> buildroot/utils/docker-run
> That way you have the minimum possible host libraries. Probably you have
> uuid lib installed in your system and you don't see the bug.

Yes, I have (I do nfs-utils compilations on my workstations), that will be the
problem.
I'll try this (I see utils/docker-run mentioned in docs).

Kind regards,
Petr

> Can you please add this fix to the patch?

> Thank you!

> Best regards
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2023-12-05 21:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-05 20:39 [Buildroot] [PATCH] package/nfs-utils: bump version to 2.6.4 Petr Vorel
2023-12-05 21:05 ` Giulio Benetti
2023-12-05 21:19   ` Petr Vorel [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20231205211920.GA133652@pevik \
    --to=petr.vorel@gmail.com \
    --cc=buildroot@buildroot.org \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=yann.morin.1998@free.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox