similar to: klibc wrapper

What do I need to do to fix this? [jonsmirl@smirl klibc-0.184]$ make make[1]: Entering directory `/home/dri/klibc-0.184/klibc' gcc -Wp,-MT,syscalls.nrs,-MD,./.syscalls.nrs.d -mregparm=3 -DREGPARM=3 -march=i386 -Os -g -falign-functions=0 -falign-jumps=0 -falign-loops=0 -nostdinc -iwithprefix include -D__KLIBC__ -DBITSIZE=32 -I../include/arch/i386 -I../include/bits32 -I../include

Hi, I am trying to compile the version on rhel 5.x box. Nasm version 0.98.39 I extracted the tar.gz and ran make in the extracted directory. Here is where it stops. gcc -Wp,-MT,rawcon.o,-MD,./.rawcon.o.d -m32 -ffreestanding -fno-stack-protector -fwrapv -freg-struct-return -march=i386 -Os -fomit-frame-pointer -mregparm=3 -DREGPARM=3 -msoft-float -fno-exceptions -fno-asynchronous-unwind-tables

make[1]: Entering directory `/syslinux-4.02-6-ge841d69/dos' gcc -Wp,-MT,syslxopt.o,-MD,./.syslxopt.o.d -m32 -ffreestanding -fno-stack-protector -fwrapv -freg-struct-return -march=i386 -Os -fomit-frame-pointer -mregparm=3 -DREGPARM=3 -msoft-float -fno-exceptions -fno-asynchronous-unwind-tables -fno-strict-aliasing -falign-functions=0 -falign-jumps=0 -falign-labels=0 -falign-loops=0

I get this with current linus bk now and klibc 187 [jonsmirl@smirl ash]$ make sh mknodes.sh nodetypes nodes.c.pat . gcc -Wp,-MD,.cd.d -mregparm=3 -DREGPARM=3 -march=i386 -Os -g -falign-functions=0 -falign-jumps=0 -falign-loops=0 -nostdinc -iwithprefix include -D__KLIBC__ -DBITSIZE=32 -I../include/arch/i386 -I../include/bits32 -I../include -I../linux/include -I../linux/include2 -I../linux/include

klibc appears to build ok, some of the apps fail gcc -Wp,-MD,.fstype.d -mregparm=3 -DREGPARM=3 -march=i386 -Os -g -falign-functions=0 -falign-jumps=0 -falign-loops=0 -nostdinc -iwithprefix include -D__KLIBC__ -DBITSIZE=32 -I../include/arch/i386 -I../include/bits32 -I../include -I../linux/include -I../linux/include2 -W -Wall -c -o fstype.o fstype.c fstype.c: In function `romfs_image':

Hi Ady, Would it work if we removed "ifdef EFI_BUILD" condition and just add -mno-red-zone for all x86_64 builds? If not, do you have any ideas how to pass this flag? This could work, because the patch is adding the -mno-red-zone flag only for x86_64 builds, which are only used in the form of the efi64 target. The efi32 and bios targets are both 32-bit. BTW. I also tried 6.04-pre1 and

From: Sylvain Gault <sylvain.gault at gmail.com> The System V ABI for x86-64 specify that a "red zone" is an area of 128 bytes above the current stack frame. This area can be used by a called function in order to avoid the overhead of modifying the stack pointer. The direct effect is that interrupt/event/signal handlers must not write to this area. In the UEFI calling convention,

It's x86 arch.The reason of compiling pxelinux only is that i want to add tcp support, not http and ftp. ? 2014-05-08 18:09:15?"Gene Cumm" <gene.cumm at gmail.com> ??? On May 7, 2014 11:54 PM, "??" <muliu92 at 163.com> wrote: > make[4]: Entering directory `/mlsyslinux/bios/com32/libupload' > gcc -Wp,-MT,cpio.o,-MD,./.cpio.o.d -std=gnu99 -m32

Hi all, I just applied the generic path searching to ISOLINUX, and you can check it here: http://git.zytor.com/?p=users/liu/gsoc09_liu.git since commit 4bb194f14a43674cced3a8c35d5e625e59db32dc. hpa, for now, all the fs code have been converted to new-style interface and I have done my best to make all the fs C code be clean and readable. Well, it would be great if you take a minute to

