similar to: No rule to make target `efi32/com32/lib/memcmp.o', needed by `syslinux.so'.

Op 2014-06-12 om 06:43 schreef Geert Stappers: > Op 2014-06-10 om 22:55 schreef Geert Stappers: > > > > Hello, > > > > A `make efi32` yeilds me > > > > make[3]: *** No rule to make target `efi32/com32/lib/memcmp.o', needed by `syslinux.so'. Stop. > > make[3]: Leaving directory `efi32/efi' > > make[2]: *** [efi] Error 2 >

Op 2014-06-10 om 22:55 schreef Geert Stappers: > > Hello, > > A `make efi32` yeilds me > > make[3]: *** No rule to make target `efi32/com32/lib/memcmp.o', needed by `syslinux.so'. Stop. > make[3]: Leaving directory `efi32/efi' > make[2]: *** [efi] Error 2 It was encountered while doing `make`. The `make efi32` is just to faster reproduce the build

Op 2014-08-01 om 20:35 schreef Ady: > Goal: To have one USB drive capable of booting UEFI IA32 and UEFI X64 > (with an optional Syslinux menu containing multiple entries). What I would like to have is the same thing for network boot. So having one topdirectory on the TFTP server that can serve several "architectures". > Problem (solved) #1: The default directory location for

On Mon, Dec 22, 2014 at 12:18:56AM +0100, Geert Stappers wrote: > On Sun, Dec 21, 2014 at 12:21:32PM -0800, Patrick Masotta wrote: > > sudo apt-get install build-essential > > sudo apt-get build-dep gcc-multilib > > sudo apt-get install gcc-multilib nasm uuid-dev > > > > $ make spotless > > $ make > > > > but it consistently fails at > >

On Sun, Dec 21, 2014 at 12:21:32PM -0800, Patrick Masotta wrote: > sudo apt-get install build-essential > sudo apt-get build-dep gcc-multilib > sudo apt-get install gcc-multilib > > sudo apt-get install nasm > sudo apt-get install uuid-dev > > I run > #make spotless > #make > > but it consistently fails at > > make[3]: Entering directory

sudo apt-get install build-essential sudo apt-get build-dep gcc-multilib sudo apt-get install gcc-multilib sudo apt-get install nasm sudo apt-get install uuid-dev I run #make spotless #make but it consistently fails at make[3]: Entering directory `/syslinux-6.03/efi32/efi' Building gnu-efi for ia32 /syslinux-6.03/efi/check-gnu-efi.sh ia32 /syslinux-6.03/efi32 Failed to build gnu-efi.

On 10/26/2015 1:46 PM, Geert Stappers via Syslinux wrote: > On Mon, Oct 26, 2015 at 12:09:40PM -0600, Alan Sparks via Syslinux wrote: >> I'm still trying fruitlessly to get some sort of local disk boot from >> syslinux EFI to work... using the 6.03 modules. Tried various >> combinations of configurations on Gene's test binaries. > > The test binariers Gene

On Sat, Oct 10, 2015 at 03:10:26PM +0300, Ady via Syslinux wrote: > From: Geert Stappers <stappers at nero.gpm.stappers.nl> > > > > com32/mboot/map.c: removed trailing spaces > > > > They were introduced by the patch for ELF64 support. > > > IMHO, the trivial trailing-space cleanup could be included in the same > commit too, instead of adding an

