From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] busybox build fails with recent oselas toolchain
Date: Fri, 11 Dec 2020 10:03:40 +0100 [thread overview]
Message-ID: <20201211090340.GQ10804@pengutronix.de> (raw)
In-Reply-To: <2754832.nNXZTqcv4L@ada>
On Mon, Oct 19, 2020 at 01:52:38PM +0200, Alexander Dahl wrote:
> Am Montag, 19. Oktober 2020, 10:54:49 CEST schrieb Alexander Dahl:
> > with the recent OSELAS Toolchain 2020.08 building busybox fails like this:
> >
> > -----------------------
> > target: busybox.compile
> > -----------------------
> >
> > make: Entering directory '/home/adahl/Work/bsp/tt/ncl/platform-ncl/build-
> > target/busybox-1.31.1'
> > CC util-linux/mount.o
> > util-linux/mount.c:253:11: fatal error: rpc/rpc.h: No such file or directory
> > compilation terminated.
> > make[1]: *** [scripts/Makefile.build:197: util-linux/mount.o] Error 1
> > make: *** [Makefile:743: util-linux] Error 2
> > make: Leaving directory '/home/adahl/Work/bsp/tt/ncl/platform-ncl/build-
> > target/busybox-1.31.1'
> > make: *** [/usr/local/lib/ptxdist-2020.08.0/rules/post/
> > ptxd_make_world_compile.make:20: /home/adahl/Work/bsp/tt/ncl/platform-ncl/
> > state/busybox.compile] Error 2
>
> Got a hint in IRC this is caused by BUSYBOX_FEATURE_MOUNT_NFS and indeed, if I
> deactivate that, busybox build does not fail anymore.
The rpc stuff was removed in the new glibc. We'll need to link to tirpc
instead for this.
> > I was trying to build with /opt/OSELAS.Toolchain-2020.08.0/arm-v5te-linux-
> > gnueabi/gcc-10.2.1-glibc-2.32-binutils-2.35-kernel-5.8-sanitized/bin and I
> > could not find any fixes in ptxdist git since ptxdist-2020.08.0 for that.
> >
> > The same BSP builds successful with
> > /opt/OSELAS.Toolchain-2019.09.1/arm-v5te-
> > linux-gnueabi/gcc-9.2.1-glibc-2.30-binutils-2.32-kernel-5.0-sanitized/bin
>
> I got other errors now. I could avoid the libnsl.so problem Jon Ringle
> reported two weeks ago by disabling PTXCONF_GLIBC_NSS_COMPAT and
> PTXCONF_GLIBC_NSL in the BSP.
>
> Now I face compile errors with sudo and logrotate. I saw sudo is already fixed
> with later ptxdist versions, so I will now migrate to 2020.10.0 first, before
> proceeding with latest toolchain tests.
I've removed some more LIBC_NSL dependencies with the 2020.12.0 release.
But there is still a lot more work to do. Especially with the new
-fno-common default.
Michael
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
prev parent reply other threads:[~2020-12-11 9:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-19 8:54 Alexander Dahl
2020-10-19 11:52 ` Alexander Dahl
2020-12-11 9:03 ` Michael Olbrich [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=20201211090340.GQ10804@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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