All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <petr.vorel@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] libtirpc: remove NIS patch
Date: Tue, 29 Dec 2020 22:06:00 +0100	[thread overview]
Message-ID: <20201229210600.GC2801@pevik> (raw)
In-Reply-To: <20201229204658.GX1680670@scaer>

Hi Yann, all,

...
> > Testing with test-pkg shows the only failure for br-riscv32:
> > RPC support not available in C library, please disable
> > BR2_TOOLCHAIN_EXTERNAL_INET_RPC

> > But test fails with the same error even when this patch is kept.

> Indeed, the risc32 case is special: it uses a glibc more recent than
> 2.32. In glibc 2.32, RPC support was entirely removed, so it is not
> unexpected that we do have RPC-relacted issues for riscv32.

I wonder if there is some package which is not yet ported to libtirpc and
requires Sun-RPC. Suppose yes, otherwise there wouldn't be that check, but I
haven't find any.

FYI openSUSE has been using libtirpc as a drop-in replacement for quite long
time. Maybe that could be a solution for Buildroot as well.

openSUSE change libtirpc.pc.in [1] in rpm spec file before build [1]:
sed -i -e 's|${includedir}/tirpc|${includedir}|g' libtirpc.pc.in

[1] https://build.opensuse.org/package/view_file/openSUSE:Factory/libtirpc/libtirpc.spec?expand=1

> Regards,
> Yann E. MORIN.

Kind regards,
Petr

  reply	other threads:[~2020-12-29 21:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-02 18:49 [Buildroot] [PATCH 1/2] libtirpc: remove NIS patch Petr Vorel
2020-12-02 18:49 ` [Buildroot] [PATCH 2/2] package/libtirpc: bump version to 1.3.1 Petr Vorel
2020-12-02 18:51   ` Petr Vorel
2020-12-29 20:50   ` Yann E. MORIN
2020-12-29 20:57     ` Petr Vorel
2020-12-29 20:46 ` [Buildroot] [PATCH 1/2] libtirpc: remove NIS patch Yann E. MORIN
2020-12-29 21:06   ` Petr Vorel [this message]
2020-12-29 23:00     ` Yann E. MORIN

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=20201229210600.GC2801@pevik \
    --to=petr.vorel@gmail.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.