Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] /bin/ld: skipping incompatible //lib/libpam.so when searching for -lpam
Date: Sat, 27 Feb 2021 09:15:31 +0100	[thread overview]
Message-ID: <20210227091531.588cd46c@gmx.net> (raw)
In-Reply-To: <1614397562997-0.post@n4.nabble.com>

On Fri, 26 Feb 2021 21:46:02 -0600 (CST), GA K <guyarkam@gmail.com> wrote:

> The problem is related to the linking of runuser during the  build of
> host-util-linux.
>
> On the first system, the build process completes successfully because the
> host-util-linux configuration script fails to locate PAM header files among
> other things and issues the following warning:
>
> configure: WARNING: ncursesw, ncurses or slang library not found; not
> building irqtop
> configure: WARNING: linux/blkzoned.h header not found; not building blkzone
> checking for LIBUSER... no
> configure: WARNING: PAM header file not found; not building runuser
> checking for ECONF... no
> configure: WARNING: libpython not found; not building pylibmount
> checking that generated files are newer than configure... done
>
> On the second system, the host-util-linux configuration script finds the PAM
> header (I have these lines)
> checking for LIBUSER... no
> checking for ECONF... no
>  and proceeds with the build of runuser. However, on this system (64-bit
> machine)  /lib/libpam.so points to the file libpam.so.0.83.1 which is a
> 32-bit ELF file.
>
> $ file libpam.so.0.83.1
> libpam.so.0.83.1: ELF 32-bit LSB shared object, Intel 80386, version 1
> (SYSV), dynamically linked,
> BuildID[sha1]=75203587ca0241a766a756b1cec17c0fc54dd479, stripped
>
>
> I have no root access to the second machine so my only solution is to skip
> runuser during the host-util-linux build process. I see that
> package/util-linux/Config.in defines BR2_PACKAGE_UTIL_LINUX_RUNUSER and
> automatically selects it when BR2_PACKAGE_LINUX_PAM is selected. In my
> particular case, I am not selecting BR2_PACKAGE_LINUX_PAM and yet runuser
> gets selected. I am hence wondering what would be the safest way to skip
> runuser while building host-util-linux.
>
> Thanks for any hint

Disable runuser for the host build (completely untested):

diff --git a/package/util-linux/util-linux.mk b/package/util-linux/util-linux.mk
index 0178c52bac..09acaca1a7 100644
--- a/package/util-linux/util-linux.mk
+++ b/package/util-linux/util-linux.mk
@@ -211,6 +211,7 @@ HOST_UTIL_LINUX_CONF_OPTS += \
 	--disable-nsenter \
 	--disable-pg \
 	--disable-rfkill \
+	--disable-runuser \
 	--disable-schedutils \
 	--disable-setpriv \
 	--disable-setterm \

Regards,
Peter

>
>
>
>
> --
> Sent from: http://buildroot-busybox.2317881.n4.nabble.com/
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

  reply	other threads:[~2021-02-27  8:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-22 18:07 [Buildroot] /bin/ld: skipping incompatible //lib/libpam.so when searching for -lpam Guy Ka
2021-02-27  3:46 ` GA K
2021-02-27  8:15   ` Peter Seiderer [this message]
2021-02-27 15:25     ` GA K

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=20210227091531.588cd46c@gmx.net \
    --to=ps.report@gmx.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox