Thank you for the help! I wanted to compile the library so I could make some changes, test them, and then maybe create a pull request. Funny how I didn't realise I need to cross-compile it, since thats what I mostly do at work. Best regards, Daniel Dubinsky On Nov 28, 2017 20:08, "Waldemar Brodkorb" <wbx@uclibc-ng.org> wrote: Hi Daniel, Daniel Dubinsky wrote,

Hello,

Sorry for the bother but I’ve been struggling with compiling uclibc-ng. All I did was clone; make defconfig; make.

I get the following error:

CC ldso/ldso/ldso.oS

In file included from ./include/bits/posix1_lim.h:152:0,

from ./include/limits.h:144,

from ./include/sys/param.h:25,

from ./ldso/include/ldso.h:43,

from ldso/ldso/ldso.c:32:

./include/bits/local_lim.h:38:26: fatal error: linux/limits.h: No such file or directory

compilation terminated.

Makerules:370: recipe for target 'ldso/ldso/ldso.oS' failed

make: *** [ldso/ldso/ldso.oS] Error 1

I’ve tried to remove -nostdinc, the compilation then proceeds but with no success. I also tried to install the following packages: kernel-package, linux-libc-dev, binutils, libc-dev-bin, linux-headers-4.10.0-35 and linux-headers-generic.

Can anyone help?

The choosen subject is a little bit strange. If you natively compile uClibc-ng, which is more or less an unusual approach. uClibc-ng is optimized for cross-compilation and a used toolchain needs to be specially configured to produce a target filesystem. For your case the defconfig can not work, because you need to configure the place where your Linux headers are installed. Therefore make menuconfig and pointing to a working Linux headers path is an necessary step. Most of the users use Buildroot, OpenADK or something else, when they have the demand to use uClibc-ng. What is your exact use case? best regards Waldemar