search for: syslinux

Hi Shao, On 2016.02.24 23:43, Shao Miller via Syslinux wrote: > Did you happen to notice anything unusual when compiling with MinGW > under Linux, once 'ok' was removed? I seem to recall warnings about > unused results, but not of unused objects. Maybe that's an incorrect > recollection or maybe it's ancient history, howev...

Hi, Matt Fleming wrote: > 'make efi64' will build just for x86-64. Likewise, 'make efi32' will > build just for i386. You can combine these, so to build BIOS and efi64 > you'd do, > > make bios efi64 'make efi64' failed with: ld -T /tmp/syslinux/efi/x86_64/syslinux.ld -Bsymbolic -pie -nostdlib -znocombreloc -L/usr/lib64 --hash-style=gnu -m elf_x86_64 /usr/lib64/crt0-efi-x86_64.o -E --strip-debug -o syslinux.so mem.o adv.o pxe.o fio.o console.o main.o derivative.o vesa.o diskio.o udp.o tcp.o /tmp/syslinux/efi64/core/codepage.o /tmp/syslinux...

...> What crash are you seeing? > > > >> I don't have the ia64 files which are needed for a complete binary. But > >> maybe that's only my special problem. > > > > You shouldn't need ia64 files to build ia32 and x86-64 versions of > > gnu-efi or Syslinux. > > Just to clarify: > > On a x86_64 system with gnu-efi 3.0u I checked out tag > "syslinux-6.01-pre5" and just run "make". It failed with > > make[3]: Entering directory `/tmp/sysl/syslinux/efi32/efi' > /tmp/sysl/syslinux/mk/efi.mk:27: *** Mi...

Matt Fleming <matt at console-pimps.org> writes: > Please do test out the release and report any regressions. Unfortunately, I can't make it under Debian wheezy + experimental gnu-efi (ie. 3.0u+debian-1): $ make installer [...] make[3]: Entering directory `/home/wferi/syslinux/syslinux-6.00/efi32/efi' gcc -I/usr/include/efi -I/usr/include/efi/ia32 -DEFI_FUNCTION_WRAPPER -fPIC -fshort-wchar -ffreestanding -Wall -I/home/wferi/syslinux/syslinux-6.00/com32/include -I/home/wferi/syslinux/syslinux-6.00/com32/include/sys -I/home/wferi/syslinux/syslinux-6.00/core/include -I/...

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 >> mboot.c32 >> menu.c32 >> syslinux.cfg >> vesamenu.c32 >> KS.CFG (vmware specific) >> BOOT.CFG (vmware specific) >> autoselect....

--- tests/syslinux/test-syslinux.pl | 21 ++++++++++++++------- 1 file changed, 14 insertions(+), 7 deletions(-) diff --git a/tests/syslinux/test-syslinux.pl b/tests/syslinux/test-syslinux.pl index d86c095..8a227d4 100755 --- a/tests/syslinux/test-syslinux.pl +++ b/tests/syslinux/test-syslinux.pl @@ -29,13 +29,20 @@...

I've been working with Matt Burgess here on this problem, and have found the following: syslinux 3.08-pre10 ? broken >>> config.inc:max_cmd_len=255 syslinux 3.08-pre11 ? works >>> config.inc:max_cmd_len=1023 syslinux 3.08 ? works >>> config.inc:max_cmd_len=1023 syslinux 3.09-pre1 ? works >>> config.inc:max_cmd_len=1023 syslinux 3.09-pre2 ? broken (repeat...

...e the destination of the redirection as it would be expected (at least, IMHO). http://git.zytor.com/?o=descr http://git.zytor.com/?s=desc http://git.zytor.com/?o=owner http://git.zytor.com/?s=owner http://git.zytor.com/?o=age http://git.zytor.com/?s=idle Heads: http://git.zytor.com/?p=syslinux/syslinux.git;a=heads http://git.zytor.com/syslinux/syslinux.git/refs/heads The redirection of "shortlog" works as expected: http://git.zytor.com/?p=syslinux/syslinux.git;a=shortlog http://git.zytor.com/syslinux/syslinux.git/log/ but the redirection of a "log" (as in gitweb...

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) > > > BOOTX64.EFI (from efi64/efi/syslinux.efi) > &g...

