search for: iusr

...rame-pointer -o scripts/basic/fixdep scripts/basic/fixdep.c : make -rR -f /root/ofs/trunk/packages/klibc-2.0.2/scripts/Kbuild.klibc obj=usr/klibc ppc-linux-gcc -Wp,-MD,usr/klibc/.__static_init.o.d -nostdinc -iwithprefix include -I/root/ofs/trunk/packages/klibc-2.0.2/usr/include/arch/ppc -Iusr/include/arch/ppc -I/root/ofs/trunk/packages/klibc-2.0.2/usr/include/bits32 -Iusr/include/bits32 -I/root/ofs/trunk/packages/klibc-2.0.2/usr/klibc/../include -Iusr/klibc/../include -I/root/ofs/trunk/packages/klibc-2.0.2/usr/include -Iusr/include -I/root/gen/trunk/knl/linux/usr//include -I/root/gen/...

On Tue, Aug 20, 2013 at 07:44:39AM +0200, leroy christophe wrote: > > > Find attached two patches I have in order to build klibc 2.0.2 > against kernel 3.8.13 > We had to introduce those patches when going from kernel 3.6 to kernel 3.7 > Hope it helps. > those patches are wrong and again very brittle. just use the way it is described in `make help': A) cd ~/src/linux

...0110225 and later would break klibc's builds as follows: TYPE unsigned int: size 4, sign 0 TYPE unsigned long: size 4, sign 0 TYPE void *: size 4, sign 0 gcc -Wp,-MD,usr/klibc/syscalls/._exit.o.d -D__ASSEMBLY__ -nostdinc -iwithprefix include -I/build/buildd/klibc-1.5.20/usr/include/arch/arm -Iusr/include/arch/arm -I/build/buildd/klibc-1.5.20/usr/include/bits32 -Iusr/include/bits32 -I/build/buildd/klibc-1.5.20/usr/klibc/../include -Iusr/klibc/../include -I/build/buildd/klibc-1.5.20/usr/include -Iusr/include -I/build/buildd/klibc-1.5.20/linux/include -Ilinux/include -I/build/buildd/klibc-1.5....

...43743 <1843743 at bugs.launchpad.net> Public bug reported: https://launchpadlibrarian.net/441262209/buildlog_ubuntu-eoan- amd64.klibc_2.0.6-1ubuntu1_BUILDING.txt.gz gcc -Wp,-MD,usr/klibc/.sigsuspend.o.d -nostdinc -iwithprefix include -I/<<PKGBUILDDIR>>/usr/include/arch/x86_64 -Iusr/include/arch/x86_64 -I/<<PKGBUILDDIR>>/usr/include/bits64 -Iusr/include/bits64 -I/<<PKGBUILDDIR>>/usr/klibc/../include -Iusr/klibc/../include -I/<<PKGBUILDDIR>>/usr/include -Iusr/include -I/<<PKGBUILDDIR>>/linux/include -Ilinux/include -D__KLIBC__=2 -...

...klibc source package in Eoan: Confirmed Bug description: https://launchpadlibrarian.net/441262209/buildlog_ubuntu-eoan- amd64.klibc_2.0.6-1ubuntu1_BUILDING.txt.gz gcc -Wp,-MD,usr/klibc/.sigsuspend.o.d -nostdinc -iwithprefix include -I/<<PKGBUILDDIR>>/usr/include/arch/x86_64 -Iusr/include/arch/x86_64 -I/<<PKGBUILDDIR>>/usr/include/bits64 -Iusr/include/bits64 -I/<<PKGBUILDDIR>>/usr/klibc/../include -Iusr/klibc/../include -I/<<PKGBUILDDIR>>/usr/include -Iusr/include -I/<<PKGBUILDDIR>>/linux/include -Ilinux/include -D__KLIBC__=2 -...

...klibc source package in Eoan: Confirmed Bug description: https://launchpadlibrarian.net/441262209/buildlog_ubuntu-eoan- amd64.klibc_2.0.6-1ubuntu1_BUILDING.txt.gz gcc -Wp,-MD,usr/klibc/.sigsuspend.o.d -nostdinc -iwithprefix include -I/<<PKGBUILDDIR>>/usr/include/arch/x86_64 -Iusr/include/arch/x86_64 -I/<<PKGBUILDDIR>>/usr/include/bits64 -Iusr/include/bits64 -I/<<PKGBUILDDIR>>/usr/klibc/../include -Iusr/klibc/../include -I/<<PKGBUILDDIR>>/usr/include -Iusr/include -I/<<PKGBUILDDIR>>/linux/include -Ilinux/include -D__KLIBC__=2 -...

...ders/ in the klibc dir: emake V=1 KLIBCKERNELSRC="${S}/linux/usr" (plus the rest of the opts) and the failure: x86_64-pc-linux-gnu-gcc -Wp,-MD,usr/klibc/.vsprintf.o.d -nostdinc -iwithprefix include -I/dev/shm/portage/dev-libs/klibc-2.0.3-r1/work/klibc-2.0.3/usr/include/arch/x86_64 -Iusr/include/arch/x86_64 -I/dev/shm/portage/dev-libs/klibc-2.0.3-r1/work/klibc-2.0.3/usr/include/bits64 -Iusr/include/bits64 -I/dev/shm/portage/dev-libs/klibc-2.0.3-r1/work/klibc-2.0.3/usr/klibc/../include -Iusr/klibc/../include -I/dev/shm/portage/dev-libs/klibc-2.0.3-r1/work/klibc-2.0.3/usr/include -Iu...

...m linux' include/asm-$ARCH to arch/$ARCH/asm, klibc fails to compile, because the in-linux-header files include from asm/, but this is not in the header search path. e.g. against linux-2.6.27 arm: arm-iwmmx-linux-gnueabi-gcc -Wp,-MD,usr/klibc/.vsnprintf.o.d -nostdinc -iwithprefix include -Iusr/include/arch/arm -Iusr/include/bits32 -Iusr/klibc/../include -Iusr/include -Ilinux/include -D__KLIBC__=1 -D__KLIBC_MINOR__=5 -D_BITSIZE=32 -fno-stack-protector -fno-exceptions -mabi=aapcs-linux -mno-thumb-interwork -Os -march=armv4 -mtune=strongarm -W -Wall -Wno-sign-compare -Wno-unused-parame...

On 12/26/2013 07:27 PM, Robin H. Johnson wrote: > (please CC me, I'm not on the klibc list, and I didn't get HPA's > response to my post). > > On Fri, Dec 27, 2013 at 12:24:34AM +0000, Thorsten Glaser wrote: >> H. Peter Anvin dixit: >>> You should be using the output of "make headers_install" to build klibc. > That makes easy cross-building a

...RNELSRC is the path to the kernel sources. In my case, this is /build/sources/linux/linux-3.10.7 (in the jail). There's an oddity in how include dirs are specified. First, an absolute 'relative' dir and it's companion: -I/build/sources/klibc/klibc-2.0.2/usr/klibc/../include -Iusr/klibc/../include Then the same dir is specified without relativity: -I/build/sources/klibc/klibc-2.0.2/usr/include -Iusr/include Is this intentional? Or is a var missing somewhere? Very near the beginning of 'make install', there's an error (asm/errno.h not found), but the make se...

...ernel sources. In my case, this is /build/sources/linux/linux-3.10.7 (in > the jail). > > There's an oddity in how include dirs are specified. First, an absolute > 'relative' dir and it's companion: > -I/build/sources/klibc/klibc-2.0.2/usr/klibc/../include > -Iusr/klibc/../include > Then the same dir is specified without relativity: > -I/build/sources/klibc/klibc-2.0.2/usr/include > -Iusr/include > Is this intentional? Or is a var missing somewhere? > > Very near the beginning of 'make install', there's an error (asm/errno...