From: Geert Stappers <stappers at nero.gpm.stappers.nl> They were introduced by the patch for ELF64 support. --- com32/mboot/map.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/com32/mboot/map.c b/com32/mboot/map.c index 2e8641f..1992f14 100644 --- a/com32/mboot/map.c +++ b/com32/mboot/map.c @@ -281,7 +281,7 @@ struct multiboot_header *map_image(void *ptr, size_t

On Sun, Sep 20, 2015 at 8:33 AM, syslinux-bot for Gene Cumm <gene.cumm at gmail.com> wrote: > Commit-ID: e0ac1d2fdf7d7c58457f3796a12561cce95ca29f > Gitweb: http://www.syslinux.org/commit/e0ac1d2fdf7d7c58457f3796a12561cce95ca29f > Author: Gene Cumm <gene.cumm at gmail.com> > AuthorDate: Sun, 20 Sep 2015 08:30:55 -0400 > Committer: Gene Cumm <gene.cumm at

Goal: To have one USB drive capable of booting UEFI IA32 and UEFI X64 (with an optional Syslinux menu containing multiple entries). Problem (solved) #1: The default directory location for both syslinux.efi is the same. Solution #1: Rename each syslinux.efi to bootx64.efi and to bootia32.efi. Problem (solved) #2: Each syslinux.efi needs at least its respective ldlinux module. Solution #2:

On Mon, Dec 29, 2014 at 8:36 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Mon, Dec 29, 2014 at 3:39 PM, Michael Sumulong <msumulong at gmail.com> > wrote: > > Hi, > > > > In efi/build-gnu-efi.sh, there's a "git submodule update --init" command > > which is causing a compilation issue on my build. I currently build in an > >

I'm currently using Microsoft DHCP to enable PXE booting. I've set options 66 and 67 for the relevant scopes and it's all fine and dandy. However, UEFI machines won't initiate PXE boot, they don't seem to recognize the options. Is there another setting that need to be set? And how to I filter UEFI clients so I set option 67 to the right value (lpxelinux.efi)? -- Alexandre

Dear Syslinux developers, I'd like to continue the discussion about this: http://www.syslinux.org/archives/2014-February/021659.html i.e. different directories for *.c32 files of BIOS, EFI32, and EFI64. I am wondering why we can not have *.c32 for the COMBOOT files of BIOS, *.e32 for the COMBOOT files of EFI32 *.e64 for the COMBOOT files of EFI64 As now the ldlinux file of syslinux 6.0x has,

> On Sun, Dec 21, 2014 at 12:21:32PM -0800, Patrick Masotta wrote: > > sudo apt-get install build-essential > > sudo apt-get build-dep gcc-multilib > > sudo apt-get install gcc-multilib > > > > sudo apt-get install nasm > > sudo apt-get install uuid-dev > > > > I run > > #make spotless > > #make > > > > but it

On Thu, May 12, 2016 at 06:16:46PM +0200, Good Old Idea via Syslinux wrote: > On Thu, May 12, 2016 at 02:29:52PM +0000, Janz, Burt via Syslinux wrote: > > I have a need to display text to COM2 before loading a kernel. > > The easiest way to do this was to invade menu.c32 (menumain.c) and > > add a function to send the string out to the serial port just before > > the

On Tue, Dec 30, 2014 at 09:34:57AM -0500, Michael Sumulong wrote: > On Mon, Dec 29, 2014 at 8:36 PM, Gene Cumm wrote: > > On Mon, Dec 29, 2014 at 3:39 PM, Michael Sumulong wrote: > > > Hi, > > > > > > In efi/build-gnu-efi.sh, there's a "git submodule update --init" command > > > which is causing a compilation issue on my build. I currently

Hello, i would like create a bootdisk , that can be boot from Old BIOS, EFI32 and EFI64. But for EFI Boot there is only one directory /EFI/BOOT/ In this directory I can copy BOOTia32.EFI and BOOTx64.EFI. But the *.c32 files for EFI32 & EFI64 , I can install to this directory at the same time. Is there a way to load the *.c32 from different directory ? Or is there a other solution ?

Gene Cumm wrote: > On Sun, Aug 4, 2013 at 5:24 PM, Dash Four <mr.dash.four at googlemail.com> wrote: > >> Is there a way I could build this package for ARM (Raspberry Pi)? >> >> I am using Pidora (Fedora mix for rpi), but can't find the source for this >> package in any of their repos >> (http://pidora.ca/pidora/releases/18/packages/source/SRPMS/s/)

On Sat, Jun 8, 2013 at 1:44 AM, Geert Stappers <stappers at stappers.nl> wrote: > Op 2013-06-07 om 12:20 schreef upen: > > On Fri, Jun 7, 2013 at 9:29 AM, Geert Stappers <stappers at stappers.nl> > wrote: > > > Op 2013-06-07 om 06:18 schreef upen: > > > > [ ... dhcp server configuration ... ] > > > > Everything has been always like this on