similar to: SYSLINUX 3.73-pre3

I have, hopefully, found and fixed the issue with non-kernel binaries that appeared in 3.35. As a result, I have pushed out 3.36-pre6 and am classifying it as a release candidate. Please try it out, especially if you have had problems with 3.35. ftp://ftp.kernel.org/pub/linux/utils/boot/syslinux/Testing/ -hpa

For the boot floppy at http://superkeen.com/peacecorpsfiles/FUZOMA14.IMG using memdisk from syslinux version 3.72 boots correctly, but for memdisk versions newer than 3.72 (I tested 3.73, 3.75, 3.85, and 3.86) all hang at boot with the following message: Loading boot sector... booting FreeDOS kernel - SVN (build 2039 OEM:0xfd [compiled Oct 2 2009]) Kernel compatibility 6.22 - BORLANDC ... XMGR,

HI: i just trying memdisk that comes with syslinux 3.35. i try to load a dos image, which contains ghost verison 8.3 and ghost version 11. both version of ghost hangs when start-up. memdisk that comes with 3.40 pre is ok. and many earlier versions is ok too. i try some parameter like "safeint","raw". but none work. i use memdisk with pxelinux, below is part of my

Well, it has to happen at some point, so I have officially pushed out SYSLINUX 3.72. The big news in this release is of course the ISOLINUX hybrid mode support (a single image which can be booted either from a CD-ROM or from a hard disk/USB stick), but there are plenty of more goodies in here, including the label listing (not technically completion) on the Tab key. As usual, huge thanks to

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Was just working with the latest 3.54, and find that the Makefile in the menu directory didn't work until I added the /include/syslinux to the file. < CFLAGS = $(M32) -mregparm=3 -DREGPARM=3 -W -Wall - march=i386 -Os -fomit-frame-pointer -I$(LUDIR)/include - I$(COM32DIR)/include -I$(COM32DIR)/include/syslinux -Ilibmenu - D__COM32__ -

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

> > C_ While initially thought to be a problem with the INCLUDE > > directive, now it seems the problem is the second parameter of the > > CONFIG directive. The second parameter of the CONFIG directive (which > > sets a new CWD) doesn't seem to work correctly (tested with pwd.c32), > > specially when the new cfg file (the first parameter of the CONFIG >

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

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

I'm new to memdisk and I wanted to have multiple floppy boot images on my USB key, I installed GRUB2 as the boot loader and have memdisk in /syslinux and my images in /image, I first tried booting normal images, memtest86+ works, my linux kernel work and they boot perfectly. Now using memdisk, I tried booting Spinrite which uses FreeDOS, it booted fine with no argument them frozen at querying

I'm not seeing how to set this path option? Here is what I get using vesamenu.c32 as an example when moved to a directory outside of the build. The current syslinux 4.06 has all the files in the same directory which is at the root of the cd. ldd vesamenu.c32 linux-gate.so.1 => (0xb77c5000) ../../com32/libutil/libutil_com.c32 => not found ../../com32/lib/libcom32.c32 => not found

Hi there, i just build a new ipxelinux.0 with an EMBED=../../syslinux-5/core/pxelinux.0. i'm trying to load up my vesamenu.c32 menu from http:. and offcorse i want this as optimal as possible, with the least needed GET requests. OLD situation with v4: PXE ROM -> ipxelinux.0 (tftp) -> menu.php (http) -> vesamenu.c32 (http) NEW situation with v5: PXE ROM -> ipxelinux.0 (tftp)

Hello all Tried hard to create a Boot Floppy using Syslinux-5.00 but NO success. I have Win98se installed on C: drive. Following is the Directory Structure on the floppy: ------------------------------------------------------------------- Volume in drive A has no label Volume Serial Number is 1115-0BEC Directory of A:\ LIBCOM32 C32 737,266 12-06-12 11:49a

Hello, I tried to make my own binary with 'make efi64 install' but it fail with make[3]: *** No rule to make target `/root/syslinux-6.02-pre3/efi64/efi/../core//writestr.o', needed by `syslinux.so'. Stop. make[3]: Leaving directory `/root/syslinux-6.02-pre3/efi64/efi' make[2]: *** [install] Error 2 make[2]: Leaving directory `/root/syslinux-6.02-pre3/efi64' make[1]: ***

Hi, We have been using isolinux 3.75 for a while now, to support pxelinux and UEFI we were going to update to 6.03, but seeing 6.04 has but fixes, decided to go with 6.04-pre3. First, is that about read for a "make official' ? Second, I did have to modify gnu-efi/inc/efilinks.h for the build to complete (had to remove the (intptr_t) which doesn't belong in EFI/EDK). So I've

Changes in 3.73: * Upgrade gPXE to release version 0.9.5. * Fix a number of build errors on various platforms. * Handle systems with E820 "extended attributes" per ACPI 3. Someone "cleverly" decided to change the E820 spec in a backwards-incompatible manner! * MEMDISK: default to "safeint". * Adopt the moniker "The Syslinux Project", standard

Hello, I just received a serious bug report from Stas Kysel of rPath (with a great test case); it appears that deleted files can confuse extlinux so that it misses files. This is bad. As a result, I have pushed out 3.63-pre3, and intend to make a 3.63 final shortly. I would appreciate any help testing this. Furthermore, I would like to finish the SDI booting module, but I have yet to

I think I botched syslinux-6.04-pre3. There are two fundamental problems with the build: a) The selection of what pieces of the library gets included in the core is done manually whereas it really should be automatic; b) The build doesn't fail if there are unresolved dependencies between the libraries and the core. I will fix these. (b) is IMO fundamental to avoid this error in the

As suggested, I have made a 6.04-pre3 release. In addition to updating gnu-efi to the latest version available (3.0.9 + a few patches) I wanted to make the tree compile with -Werror on my box, which resulted in pulling a thread which in turn caused a whole bunch of things to unravel :) The end result was that I ended up refactoring much of the tree so that it now avoids building a ton of