search for: gccwarn

On 05-08-15 15:28, Gene Cumm wrote: >>> 0x2f8 is a BIOSism. > >> Is this a problem? The example in the comments said 0x3f8 which is COM1. > > It means that a BIOS IO port for a UART won't work for EFI. No value > for DEBUG_PORT will do anything unless someone's got some translation > "glue" to take the attempts to open the UART and use an EFI handle

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

This patch adds support for printing messages through a debug console. QEMU, for example, supports this through the debugcon facility. The benefit is that it's *much* faster than printing over a serial port. To print to I/O port 0x402 (the default used by SeaBIOS and OVMF), add "-DDEBUG_IO_PORT=0x402 -DCORE_DEBUG=1" to the build CFLAGS. To enable a debug console in QEMU that

On 05-08-15 12:05, Gene Cumm wrote: > > I recompiled with this in mk/devel.mk <http://devel.mk>: > > GCCWARN += -DDEBUG_PORT=0x2f8 -DCORE_DEBUG=1 > > 0x2f8 is a BIOSism. Is this a problem? The example in the comments said 0x3f8 which is COM1.

...x.mk | 4 ++-- >> 1 file changed, 2 insertions(+), 2 deletions(-) >> >> diff --git a/mk/syslinux.mk b/mk/syslinux.mk >> index 337560b..9ca74b1 100644 >> --- a/mk/syslinux.mk >> +++ b/mk/syslinux.mk >> @@ -82,11 +82,11 @@ ARCH ?= $(strip $(SUBARCH)) >> GCCWARN = -W -Wall -Wstrict-prototypes $(DEBUGOPT) >> >> # Common stanza to make gcc generate .*.d dependency files >> -MAKEDEPS = -Wp,-MT,$@,-MD,$(dir $@).$(notdir $@).d >> +MAKEDEPS = -MT $@ -MD >> >> # Dependencies that exclude system headers; use whenever we use &...

...Signed-off-by: Khem Raj <raj.khem at gmail.com> --- mk/syslinux.mk | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/mk/syslinux.mk b/mk/syslinux.mk index 337560b..9ca74b1 100644 --- a/mk/syslinux.mk +++ b/mk/syslinux.mk @@ -82,11 +82,11 @@ ARCH ?= $(strip $(SUBARCH)) GCCWARN = -W -Wall -Wstrict-prototypes $(DEBUGOPT) # Common stanza to make gcc generate .*.d dependency files -MAKEDEPS = -Wp,-MT,$@,-MD,$(dir $@).$(notdir $@).d +MAKEDEPS = -MT $@ -MD # Dependencies that exclude system headers; use whenever we use # header files from the platform. -UMAKEDEPS = -Wp...

