Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Andre McCurdy <armccurdy@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] busybox: Enable FEATURE_MOUNT_NFS and use libtirpc
Date: Sun, 10 Jun 2018 13:05:54 +0200	[thread overview]
Message-ID: <20180610110554.GA1355@jama> (raw)
In-Reply-To: <CAJ86T=Xk+fUWoOM5igiD6ZBTQfb4opLooTa3HeAFHVs7GFAvDg@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1929 bytes --]

On Wed, May 30, 2018 at 10:39:16AM -0700, Andre McCurdy wrote:
>  On Thu, May 10, 2018 at 12:26 PM, Khem Raj <raj.khem@gmail.com> wrote:
> > On 5/10/18 12:16 PM, Martin Jansa wrote:
> >>>
> >>> On second thought, this probably should be enabled using a config
> >>> fragment, since its not gonna link in another library it may not be
> >>> common case to justify for a default config.
> >>
> >> That's true, I've enabled CONFIG_FEATURE_MOUNT_NFS mostly to show how to
> >> reproduce the issue.
> >>
> >> If there isn't interest to enable this by default, I'm fine with keeping
> >> this
> >> locally (to enable it only with our defconfig changes which enable it).
> >
> > I think keeping it as a nfsmount.cfg which then can be applied via a
> > bbappend could be a good option. May be adding a PACKAGECONFIG to control
> > the -I flag and libtirpc dependency would be nice too
> 
> According to the busybox config help, CONFIG_FEATURE_MOUNT_NFS is only
> required for kernel versions before 2.6.23. Do we officially support
> kernels that old in oe-core? Or should this be in a .bbappend etc in
> separate layer?

OK, I agree that this should be kept in separate layer. If anyone needs
it, the working version (with tirpc added in CONFIG_EXTRA_LDLIBS) is
attached.

> //config:config FEATURE_MOUNT_NFS
> //config:    bool "Support mounting NFS file systems on Linux < 2.6.23"
> //config:    default n
> //config:    depends on MOUNT
> //config:    select FEATURE_SYSLOG
> //config:    help
> //config:    Enable mounting of NFS file systems on Linux kernels prior
> //config:    to version 2.6.23. Note that in this case mounting of NFS
> //config:    over IPv6 will not be possible.
> //config:
> //config:    Note that this option links in RPC support from libc,
> //config:    which is rather large (~10 kbytes on uclibc).

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #1.2: 0001-busybox-Enable-FEATURE_MOUNT_NFS-and-use-libtirpc.patch --]
[-- Type: text/x-diff, Size: 2680 bytes --]

From 3316407c73058173bcfa1b9fabcad4592d23cbfc Mon Sep 17 00:00:00 2001
From: Martin Jansa <Martin.Jansa@gmail.com>
Date: Thu, 10 May 2018 12:08:58 +0000
Subject: [PATCH] busybox: Enable FEATURE_MOUNT_NFS and use libtirpc

* We dropped in-tree obsoleted rpc from glibc and now busybox builds
  which had CONFIG_FEATURE_MOUNT_NFS enabled were failing with:
  | util-linux/mount.c:252:11: fatal error: rpc/rpc.h: No such file or directory
  |  # include <rpc/rpc.h>
  |            ^~~~~~~~~~~
  | compilation terminated.
  | make[1]: *** [util-linux/mount.o] Error 1

Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
---
 meta/recipes-core/busybox/busybox.inc       | 6 +++---
 meta/recipes-core/busybox/busybox/defconfig | 4 ++--
 2 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/meta/recipes-core/busybox/busybox.inc b/meta/recipes-core/busybox/busybox.inc
index d1675c37aa..2db19ed317 100644
--- a/meta/recipes-core/busybox/busybox.inc
+++ b/meta/recipes-core/busybox/busybox.inc
@@ -3,7 +3,7 @@ DESCRIPTION = "BusyBox combines tiny versions of many common UNIX utilities into
 HOMEPAGE = "http://www.busybox.net"
 BUGTRACKER = "https://bugs.busybox.net/"
 
-DEPENDS += "kern-tools-native"
+DEPENDS += "kern-tools-native libtirpc"
 
 # bzip2 applet in busybox is based on lightly-modified bzip2 source
 # the GPL is version 2 only
@@ -15,8 +15,8 @@ SECTION = "base"
 # Whether to split the suid apps into a seperate binary
 BUSYBOX_SPLIT_SUID ?= "1"
 
