similar to: cmenu.c32 Symbol not found luaL_checklstring

Reinier Kleipool via Syslinux <syslinux at zytor.com> writes: > But when I want to use cmenu.c32 (with UI cmenu.c32 in the config > file), the loader downloads: > * cmenu.c32 > * libmenu.c32 > * libcom32.c32 > * libutil.c32 > Then syslinux reports: "unable to load cmenu.c32: symbol not found > luaL_checklstring". > This sysbol is defined in

On Fri, 2012-06-29 at 07:42 -0700, syslinux-bot for H. Peter Anvin wrote: > elflink: fix dependency problem in cmenu/Makefile > > Instead of adding library dependencies implicitly, make them explicit > and use --as-needed to avoid bogus DT_NEEDED entries from being > generated. This is fine, but... > diff --git a/com32/cmenu/Makefile b/com32/cmenu/Makefile > index

Hello, I poked a little bit to extract the list of modules dependencies in Syslinux v6 (see below). I have attached a bash script that generate a nice table from the tarball. The output can either be an ASCII table, or wiki markup, typically for the page Library_modules[1]. I am not in the wiki Editor group, so I can't put that in the wiki. anyway, here's an updated dependency tree for

Testing Syslinux 6.03-pre13 in a BIOS 32-bit VM, boot: vesa.c32 Undef symbol FAIL: luaL_checklstring Failed to load COM32 file vesa.c32 boot: Is there a Lua-related issue? Is vesa.c32 expecting some kind of argument? TIA, Ady.

Hello All, This is my first time requesting help, so please bear with me. I don't upgrade Syslinux very often (only when the need arises), until now I have been using version 4.05. However, I have recently acquired several UEFI servers that are in need of being able to do OS installations via pxelinux. I have upgraded to Syslinux version 6.03, however I am not able to compile my custom

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

"H. Peter Anvin" <hpa at zytor.com> writes: > On 06/03/2014 02:59 AM, Ady wrote: > >> Testing Syslinux 6.03-pre13 in a BIOS 32-bit VM, >> boot: vesa.c32 >> Undef symbol FAIL: luaL_checklstring >> Failed to load COM32 file vesa.c32 >> boot: >> >> Is there a Lua-related issue? >> >> Is vesa.c32 expecting some kind of

From: Matt Fleming <matt.fleming at linux.intel.com> Don't link against libmenu.a, it no longer exists as it was removed in commit 74518b8b691c ("elflink: Make ELF the default object format"). This fixes the following build error, make[2]: *** No rule to make target `../cmenu/libmenu/libmenu.a', needed by `hdt.c32'. Stop. Signed-off-by: Matt Fleming

make[2]: *** No rule to make target `../cmenu/libmenu/libmenu.a', needed by `hdt.c32'. Stop. Sebastian

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

On Thu, Apr 21, 2016 at 6:39 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Thu, Apr 21, 2016 at 3:29 AM, Atle Holm <atle at team-holm.net> wrote: >> Under EFI/BOOT are the following files: >> BOOTIA32.EFI (from efi32/efi/syslinux.efi) >> BOOTX64.EFI (from efi64/efi/syslinux.efi) >> ldlinux.sys (copied from root of partition) >> lua.c32 >>

Hi, Yes, I'm back with this pet peeve of mine again. Most of the old cover letter at https://gist.github.com/wferi/6989458 still applies; I'd like to reiterate its last paragraph here, too: > And an official stat() implementation would be very useful. After > inventing mine, I noticed rosh also invented its own... Anyway, here it is: The following changes since commit

Hello, Is "Dos installer from Win98" REMOVED from Syslinux-5.00/syslinux-5.01-pre1? Prof S W Damle

On 3/5/2014 4:21 AM, Gene Cumm wrote: > tp. But I can't get it to work. > 5.10 introduced lpxelinux.0, a variant that uses UNDI+lwIP instead of PXE calls. Ah, ok, the wording in 5.10 change log is a little ambiguous then...It seems to imply (to me at least) that http support was added to pxelinux.0 with an old TCP stack, but lpxelinux.0 has http with a new TCP stack. > >>

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

On Sat, Dec 1, 2018 at 2:46 AM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > it works. (boots into the d-i installer, I don't care if the installer > > is missing stuff, booting it is all we care about here. > > > OK, so let's add complexity (but not the whole thing, not yet). > > We already have: > > target > ??? EFI > ? ???

> > Is this "ArchLinux" entry equivalent to "\EFI\syslinux\syslinux.efi" > > in your UEFI firmware? > > Note: UEFI firmware is supposed to use (or show) backslash "\" as path > > separator. > > You have a great point there. > I redid the "efibootmgr" installation and instead of > > efibootmgr -c -d /dev/sdd -p 1 -l

> "H. Peter Anvin" <hpa at zytor.com> writes: > > > On 06/03/2014 02:59 AM, Ady wrote: > > > >> Testing Syslinux 6.03-pre13 in a BIOS 32-bit VM, > >> boot: vesa.c32 > >> Undef symbol FAIL: luaL_checklstring > >> Failed to load COM32 file vesa.c32 > >> boot: > >> > >> Is there a Lua-related issue?

I am a developer from the 'Frugalware Linux' distribution. I have been trying to use the syslinux lua module to support more dynamic menu generation at runtime for our distributed ISO images, as Grub2 is not very configurable for this. For example, I need raw access to the PCI bus information to configure the video output kernel boot parameters for specific hardware. Specifically,

On Wed, Oct 30, 2013 at 09:52:57AM +0200, Ady wrote: > > > The wiki (http://www.syslinux.org/wiki/index.php/PXELINUX) still says: > > > > "copy pxelinux.0 (from the SYSLINUX distribution) and any > > kernel or initrd images that you want to boot" > > > > like I've been doing forever, but how do I know what else I need, and > >