[Buildroot] /bin/ld: skipping incompatible //lib/libpam.so when searching for -lpam

[Buildroot] /bin/ld: skipping incompatible //lib/libpam.so when searching for -lpam

[Guy Ka]

Hi all,
On a first system (64-bit Centos7), I configured and successfully built
Buildroot (released December 27th, 2020) for RISCV and then did
make source
I then moved the entire directory to another system (64-bit CentOs7)
without internet access. I then did
make clean
and
make
However, while building uuidgen of host-util-linux-2.36, I get the
following error:

/bin/ld: skipping  incompatible //lib/libpam.so when searching for -lpam

I guess there is an issue with the way pam on my second system is
configured but I have no clue where to start digging. I have no root
privilege on this second system.
Thanks for any clue.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20210222/2e41fcf5/attachment.html>

[Buildroot] /bin/ld: skipping incompatible //lib/libpam.so when searching for -lpam

[GA K]

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




--
Sent from: http://buildroot-busybox.2317881.n4.nabble.com/

[Buildroot] /bin/ld: skipping incompatible //lib/libpam.so when searching for -lpam

[Peter Seiderer]

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

[Buildroot] /bin/ld: skipping incompatible //lib/libpam.so when searching for -lpam

[GA K]

Thanks Peter, 
That works. 
Guy



--
Sent from: http://buildroot-busybox.2317881.n4.nabble.com/