search for: dldlinux

...me/wferi/syslinux/syslinux-6.00/core/ -m32 -march=i386 -I/home/wferi/syslinux/syslinux-6.00/com32/lib/ -I/home/wferi/syslinux/syslinux-6.00/com32/libutil/include -std=gnu99 -DELF_DEBUG -DSYSLINUX_EFI -I/home/wferi/syslinux/syslinux-6.00/efi32 -W -Wall -Wstrict-prototypes -D__COM32__ -mno-red-zone -DLDLINUX=\"ldlinux.e32\" -fvisibility=hidden -Wno-unused-parameter -c -o adv.o /home/wferi/syslinux/syslinux-6.00/efi/adv.c In file included from /usr/include/efi/efi.h:45:0, from /home/wferi/syslinux/syslinux-6.00/efi/efi.h:22, from /home/wferi/syslinux/syslinux-...

...) \ -I$(com32)/lib/ -I$(com32)/libutil/include -std=gnu99 \ -DELF_DEBUG -DSYSLINUX_EFI -I$(objdir) \ - $(GCCWARN) -D__COM32__ -D__FIRMWARE_$(FIRMWARE)__ -mno-red-zone \ + $(GCCWARN) -D__COM32__ -D__FIRMWARE_$(FIRMWARE)__ \ -DLDLINUX=\"$(LDLINUX)\" -fvisibility=hidden \ -Wno-unused-parameter $(GCCOPT) --- syslinux.orig/mk/elf.mk +++ syslinux/mk/elf.mk @@ -27,6 +27,9 @@ ifeq ($(ARCH),x86_64) GCCOPT += $(call gcc_ok,-m64,) GCCOPT += $(call gcc_ok,-march=x86-64) +ifeq ($(FWCLASS),EFI) +...

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

...x-6.00/com32/include/sys -I/tmp/syslinux-6.00/core/include -I/tmp/syslinux-6.00/core/ -m32 -march=i386 -I/tmp/syslinux-6.00/com32/lib/ -I/tmp/syslinux-6.00/com32/libutil/include -std=gnu99 -DELF_DEBUG -DSYSLINUX_EFI -I/tmp/syslinux-6.00/efi32 -W -Wall -Wstrict-prototypes -D__COM32__ -mno-red-zone -DLDLINUX=\"ldlinux.e32\" -fvisibility=hidden -Wno-unused-parameter -c -o mem.o /tmp/syslinux-6.00/efi/mem.c In file included from /usr/include/efi/efi.h:45:0, from /tmp/syslinux-6.00/efi/efi.h:22, from /tmp/syslinux-6.00/efi/mem.c:3: /usr/include/efi/efiapi.h:663:...

...me/wferi/syslinux/genec/core/ -m32 -march=i386 -I/home/wferi/syslinux/genec/com32/lib/ -I/home/wferi/syslinux/genec/com32/libutil/include -std=gnu99 -DELF_DEBUG -DSYSLINUX_EFI -I/home/wferi/syslinux/genec/efi32 -W -Wall -Wstrict-prototypes -Wno-clobbered -DDYNAMIC_DEBUG -D__COM32__ -mno-red-zone -DLDLINUX=\"ldlinux.e32\" -fvisibility=hidden -Wno-unused-parameter -Wno-strict-prototypes -DDATE_STR='"4.03-pre3-2126-g73d08a5"' -c -o adv.o /home/wferi/syslinux/genec/efi/adv.c In file included from /home/wferi/syslinux/genec/efi/adv.h:4:0, from /home/wferi/sysl...

...-I/root/syslinux/core/include -I/root/syslinux/com32/include -I/root/syslinux/com32/include/sys -I/root/syslinux/com32/lib -I/root/syslinux/core/lwip/src/include -I/root/syslinux/core/lwip/src/include/ipv4 -I/root/syslinux/core/fs/pxe -D__SYSLINUX_CORE__ -D__FIRMWARE_BIOS__ -I/root/syslinux/bios -DLDLINUX=\"ldlinux.c32\" -c -o kaboom.o /root/syslinux/core/kaboom.c So the CORE_DEBUG option is passed, and in the code I see: #if defined(CORE_DEBUG) || defined(DEBUG_PORT) #include <dprintf.h> __export __noreturn __bad_SEG(const volatile void *p) { dprintf("SEG() passed an in...

