search for: c_libs

From: Matt Fleming <matt.fleming at linux.intel.com> This series includes a patch (PATCH 1/6) that I sent previously but I thought it was worth sending it again since the rest of the series depends on it, and it also gives a bit of context. These cleanups make it simpler to do the big switchover to ELF modules on the elflink branch because the libraries in $LIBS are now contained in one

From: Matt Fleming <matt.fleming at intel.com> The first two patches in this series are fixes for bugs reported by someone in #syslinux. The third makes dmitest.c32 actually wait for user input. If no one has any objections/concerns, I'll pull this into the official elflink branch. Matt Fleming (3): core: Print error message if we don't load ldlinux.c32 Clean up $(GPLLIB) leak

...e prerequisite '/home/john/git/syslinux/efi64/com32/gpllib/libgpl.c32'. Trying rule prerequisite '/home/john/git/syslinux/efi64/com32/lib/libcom32.c32'. Looking at mk/elf.mk, you can trace the expansion from .c32 -> .elf -> .o -> .S -> .c, and then the expansion from $(C_LIBS) -> libutil.c32 libgpl.c32 libcom32.c32 -------------------------------------------------- GPLLIB = $(objdir)/com32/gpllib/libgpl.c32 <snip> C_LIBS += $(objdir)/com32/libutil/libutil.c32 $(GPLLIB) \ $(objdir)/com32/lib/libcom32.c32 .SUFFIXES: .lss .c .o .PRECIOUS: %.o %.o:...

...th the same flags as are used in the syslinux com32 module build. There is no error output during the link, you just end up with seemingly random run-time issues. This may partially depend upon #2, below. 2) The final link command line order is surprisingly fussy. "$(LD) $(LDFLAGS) -o $@ $^ $(C_LIBS)" builds a com32 module that runs pretty reliably. "$(LD) -o $@ $^ $(LDFLAGS) $(C_LIBS)" builds a com32 module that may or may not run depending upon how much and in what order your .c source code may be. Order of flags on the tool's command line matters? Looks like it. Weird. S...

...mingly random run-time issues. This may > > partially depend upon #2, below. > > > > This is very true. The Syslinux ABI is not compatible with any other ABI. > > > 2) The final link command line order is surprisingly fussy. "$(LD) > > $(LDFLAGS) -o $@ $^ $(C_LIBS)" builds a com32 module that runs pretty > > reliably. "$(LD) -o $@ $^ $(LDFLAGS) $(C_LIBS)" builds a com32 module > > that may or may not run depending upon how much and in what order your > > .c source code may be. Order of flags on the tool's command line &gt...

...end upon #2, below. > >> > > >> > >> This is very true. The Syslinux ABI is not compatible with any other > >ABI. > >> > >> > 2) The final link command line order is surprisingly fussy. "$(LD) > >> > $(LDFLAGS) -o $@ $^ $(C_LIBS)" builds a com32 module that runs > >pretty > >> > reliably. "$(LD) -o $@ $^ $(LDFLAGS) $(C_LIBS)" builds a com32 > >module > >> > that may or may not run depending upon how much and in what order > >your > >> > .c source code may...

...L_VERSION ?= $(shell uname -r) +MODULES_ALIAS_FILE ?= /lib/modules/$(KERNEL_VERSION)/modules.alias +MODULES_PCIMAP_FILE ?= /lib/modules/$(KERNEL_VERSION)/modules.pcimap +PCI_IDS_FILE ?= $(PWD)/floppy/pci.ids + all: $(MODULES) $(TESTFILES) hdt.elf : $(OBJS) $(LIBS) $(C_LIBS) @@ -39,9 +44,17 @@ rm -f *.lnx spotless: clean - rm -f *.lss *.c32 *.com + rm -f *.lss *.c32 *.com hdt.img rm -f *~ \#* install: -include .*.d + +hdt.img: hdt.c32 floppy/hdt.cfg $(topdir)/mtools/syslinux $(MODULES_ALIAS_FILE) $(MODULES_PCIMAP_FILE) $(PCI_IDS_FILE) floppy/m...

From: Matt Fleming <matt.fleming at linux.intel.com> This series fixes some bugs and switches the elflink branch to be entirely ELF modules. It applies on top of, http://syslinux.zytor.com/archives/2011-April/016369.html The deletions in the diff stat below are mainly from deleting com32/elflink/modules (finally!). Now there should be no duplicate code because we don't need COM32 and

From: Matt Fleming <matt.fleming at intel.com> The following patch series is available at, git://git.zytor.com/users/mfleming/syslinux.git elflink All patches are against the 'elflink' branch. This series fixes a few serious bugs and some behavioural incompatibilities with the 4.x series. Matt Fleming (19): ldlinux: Initialise 'p' before using it. ldlinux: Parse

...: + lfree(bounce); *size_found = count; } diff --git a/com32/hdt/Makefile b/com32/hdt/Makefile index 36206cd..ff0fa2e 100644 --- a/com32/hdt/Makefile +++ b/com32/hdt/Makefile @@ -20,6 +20,9 @@ MAKEDIR = $(topdir)/mk include $(MAKEDIR)/elf.mk LIBS = ../libupload/libcom32upload.a +C_LIBS += $(com32)/cmenu/libmenu/libmenu.c32 \ + $(com32)/libutil/libutil_com.c32 \ + $(com32)/lib/libcom32.c32 $(com32)/gpllib/libcom32gpl.c32 CFLAGS += -I$(com32)/cmenu/libmenu -I$(com32) MODULES = hdt.c32 diff --git a/com32/hdt/hdt-common.c b/com32/hdt/hdt-common.c index 8e9a9e6.....

1) code split and move Iterator related functionality is yanked from chain.c and moved to iterator.{c,h}. Both are moved to com32/chain and this way chain.c is ready for further splitting. Alternatively, partiter could be moved to com32/lib at any time in the future. It's potentially useful for other modules (e.g. if someone wanted to code partition dumper or editor). 2) Iterator updates

Hi, This series targets automatic boot menu generation, but most of it is the Lua upgrade, because I got tired reading deprecated API docs. It's mostly a straightforward forward port of the earlier Syslinux specific changes to Lua 5.1, except that: * I chose the add a stub getenv() implementation to the COM32 API instead of #ifdefing out all the references in Lua, and * I kept oslib