Im using snapshot 0.81. make[1]: Entering directory `/home/rogelio/src/klibc-0.81/klibc' gcc -Wp,-MD,./.getenvtest.d -march=i386 -Os -falign-functions=0 -falign-jumps=0 -falign-loops=0 -nostdinc -iwithprefix include -I../klibc -I../klibc/arch/i386/include -I../klibc/include/bits32 -D__KLIBC__ -DBITSIZE=32 -I../klibc/include -I../linux/include -W -Wall -Wpointer-arith -Wwrite-strings

Well, it has to happen at some point, so I have officially pushed out SYSLINUX 3.72. The big news in this release is of course the ISOLINUX hybrid mode support (a single image which can be booted either from a CD-ROM or from a hard disk/USB stick), but there are plenty of more goodies in here, including the label listing (not technically completion) on the Tab key. As usual, huge thanks to

Hi, on my system the klibc/ash ( 0.197 ) doesn't compile: [ghigo@therra ash]$ pwd /home/ghigo/klibc/klibc-0.197/ash [ghigo@therra ash]$ make [...] gcc -Wp,-MD,.arith_lex.d -mregparm=3 -DREGPARM=3 -march=i386 -Os -g -falign-functions=0 -falign-jumps=0 -falign-loops=0 -nostdinc -iwithprefix include -D__KLIBC__ -DBITSIZE=32 -I../include/arch/i386 -I../include/bits32 -I../include

make -r -C /mlsyslinux -f /mlsyslinux/Makefile SRC="/mlsyslinux" \ OBJ=/mlsyslinux objdir=/mlsyslinux bios make[1]: Entering directory `/mlsyslinux' make -r -C /mlsyslinux/bios -f /mlsyslinux/Makefile SRC="/mlsyslinux" \ objdir=/mlsyslinux/bios OBJ=/mlsyslinux/bios HAVE_FIRMWARE=1 \ ARCH=i386 LDLINUX=ldlinux.c32 all make[2]:

Clang doesn't have a suitable replacement for libgcc readily available. Supply one that we know exists. Use "-fno-builtin-bcmp" to prevent clang from calling a function that doesn't exist. Signed-off-by: Bill Wendling <morbo at google.com> --- scripts/Kbuild.klibc | 2 ++ usr/klibc/arch/x86_64/MCONFIG | 2 ++ 2 files changed, 4 insertions(+) diff --git

On Tue, Oct 27, 2015 at 10:15 PM, Bruno Cornec via Syslinux <syslinux at zytor.com> wrote: > Bruno Cornec via Syslinux said on Wed, Oct 28, 2015 at 01:45:22AM +0100: >> >> Is there a way to increase the debug level of syslinux.efi in order to >> check what it tries to do and diagnose more precisely what happens ? > > > Ok, I tried to modify mk/devel.mk to put:

From: Michael Davidson <md at google.com> Add cc-name to klibc/scripts/Kbuild.include. Make optimization flags not supported by clang conditional on cc-name. Don't use -nostdinc when building klibc. While klibc doesn't (shouldn't) use the standard header files supplied by the toolchain, it does still need to be able to find the compiler-specific header file

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Was just working with the latest 3.54, and find that the Makefile in the menu directory didn't work until I added the /include/syslinux to the file. < CFLAGS = $(M32) -mregparm=3 -DREGPARM=3 -W -Wall - march=i386 -Os -fomit-frame-pointer -I$(LUDIR)/include - I$(COM32DIR)/include -I$(COM32DIR)/include/syslinux -Ilibmenu - D__COM32__ -

Hi folks, attached you can find a tiny patch for klibc-0.198 to get rid of the symbolic link pointing to the kernel sources, and to get rid of some obsolete rebuilds during incremental. Feel free to include it. Regards Harri -------------- next part -------------- diff -ur old/klibc-0.198/MCONFIG klibc-0.198/MCONFIG --- old/klibc-0.198/MCONFIG 2004-10-14 06:32:24.000000000 +0200 +++

I have, hopefully, found and fixed the issue with non-kernel binaries that appeared in 3.35. As a result, I have pushed out 3.36-pre6 and am classifying it as a release candidate. Please try it out, especially if you have had problems with 3.35. ftp://ftp.kernel.org/pub/linux/utils/boot/syslinux/Testing/ -hpa

Thank you all. It looks like -mno-red-zone flag is already in master branch since commit 7d70885d, but it seems it is applied to all EFI builds. IIUC, the problem only affects efi64 builds. So here's the modification of my patch to only apply -mno-red-zone flag to efi64 target. The patch is against master. I verified that it builds correctly in master. Please feel free to accept or reject