Displaying 20 results from an estimated 400 matches similar to: "[PATCH] Avoid infinite loop during build with make 3.82"
2010 Mar 02
17
[PATCH 00/16] External building, update for 2.6.33 and multiple root devices.
The following patchset implements 3 seperate series of changes.
External Building
=================
Patches 1 through 8 enable to use of klibc's build system while leaving the src
tree pristine (and potentially read only). Specifically:
- srctree=<Sources for klibc>
- objtree=<Ouput directory for klibc>
- KLIBCKERNELSRC=<Kernel sources>
- KLIBCKERNELOBJ=<Kernel
2010 Oct 04
0
No subject
* WARNING: Backward-incompatibility!
The '$?' variable now contains all prerequisites that caused the target to
be considered out of date, even if they do not exist (previously only
existing targets were provided in $?).
---
usr/klibc/socketcalls/Kbuild | 3 +++
usr/klibc/syscalls/Kbuild | 3 +++
2 files changed, 6 insertions(+), 0 deletions(-)
diff --git
2005 Jul 30
3
kbuild updates to klibc
Hi Peter & others.
Here are three patches that does the following:
#1 - Update kbuild part of klibc so make clean works
Adds gzip including a sample kbuild file
#2 - Factor out definition of usr/ to two variables
#3 - Move kbuild files to reflect location in the kernel
As requested in earlier mail I need a bit of guidiance of what you
expect from the kernel integrated parts of klibc.
2006 Apr 11
6
klibc kbuild status
Hi hpa & others.
Following is a list of issues that I hope to be addressed soon so
we are in even better shape for -mm inclusion.
1) rebuild initramfs when content changes.
> It is a simple matter of copying in usr/Makefile from the latest
> -linus kernel and replace the 10 first lines with the content from
> klibc Kbuild file.
2) havesyscalls.h is not deleted after make
2007 Dec 10
1
[git patch] m-i-t support, ipconfig fix
hello hpa,
please pull latest
git pull git://git.debian.org/~maks/klibc.git maks
forgot to ask to keep git port open for our boxes at university,
thus moved my tree over too the alioth box.
for the changes
maximilian attems (4):
[klibc] klibc/socketcalls/.gitignore addition
[klibc] elf.h add support for st_info field
[klibc] remove local insmod.c copy
[klibc] ipconfig
2003 Oct 04
0
klibc: kbuild improvements
Hi Bryan and other klibc people.
I have taken a stamp on the Makefiles for klibc, this is what
I came up with.
1) No longer recompile on every invocation
2) Correct checking on dependencies
3) Simpler makefile syntax (almost all over the place)
I compile-time tested it only.
Two open issues:
a) Do we realy use .a files for initramfs. I renemed that to the
executable.
b) I renamed
2007 Sep 22
3
[git patch] module-init-tools fixes
hello hpa,
quite easy to get m-i-t build against klibc,
so i propose to kill the old local insmod copy.
sent the only local m-i-t fix upstream, please pull:
git pull git://brane.itp.tuwien.ac.at/~mattems/klibc.git maks
maximilian attems (3):
[klibc] klibc/socketcalls/.gitignore addition
[klibc] elf.h add support for st_info field
[klibc] remove local insmod.c copy
and diffstat
2019 Jan 07
4
[PATCH klibc 0/4] Fix the KLIBCKERNEL{SRC,OBJ} mess
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]
2008 Feb 13
4
[PATCHv3 1/3] x86: use ELF format in compressed images.
This allows other boot loaders such as the Xen domain builder the
opportunity to extract the ELF file.
Signed-off-by: Ian Campbell <ijc@hellion.org.uk>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: H. Peter Anvin <hpa@zytor.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: virtualization@lists.linux-foundation.org
---
2008 Feb 13
4
[PATCHv3 1/3] x86: use ELF format in compressed images.
This allows other boot loaders such as the Xen domain builder the
opportunity to extract the ELF file.
Signed-off-by: Ian Campbell <ijc@hellion.org.uk>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: H. Peter Anvin <hpa@zytor.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: virtualization@lists.linux-foundation.org
---
2007 Jun 20
9
[PATCH 0/9] x86 boot protocol updates
[ This patch depends on the cross-architecture ELF cleanup patch. ]
This series updates the boot protocol to 2.07 and uses it to implement
paravirtual booting. This allows the bootloader to tell the kernel
what kind of hardware/pseudo-hardware environment it's coming up under,
and the kernel can use the appropriate boot sequence code.
Specifically:
- Update the boot protocol to 2.07, which
2007 Jun 20
9
[PATCH 0/9] x86 boot protocol updates
[ This patch depends on the cross-architecture ELF cleanup patch. ]
This series updates the boot protocol to 2.07 and uses it to implement
paravirtual booting. This allows the bootloader to tell the kernel
what kind of hardware/pseudo-hardware environment it's coming up under,
and the kernel can use the appropriate boot sequence code.
Specifically:
- Update the boot protocol to 2.07, which
2007 Jun 06
7
[PATCH RFC 0/7] proposed updates to boot protocol and paravirt booting
This series:
1. Updates the boot protocol to version 2.07
2. Clean up the existing build process, to get rid of tools/build and
make the linker do more heavy lifting
3. Make the bzImage payload an ELF file. The bootloader can extract
this as a naked ELF file by skipping over boot_params.setup_sects worth
of 16-bit setup code.
4. Update the boot_params to 2.07, and update the
2007 Jun 06
7
[PATCH RFC 0/7] proposed updates to boot protocol and paravirt booting
This series:
1. Updates the boot protocol to version 2.07
2. Clean up the existing build process, to get rid of tools/build and
make the linker do more heavy lifting
3. Make the bzImage payload an ELF file. The bootloader can extract
this as a naked ELF file by skipping over boot_params.setup_sects worth
of 16-bit setup code.
4. Update the boot_params to 2.07, and update the
2005 Jul 28
0
[PATCH] Use KLIBSRC + KLIBINC consistent in kbuild files
Factor out all kernel specific path's (those containing usr/)
into two variables: KLIBSRC + KLIBINC. Set the variables
in a kernel spcific Kbuild file.
Sam
commit e6f989c1597a837f4aecbd11083697184c089611
tree 93f88d7564bb9e4d4bc95fd455b842d0bd0fdc54
parent 8151f4a98f82fba4fe3b949f49da4ab8bba71501
author Sam Ravnborg <sam@mars.(none)> Thu, 28 Jul 2005 23:36:07 +0200
committer Sam
2006 Jul 09
6
[PATCH/RFC] klibc/kbuild: use separate kbuild files for each klibc subdirectory
This fixes a long standing issue where it was not possible to
do "make usr/klibc/arch/x86_64/longjmp.o" in the kernel.
The principle is that all .o files to be part of klibc are listed
with klib-y. For each directory a klib.list file is made that specify
all .o file and the final AR then adds all .o files to create libc.a.
This patch introduce the infrastructure and converts x86_64 to
2005 Jul 31
5
Shared versus static linked executables - and strip
I'm still pondering with kbuild and klibc.
Next in line was to get ipconfig support in the kernel (build wise).
A little challenge that is bigger than anticipated was to create
a shared executable. This required a far bigger rewrite of Kbuild.klibc
than originally planned. The good part is that I now managed to treat
linking of objects with single and multiple .o files almost the same.
2007 Jun 15
11
[PATCH 00/10] paravirt/subarchitecture boot protocol
This series updates the boot protocol to 2.07 and uses it to implement
paravirtual booting. This allows the bootloader to tell the kernel
what kind of hardware/pseudo-hardware environment it's coming up under,
and the kernel can use the appropriate boot sequence code.
Specifically:
- Update the boot protocol to 2.07, which adds fields to specify the
hardware subarchitecture and some
2007 Jun 15
11
[PATCH 00/10] paravirt/subarchitecture boot protocol
This series updates the boot protocol to 2.07 and uses it to implement
paravirtual booting. This allows the bootloader to tell the kernel
what kind of hardware/pseudo-hardware environment it's coming up under,
and the kernel can use the appropriate boot sequence code.
Specifically:
- Update the boot protocol to 2.07, which adds fields to specify the
hardware subarchitecture and some
2007 Jun 15
11
[PATCH 00/10] paravirt/subarchitecture boot protocol
This series updates the boot protocol to 2.07 and uses it to implement
paravirtual booting. This allows the bootloader to tell the kernel
what kind of hardware/pseudo-hardware environment it's coming up under,
and the kernel can use the appropriate boot sequence code.
Specifically:
- Update the boot protocol to 2.07, which adds fields to specify the
hardware subarchitecture and some