-export EXTRA_CFLAGS = "${CFLAGS}"
-export EXTRA_LDFLAGS = "${LDFLAGS}"
+export EXTRA_CFLAGS = "${CFLAGS} -I${STAGING_INCDIR}/tirpc"
+export EXTRA_LDFLAGS = "${LDFLAGS} -ltirpc"
 
 EXTRA_OEMAKE = "CC='${CC}' LD='${CCLD}' V=1 ARCH=${TARGET_ARCH} CROSS_COMPILE=${TARGET_PREFIX} SKIP_STRIP=y HOSTCC='${BUILD_CC}' HOSTCPP='${BUILD_CPP}'"
 
diff --git a/meta/recipes-core/busybox/busybox/defconfig b/meta/recipes-core/busybox/busybox/defconfig
index fbb5fd852c..2e920277b7 100644
--- a/meta/recipes-core/busybox/busybox/defconfig
+++ b/meta/recipes-core/busybox/busybox/defconfig
@@ -51,7 +51,7 @@ CONFIG_CROSS_COMPILER_PREFIX=""
 CONFIG_SYSROOT=""
 CONFIG_EXTRA_CFLAGS=""
 CONFIG_EXTRA_LDFLAGS=""
-CONFIG_EXTRA_LDLIBS=""
+CONFIG_EXTRA_LDLIBS="tirpc"
 
 #
 # Installation Options ("make install" behavior)
@@ -638,7 +638,7 @@ CONFIG_MOUNT=y
 # CONFIG_FEATURE_MOUNT_VERBOSE is not set
 # CONFIG_FEATURE_MOUNT_HELPERS is not set
 # CONFIG_FEATURE_MOUNT_LABEL is not set
-# CONFIG_FEATURE_MOUNT_NFS is not set
+CONFIG_FEATURE_MOUNT_NFS=y
 # CONFIG_FEATURE_MOUNT_CIFS is not set
 CONFIG_FEATURE_MOUNT_FLAGS=y
 CONFIG_FEATURE_MOUNT_FSTAB=y
-- 
2.17.1


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]

  reply	other threads:[~2018-06-10 11:05 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-05  0:26 [RFT] GCC 8.1 Khem Raj
2018-05-09  9:38 ` Martin Jansa
2018-05-10 12:20   ` [PATCH] busybox: Enable FEATURE_MOUNT_NFS and use libtirpc Martin Jansa
2018-05-10 13:01     ` Burton, Ross
2018-05-10 18:21       ` Khem Raj
2018-05-10 18:24         ` Khem Raj
2018-05-10 19:16           ` Martin Jansa
2018-05-10 19:26             ` Khem Raj
2018-05-30 17:39               ` Andre McCurdy
2018-06-10 11:05                 ` Martin Jansa [this message]
2018-05-10 18:50   ` [RFT] GCC 8.1 Khem Raj
2018-05-10 19:11     ` Martin Jansa
2018-05-10 19:27       ` Andre McCurdy
2018-05-10 21:43         ` Martin Jansa
2018-05-10 22:07           ` Martin Jansa
2018-05-10 22:35             ` Khem Raj
2018-05-10 22:38             ` Andre McCurdy
2018-05-10 22:38               ` Martin Jansa
2018-05-10 22:40                 ` Andre McCurdy
2018-05-10 22:50                   ` Martin Jansa
2018-05-10 23:11                     ` Andre McCurdy
2018-05-10 23:32                       ` Martin Jansa
2018-05-10 23:41                         ` Andre McCurdy
2018-05-11  0:55                       ` Khem Raj
2018-05-11  1:00                         ` Andre McCurdy
2018-05-11  1:06                           ` Khem Raj
2018-05-11  1:11                             ` Andre McCurdy
2018-05-11  1:16                               ` Khem Raj
2018-05-11  1:21                                 ` Andre McCurdy
2018-05-17 10:46       ` Martin Jansa
2018-05-18  5:54         ` Khem Raj
2018-05-24 15:08         ` Martin Jansa
2018-05-10 14:34 ` Dan McGregor
2018-05-10 18:53   ` Khem Raj
2018-05-14 16:33     ` Dan McGregor
2018-05-14 17:09       ` Martin Jansa
     [not found] ` <CAGAf8LxceSXvK-pgfWYDvYLmcvMMK0D5q==PKG9jeRWs6YEbGA@mail.gmail.com>
2018-05-10 19:21   ` [yocto] " Khem Raj
2018-05-11 22:05 ` Burton, Ross
2018-05-12  6:10   ` Khem Raj
2018-05-13 23:35   ` Khem Raj

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=20180610110554.GA1355@jama \
    --to=martin.jansa@gmail.com \
    --cc=armccurdy@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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