Displaying 5 results from an estimated 5 matches for "installsubdir".
Did you mean:
installsubdirs
2013 Jun 24
0
Syslinux 6.00 released
...-
2 files changed, 1 insertion(+), 3 deletions(-)
diff --git a/Makefile b/Makefile
index 3861168..9c886d8 100644
--- a/Makefile
+++ b/Makefile
@@ -164,7 +164,7 @@ BOBJECTS = $(BTARGET) \
ifdef EFI_BUILD
BSUBDIRS = codepage com32 lzo core mbr sample efi txt
-ISUBDIRS = efi utils
+ISUBDIRS =
INSTALLSUBDIRS = efi
diff --git a/efi/Makefile b/efi/Makefile
index 2003430..c89ca06 100644
--- a/efi/Makefile
+++ b/efi/Makefile
@@ -66,8 +66,6 @@ codepage.o: ../codepage/cp865.cp
cp $(objdir)/../codepage/cp865.cp codepage.cp
$(CC) $(SFLAGS) -c -o $@ $(core)/codepage.S
-installer: syslinux.efi
-
instal...
2010 May 29
2
Syslinux doesn't compile on Mandriva Linux - fixed
...ux
INSTALL_AUX = core/pxelinux.0 gpxe/gpxelinux.0 core/isolinux.bin \
core/isolinux-debug.bin \
- dos/syslinux.com win32/syslinux.exe \
+ dos/syslinux.com $(INSTALL_AUX_OPT) \
mbr/*.bin $(MODULES)
-INSTALL_AUX_OPT = win32/syslinux.exe
# These directories manage their own installables
INSTALLSUBDIRS = com32 utils dosutil
2013 Jun 24
2
Syslinux 6.00 released
On Sat, 22 Jun, at 05:24:21PM, Ferenc Wagner wrote:
> 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]: *** No rule to make target
2012 Oct 19
3
[PATCH 0/3] elflink fixes
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
2015 Nov 27
8
[PATCH 0/2] Do not use the "red zone" on EFI
From: Sylvain Gault <sylvain.gault at gmail.com>
The System V ABI for x86-64 specify that a "red zone" is an area of 128 bytes
above the current stack frame. This area can be used by a called function in
order to avoid the overhead of modifying the stack pointer. The direct effect
is that interrupt/event/signal handlers must not write to this area. In the
UEFI calling convention,