similar to: cannot compile simple.c from within Syslinux 6.03

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 >>

Hello everyone, I am trying to PXE boot my Acer Aspire G3-773G laptop. It uses UEFI, so I load 64bit syslinux.efi (v6.03) and it automatically loads ldlinux.e64. All is fine. 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:

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 mboot.c32 menu.c32 syslinux.cfg vesamenu.c32 KS.CFG (vmware specific) BOOT.CFG (vmware specific) autoselect.lua These files are also all under the root of the partition (except BOOTIA32.EFI and BOOTX64.EFI) and work fine

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

Hi all, I'm building extlinux on a rather limited linux system (LFS), bios version (no efi). Unfortunately, extlinux.txt does not contain any information related to build procedures and dependencies. python /sources/syslinux-6.03pre11/com32/cmenu/menugen.py --input=/sources/syslinux-6.03pre11/com32/cmenu/test2.menu --output=test2.c

The following are new Lua c32 modules in 6.03-pre*: cmenu.c32: cpu.c32: dhcp.c32: dmi.c32: lfs.c32: pci.c32: syslinux.c32: vesa.c32: I am wondering whether the following modules, which are _not_ new and are also included in 6.03-pre*, have _any_ relation either to the above list or to Lua: cpuid.c32: cpuidtest.c32: dmitest.c32: pcitest.c32: vesainfo.c32: TIA, Ady.

I'm seeing some sporadic build failures with 'make -j4'. The failures are: make[4]: *** No rule to make target 'hello.c32', needed by 'all'. Stop. I've only seen the failures with com32/samples/hello.c32 and com32/rosh/rosh.c32. I'm not a make expert, but I think it's due to missing dependencies. This patch seems to fix my failures, but I'm

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

Hi all, wasnt sure whether this was the best place to put this information; but something seems to have gone 'backwards' in the later pre-releases of 6.03 regarding network booting. below are results of me testing - i did each a few times to make sure they are valid results. hope it helps identify something that's gone awry ? so far, 6.03 pre11 and pre13 (excluding efi32) seem most

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 > ? ???

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

> Den 21. april 2016 kl. 22.04.37 +02.00 skrev Gene Cumm <gene.cumm at gmail.com>: > > > 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: > >

Hi all - I'm not sure if it's appropriate to ask this here, but I don't see this question explicitly answered anywhere. Is there an EFI version of "pxelinux.0" that will function basically the same way and read the same pxelinux.cfg/default menu files? I've got a really dodgy grubx64.efi EFI PXE menu up at work, but it can't load the 1.2 gigabyte LiveCD that we use

I thought I've found three bugs on syslinux 6.03: (1) With sample config file as is, i.e. leaving commented MENU VSHIFT and MENU COLOR UNSEL but uncommented MENU COLOR SEL: A black "border" is displayed below the selected line and on its right edge. (2) Uncommenting MENU COLOR UNSEL: This effect appears also on separators and on right edge on every unselected lines. (3)

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

Patrick, Even more confusing. I downloaded the 6.03 syslinux tar and extracted all the files. It shows 3 pxechn versions, [root at localhost_PXENG ~]# cd /tmp/syslinux-6.03 [root at localhost_PXENG syslinux-6.03]# find . -name pxechn.c32 ./efi32/com32/modules/pxechn.c32 ./efi64/com32/modules/pxechn.c32 ./bios/com32/modules/pxechn.c32 Is it possible to pxechn to a BIOS pxelinux.0?

Den 21. april 2016 kl. 14.21.04 +02.00 skrev Geert Stappers <stappers at stappers.nl>: > On Thu, Apr 21, 2016 at 06:39:44AM -0400, Gene Cumm via Syslinux 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)

Den 21. april 2016 kl. 22.04.37 +02.00 skrev Gene Cumm <gene.cumm at gmail.com>: > 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

Hello syslinux maintainers, I came across the issue of syslinux crashing with some EFIs in the UEFI boot mode. Upon closer investigation it turned out that most object files which go into syslinux efi64 are compiled with the so-called red zone. Some EFIs follow Windows ABI more strictly and cause syslinux to crash due to stack overwrite. Looking at mk/efi.mk there was a previous attempt to fix

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