similar to: Building klibc on 64-bit Ubuntu

Hi All: We have some patches to port klibc to ArmV8. The first set of patches from Neil Williams fixes the build issues. The second set of patches from Anil Singhar fixes functionalities. The following files have changed in the second set of patches ------------------------------------------------------------------------------------------ usr/include/arch/aarch64/klibc/archconfig.h

On 10/16/2013 12:52 AM, Anil Singhar wrote: > Hi HPA, > > Thanks for your reply. One confusion I have is: > > e.g. 'access' is not supported in aarch64, so should the declaration be: > > <!aarch64> int access(const char *, int); <-- This is how it is currently > indicating that only aarch64 doesn't support it. > > OR > > <?> int

On Wed, Aug 21, 2013 at 01:39:50PM +0200, leroy christophe wrote: > > Le 21/08/2013 12:20, maximilian attems a ?crit : > >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

Le 21/08/2013 17:36, leroy christophe a ?crit : > > Le 21/08/2013 17:15, maximilian attems a ?crit : >> On Wed, Aug 21, 2013 at 01:39:50PM +0200, leroy christophe wrote: >>> Le 21/08/2013 12:20, maximilian attems a ?crit : >>>> On Tue, Aug 20, 2013 at 07:44:39AM +0200, leroy christophe wrote: >>>>> Find attached two patches I have in order to build

Commit-ID: 25a66fa8d8623fae267f6807b56438cd7c40e034 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=25a66fa8d8623fae267f6807b56438cd7c40e034 Author: maximilian attems <max at stro.at> AuthorDate: Wed, 21 Aug 2013 17:31:25 +0200 Committer: maximilian attems <max at stro.at> CommitDate: Wed, 21 Aug 2013 17:32:16 +0200 README.klibc: update build information It

On Wed, Aug 21, 2013 at 06:48:08PM +0200, maximilian attems wrote: > On Wed, Aug 21, 2013 at 06:03:41PM +0200, leroy christophe wrote: > > > > Note that step B is working well. > > It is step C, the 'make install', which fails. > > right, it is the toplevel Makefile one needs to poke for the target. > see belows proper patch: >From

On 10/16/2013 12:42 AM, Anil Singhar wrote: > Hi HPA, > > Regarding the architecture un-supported system calls, I wrapped them with > #ifndef __NR_<foo> .. #endif /* __NR_<foo> */ switches. I have already done > that. But you also mentioned that in SYSCALLS.def all these calls should be > present and marked with '?'.. Is that right..? Could you please give

Gauche as it may be, I am reviving an old thread from January: http://www.zytor.com/pipermail/klibc/2013-January/003402.html. Building Smoothwall Express 3.1 in a chroot jail works well. (gcc 4.7.2, linux 3.4.58, klibc 2.0.1, et alia). I'm now working on 'express-next' to prepare for a future release (linux 3.10.7, klibc 2.0.2, et alia). Same build system, worked through some

Hello, Here is V2 of the arm64 support for klibc patch set. Notable changes since the original series: * fp regs dropped from setjmp/longjmp * chmod, lstat and stat re-implemented with *at functions. * open64 merged into open. As with the original, this series is to be applied against the latest klibc, just after 25a66fa README.klibc: update build information V2 has been tested on x86_64

On Wed, 9 Oct 2013 15:51:32 +0200 maximilian attems <maks at stro.at> wrote: > On Wed, Oct 09, 2013 at 03:14:44PM +0530, Anil Singhar wrote: > > Hi All: > > > > We have some patches to port klibc to ArmV8. > > > > The first set of patches from Neil Williams fixes the build issues. > > The second set of patches from Anil Singhar fixes functionalities.

Are there any version compatibilities between linux and klibc? I tried to compile the latest klibc (1.5.18) with the latest linux (2.6.32.15) and there is miserable compile failures. It looks like klibc wants some headers to be in include/asm (linked in my case to include/asm-x86) but they are instead in include/asm-generic (it seems all headers but one are in there). I put together this script

The kernel header guard to ensure that headers aren't included from userland moved in commit 69c8f52b. This causes the following message to be emitted when building klibc (which is designed to use kernel headers explicitly): /usr/local/src/git/linux-2.6//include/linux/types.h:13:2: warning: #warning "Attempt to use kernel headers from user space, see

It seems the mailing list has been broken for several days. It should now be temporarily fixed, but because the fix is temporary I can't promise it won't happen again until the permanent fix is available. Sorry for that. -hpa

Version: 2.0.4 and git Kernel tested: 3.10.70 Description: make install fails with: No rule to make target `headers_install'. File impacted: scripts/Kbuild.install Error Received: make[2]: *** No rule to make target `headers_install'. Stop. make[1]: *** [header] Error 2 make: *** [install] Error 2 Issue: KLIBCKERNELSRC=`pwd`/linux/usr points to Makefile without headers_install rule.

as the next klibc release 1.5.16 looks like shaping up, I have a trouble to build that for Debian. currently I build depent on linux-libc-dev, I don't know what against I can build latest klibc, see klibc fails to build due too: make -C linux/ ARCH=x86_64 INSTALL_HDR_PATH=debian/tmp/usr/lib/klibc/ headers_install make[3]: *** No rule to make target `headers_install'. Stop. make[2]: ***

We currently use KLIBCKERNELSRC and KLIBCKERNELOBJ variables which used to be required to point to a kernel source and object directories. However the kernel headers were reorganised starting in Linux 3.7 such that that doesn't work properly. This series removes KLIBCKERNELOBJ and changes the use and documentation of KLIBCKERNELSRC to be consistent. Ben. Ben Hutchings (4): [klibc]

H. Peter Anvin dixit: >You should be using the output of "make headers_install" to build klibc. Hm. Can we catch that somehow? Like? #ifdef using_uninstalled_kernel_headers # error Go RTFM! #endif ? in the klibc sources, centrally somewhere? Ideally, a klibc header that?d also be included when using klcc to build some? thing, so that both klibc-build time and klibc-use time would

Also there are lines as follows: <ppc64> int stat::stat(const char *, struct stat *); Should they be changed likewise too..? I mean to <?> Thanks, Anil On 16 October 2013 13:40, Anil Singhar <anil.singhar at linaro.org> wrote: > OK, I will change all <!aarch64> to <?> then. How about lines declared > like the following: > >

Hello, This series introduces arm64 support to klibc. I've rebased the work from Neil Williams and Anil Singhar into the following three patches. Most of the code changes are due to new syscall implementations being needed for arm64 as a only a minimal set of syscalls are defined in the arm64 kernel. This series is to be applied against the latest klibc, just after 25a66fa README.klibc:

On Wed, 9 Oct 2013 10:44:27 +0000 (UTC) Thorsten Glaser <tg at mirbsd.de> wrote: > Anil Singhar dixit: > > >Manual testing as provided within the package has been done with all > >tests passing. This includes the units tests available under > >usr/klibc/tests, usr/utils, usr/dash and usr/gzip. For dash and > >gzip, only sanity testing has been done. > >