Finally, the Syslinux 6.00 release is out. This release includes support for booting from EFI, both from disk-based media and over the network via PXE. Thanks to everyone who has been testing this out. There are some EFI bugs that I'm aware of, * booting Linux kernels without CONFIG_RELOCATABLE doesn't work * 64-bit syslinux.efi cannot boot 32-bit kernels and vice versa *

.../include -I/tmp/syslinux-6.04-pre1/com32/include/sys -I/tmp/syslinux-6.04-pre1/com32/lib -I/tmp/syslinux-6.04-pre1/core/lwip/src/include -I/tmp/syslinux-6.04-pre1/core/lwip/src/include/ipv4 -I/tmp/syslinux-6.04-pre1/core/fs/pxe -D__SYSLINUX_CORE__ -D__FIRMWARE_BIOS__ -I/tmp/syslinux-6.04-pre1/bios -DLDLINUX=\"ldlinux.c32\" -c -o fs/pxe/tcp.o /tmp/syslinux-6.04-pre1/core/fs/pxe/tcp.c nasm -f elf -Ox -g -F dwarf -DDATE_STR="''" \ -DHEXDATE="0x56dc3c62" \ -Di386 \ -I/tmp/syslinux-6.04-pre1/core/ \ -l ldlinux.lsr -o ldlinux.o -MP -MD ./.ldlinux.o.d /tmp/syslinux-...

...lude -I/home/voltagex/src/syslinux/core/ -m64 -march=x86-64 -I/home/voltagex/src/syslinux/com32/lib/ -I/home/voltagex/src/syslinux/com32/libutil/include -std=gnu99 -DELF_DEBUG -DSYSLINUX_EFI -I/home/voltagex/src/syslinux/efi64 -W -Wall -Wstrict-prototypes -Wno-clobbered -D__COM32__ -mno-red-zone -DLDLINUX=\"ldlinux.e64\" -c -o mem.o /home/voltagex/src/syslinux/efi/mem.c In file included from /usr/include/efi/efi.h:45:0, from /home/voltagex/src/syslinux/efi/efi.h:22, from /home/voltagex/src/syslinux/efi/mem.c:2: /usr/include/efi/efiapi.h:663:5: warning: fun...

When we add -ffreestanding the compiler won't get to inline this any more. Signed-off-by: David Woodhouse <dwmw2 at infradead.org> --- com32/lib/math/fabs.S | 15 +++++++++++++++ mk/lib.mk | 2 +- 2 files changed, 16 insertions(+), 1 deletion(-) create mode 100644 com32/lib/math/fabs.S diff --git a/com32/lib/math/fabs.S b/com32/lib/math/fabs.S new file mode 100644 index

On Fri, Jan 10, 2014 at 2:53 AM, Ferenc Wagner <wferi at niif.hu> wrote: > Gene Cumm <gene.cumm at gmail.com> writes: > >> On Sat, Jan 4, 2014 at 6:39 AM, Gene Cumm <gene.cumm at gmail.com> wrote: >>> On Tue, Dec 17, 2013 at 8:39 AM, Ferenc Wagner <wferi at niif.hu> wrote: >>> >>>> * make spotless still fails after working around

...) \ -I$(com32)/lib/ -I$(com32)/libutil/include -std=gnu99 \ -DELF_DEBUG -DSYSLINUX_EFI -I$(objdir) \ - $(GCCWARN) -D__COM32__ -D__FIRMWARE_$(FIRMWARE)__ -mno-red-zone \ + $(GCCWARN) -D__COM32__ -D__FIRMWARE_$(FIRMWARE)__ \ -DLDLINUX=\"$(LDLINUX)\" -fvisibility=hidden \ -Wno-unused-parameter $(GCCOPT) --- syslinux-6.03-orig/mk/elf.mk +++ syslinux-6.03/mk/elf.mk @@ -27,6 +27,9 @@ ifeq ($(ARCH),x86_64) GCCOPT += $(call gcc_ok,-m64,) GCCOPT += $(call gcc_ok,-march=x86-64) +ifdef EFI_BUIL...

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:

After so much time and improvements, I'm glad to see and publicize a pre-release, 6.04-pre1 in https://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/6.04/ Personally, I've already been working testing the pre-release as-is and my tests have been positive so far. I appreciate feedback like that from Gabriele Balducci and testing "make bios installer". Yes, there are a

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,