Displaying 5 results from an estimated 5 matches for "bsubdirs".
Did you mean:
subdirs
2012 Jan 27
1
[PATCH] [RFC] Makefile: add mingw objects conditionally
...e \
dosutil/*.com dosutil/*.sys \
$(MODULES)
+ifeq ($(shell win32/find-mingw32.sh gcc >/dev/null 2>&1 ; echo $$?), 0)
+BOBJECTS += win32/syslinux.exe
+endif
+ifeq ($(shell win64/find-mingw64.sh gcc >/dev/null 2>&1 ; echo $$?), 0)
+BOBJECTS += win64/syslinux64.exe
+endif
# BSUBDIRs build the on-target binary components.
# ISUBDIRs build the installer (host) components.
--
1.7.7.6
2006 May 03
1
syslinux gone?
I'm just curious. The older klibc tarballs had a syslinux dir used to
build a syslinux image with klibc. While I haven't used it, I was
planning on messing with it at some point in the future.
However, the syslinux stuff was removed from recent klibc images. Is
there a technical reson for this, or would is still be acceptable to
use the old Makefiles from that dir to build syslinux?
2013 Jun 24
0
Syslinux 6.00 released
...Matt Fleming <matt.fleming at intel.com>
---
Makefile | 2 +-
efi/Makefile | 2 --
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.c...
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
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,