...r > normal use (mixing gets ugly) and a special build must be made by > changing mk/devel.mk (although it's been a while). Lines 3 and 4 must > be uncommented and line 5 must be commented out. Booting such a build > may take a long time while data is pumped over the serial. > GCCWARN += -DDEBUG_MALLOC GCCWARN += -DDEBUG_PORT=0x3f8 -DCORE_DEBUG=1 These directives have made it unnecessary: - switch to 'isolinux-debug.bin' usage - engage "serial 0" within the 'isolinux.cfg' To put it another way, the effect is the same. > Although perhaps not helpf...

...at greenbone.net> --- utils/Makefile | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/utils/Makefile b/utils/Makefile index dfe6259..f31f117 100644 --- a/utils/Makefile +++ b/utils/Makefile @@ -17,8 +17,9 @@ VPATH = $(SRC) include $(MAKEDIR)/syslinux.mk -CFLAGS = $(GCCWARN) -Os -fomit-frame-pointer -D_FILE_OFFSET_BITS=64 -I$(SRC) -LDFLAGS = -O2 +CC = $(CC_FOR_BUILD) +CFLAGS = $(CFLAGS_FOR_BUILD) $(GCCWARN) -Os -fomit-frame-pointer -D_FILE_OFFSET_BITS=64 -I$(SRC) +LDFLAGS = $(LDFLAGS_FOR_BUILD) -O2 C_TARGETS = isohybrid gethostip memdiskfind SCRIPT_TARG...

...s/Makefile 2016-03-05 10:34:14.235228580 +0100 @@ -1,7 +1,7 @@ include $(MAKEDIR)/syslinux.mk OPTFLAGS = -g -Os -INCLUDES = -I$(SRC) -I$(objdir) -I$(SRC)/../libfat -I$(SRC)/../libinstaller +INCLUDES = -I$(SRC) -I$(objdir) -I$(SRC)/../bios -I$(SRC)/../libfat -I$(SRC)/../libinstaller CFLAGS = $(GCCWARN) -D_FILE_OFFSET_BITS=64 $(OPTFLAGS) $(INCLUDES) LDFLAGS = --- syslinux-6.04-pre1-BROKEN/linux/Makefile.ORIG 2016-03-04 17:17:12.586189283 +0100 +++ syslinux-6.04-pre1-BROKEN/linux/Makefile 2016-03-04 17:17:44.866281543 +0100 @@ -17,7 +17,7 @@ include $(MAKEDIR)/syslinux.mk OPTFLAGS = -g -O...

...$(LIBDIR)/elf_$(EFI_SUBARCH)_efi.lds LDFLAGS = -T $(SRC)/$(ARCH)/syslinux.ld -Bsymbolic -pie -nostdlib -znocombreloc \ - -L$(LIBDIR) --hash-style=gnu -m elf_$(ARCH) $(CRT0) -E + -znoseparate-code -L$(LIBDIR) --hash-style=gnu -m elf_$(ARCH) \ + $(CRT0) -E SFLAGS = $(GCCOPT) $(GCCWARN) $(ARCHOPT) \ -fomit-frame-pointer -D__COM32__ -D__FIRMWARE_$(FIRMWARE)__ \

...86-64 + ARCHOPT += -mno-red-zone EFI_SUBARCH = $(ARCH) endif @@ -29,7 +32,7 @@ -I$(core)/include -I$(core)/ $(ARCHOPT) \ -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 @@...

Hi together, this is the second version of my cross-compilation patch serie. I'm sending it in the hope to get an honest review, and possibly see the patches integrated upstream. Those patches allow to build syslinux using a toolchain different from the host one by explicitely using the host toolchain for the utilities that are required at build-time / on the build machine. I am using the

On 6/6/19 8:16 AM, Ady Ady via Syslinux wrote: > >> the PXELINUX log line is >> printed (PXELINUX 6.04 lwIP 6.04-pre3 Copyright (C) 1994-2015 H. Peter >> Anvin et al), > > (snip) > > FWIW, the official binaries from 6.04-pre2 and 6.04-pre3 are not good > for troubleshooting. > > Is the same behavior present when testing with other versions? I would

...+ ARCHOPT = -mno-red-zone +endif EFI_SUBARCH = $(ARCH) endif @@ -29,7 +32,7 @@ -I$(core)/include -I$(core)/ $(ARCHOPT) \ -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...

On Tue, Jun 30, 2015 at 4:29 PM, poma <pomidorabelisima at gmail.com> wrote: > "A real serial port that can reliably operate at 115200 8n1 may be > necessary." > > Gene, is there something special in "A real serial port" usage, compared to emulated? I should restate: A serial port that responds on BIOS IO port 3F8h that can reliably operate at 115200 8n1 may

...uno 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: > GCCWARN += -Wno-clobbered -DCORE_DEBUG=1 -DDEBUG_MALLOC -DDEBUG_THREAD > And removing the -DDYNAMIC_DEBUG but now syslinux doesn't want to build: MALLOC and THREAD are two debugs you probably don't want. If you can capture the serial port and the firmware would allow it, "-DDEBUG_PORT=0x3...

...ant to hook something to COM1 as I have to order some hardware for that, but this also works very well. A pity I didn't think of using it earlier. Still miss the printf output, though, so error messages from the shared code don't reach the user. I recompiled with this in mk/devel.mk: GCCWARN += -DDEBUG_PORT=0x2f8 -DCORE_DEBUG=1 And used ipmi_console to capture the output. Another way is to use the vsp command in the ILO4 shell. For future reference. > Any suggestions while I keep on debugging? Got some result! I was using 'vesamenu.c32' to display a menu. Changing this...

Hello Geert Thanks for replying.. But i think i can?t use it, as i don?t reach the point where the debug module will be available.. it just pulls the lpxelinux.0 and tries to get the next download-- the ldlinux.c32 and it fails...and freezes. And the next step would be other modules i think.. if i?m wrong.. excuse me 8-).. yesterday i managed to get ipxelinux working from ipxe.org.. so the nic

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

Hi there, I've had issue with the integration of syslinux into the buildroot project [0]. After some research, it turned out that we were wrongly using the host toolchain instead of the target toolchain to build syslinux. This gave us bigger issues (for instance) when trying to link syslinux with gnu-efi, that was built using the target toolchain. The first one forces ld to output i386