...#!/bin/sh. Again I wonder what's the point of it, as the script exits right after the popd, and it is not sourced but executed, so the current working directory is discarded anyway. * make spotless still fails after working around the above: [...] make -r -C efi SRC="/home/wferi/syslinux/syslinux/efi" OBJ="/home/wferi/syslinux/syslinux/efi32/efi" \ -f /home/wferi/syslinux/syslinux/efi/Makefile spotless In file included from /usr/include/elf.h:24:0, from reloc_ia32.c:39: /usr/include/features.h:323:26: fatal error: bits/predefs.h: No such fi...

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

On Mon, Dec 3, 2018 at 10:02 AM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > Now it is just dd, mkfs and copy in the files we need. > > One less thing to worry about keeping versions consistent. > > > > > > I just noticed those 2 files that were added by > > > > syslinux -i boot.img >...

Gene Cumm <gene.cumm at gmail.com> writes: > Could you try gnuefi-script-for-wferi-test branch on my repos at > > git://git.zytor.com/users/genec/syslinux.git > git://github.com/geneC/syslinux.git > > These changes fixed my issues (aside from the concurrency issue which > 2-3 passes solves for me). Now this shows me something I haven't ever seen. Build continuing in the background after the main process exits? wferi at lant:~/sys...

Hi all, I have just released syslinux-3.70-pre25. Unless someone has something big and scary that either I have managed to miss or was just stumbled over, I'm going to release 3.70 final some time between tomorrow and Monday. Thus, *please holler now* if there are any stop-ship problems still known... -hpa

I am looking for guides on how to create syslinux uefi bootable usb. A syslinux bootable usb is created already with vesamenu and luascripting. Want to set up the same thing to be UEFI compatible. In this case I am booting an vmware esxi installer. /EFI/boot on the vmware ISO has the files?BOOTX64.EFI and?BOOTIA32.EFI that can be used on the usb....

...lt;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 the above: >>>> [...] >>>> make -r -C efi SRC="/home/wferi/syslinux/syslinux/efi" OBJ="/home/wferi/syslinux/syslinux/efi32/efi" \ >>>> -f /home/wferi/syslinux/syslinux/efi/Makefile spotless >>>> In file included from /usr/include/elf.h:24:0, >>>> from reloc_ia32.c:39: >>&g...

...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 > > > mboot.c32 > > > menu.c32 > > > syslinux.cfg > > > vesamenu.c32 > > > KS.CFG (vmware specific) > >...

Trying to set up UEFI Syslinux boot on an ArchLinux USB 4GB stick. - Host system: 64-bit Ubuntu 14.10 on 56 GB hard drive - Hardware: ASUS P8H77-I, Bios v1101, i7-3770 at 3.40 GHz, 16 GB DDR3 - ArchLinux Instructions followed: https://wiki.archlinux.org/index.php/Syslinux#UEFI_Systems > ? ? 2. UEFI Systems > 2.2 Instal...

I recognize hardware with Lua and execute the ESXi installer with configuration files for that hardware. This works fine with normal Syslinux boot, but I want to get it working for UEFI boot as well. I found?efi64/efi/syslinux.efi and efi32/efi/syslinux.efi in the installer source, copied them and named them respectively?BOOTX64.EFI and?BOOTIA32.EFI in USBDISK:\EFI\BOOT. These were also the original names that the ESXi installer uses fo...

I made several attepmts using the tree of 5.01 2013. My syslinux.cfg file has display /path_to/syslinux.cfg directive. 1. The installation, with a --directory option, was successful. After boot I got syslinux boot prompt. The syslinux.cfg was not displayed. I guess that means the MBR was there, but not the partition boot sector. Then I notice...