similar to: [PATCH] Makefile: Move Makefile fragments into mk/

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

I tend to use the same tool-chain across various hosts so I made this very simple patch that allows you to pass the cross-compiler name to make ( e.g. make CROSS_COMPILE=i686-nptl-linux-gnu-). I'm not sure if patches should be attached or just pasted inline so I did both this time. BTW, it's relative to syslinux 4 but the same changes work with syslinux 3 although the patch won't

On Mon, Sep 14, 2015 at 05:50:58AM +0200, celelibi--- via Syslinux wrote: > index a705440..5ef6702 100644 > --- a/mk/efi.mk > +++ b/mk/efi.mk > @@ -10,6 +10,7 @@ core = $(topdir)/core > GCCOPT := $(call gcc_ok,-fno-stack-protector,) > EFIINC = $(objdir)/include/efi > LIBDIR = $(objdir)/lib > +EFIDIR = $(topdir)/gnu-efi/gnu-efi-3.0 Would it make sense to add AROPT =

It has been observed that binaries contents are depending on the order of linked objects. This order is caused by GNU make's wildcard function and the position of sources on filesystem. This change tries to prevent this kind of randomness. Also consider building using -j1 flag to make it even more reproductible. Change-Id: Ie8eee7f336e6f1fa2863c4150d967afd15519f1d Bug:

This patch adds to Com32 modules the capabilities of accessing the EFI environment The idea is simple, the EFI parameters "image" and "table" received by syslinux.efi's efi_main() are stored in the "firmware" structure, next they are retrieved from the Com32 module which is linked against the gnu-efi static library. The Com32 module can use the EFI

From: Sylvain Gault <sylvain.gault at gmail.com> The error-prone shell scripts for building gnu-efi are replaced by a Makefile recipe. This is accompanied with a small update of gnu-efi which, despite not strongly mandatory, avoid recompiling gnu-efi and all the efi subtree on each invocation of make. Signed-off-by: Sylvain Gault <sylvain.gault at gmail.com> ---

Op 20100701 om 18:15 schreef syslinux-bot for H. Peter Anvin: > Commit-ID: 18de1534f9b69fb298a5b56e61919130d875b34b > Gitweb: http://syslinux.zytor.com/commit/18de1534f9b69fb298a5b56e61919130d875b34b > Author: H. Peter Anvin <hpa at linux.intel.com> > AuthorDate: Thu, 1 Jul 2010 18:12:41 -0700 > Committer: H. Peter Anvin <hpa at linux.intel.com> >

Thank you all. It looks like -mno-red-zone flag is already in master branch since commit 7d70885d, but it seems it is applied to all EFI builds. IIUC, the problem only affects efi64 builds. So here's the modification of my patch to only apply -mno-red-zone flag to efi64 target. The patch is against master. I verified that it builds correctly in master. Please feel free to accept or reject

This is an attempt to avoid potential confusion. Here are some example sizes for the two Syslinux versions mentioned in the e-mail subject. Your build results might be different. 4.06: 1 55 Sep 22 22:23 modules/int18.com 1 108 Nov 1 18:07 version.mk 1 138 Nov 1 18:07 version.gen 1 138 Nov 1 18:07 version.h 1 239 Sep 22 22:23 modules/poweroff.com 1 408 Sep 22 22:25

Hello syslinux maintainers, I came across the issue of syslinux crashing with some EFIs in the UEFI boot mode. Upon closer investigation it turned out that most object files which go into syslinux efi64 are compiled with the so-called red zone. Some EFIs follow Windows ABI more strictly and cause syslinux to crash due to stack overwrite. Looking at mk/efi.mk there was a previous attempt to fix

1) mk/syslinux.mk runs a shell to make a temp file gcc_ok.$$$$.tmp (perhaps in the wrong directory) while several Makefiles have an include rule for *.tmp which I believe is causing some occasional parallel build issues. make[3]: Entering directory `/home/gene/s/g/bios/memdump' gcc_ok.6333.tmp:1: warning: NUL character seen; rest of line ignored gcc_ok.6333.tmp:1: *** missing separator.

On Sat, Jan 18, 2014 at 6:18 PM, H. Peter Anvin <hpa at zytor.com> wrote: > On 01/18/2014 12:58 PM, Gene Cumm wrote: >> 1) mk/syslinux.mk runs a shell to make a temp file gcc_ok.$$$$.tmp >> (perhaps in the wrong directory) while several Makefiles have an >> include rule for *.tmp which I believe is causing some occasional >> parallel build issues. >> >>

Op 2014-01-18 om 15:58 schreef Gene Cumm: > 1) mk/syslinux.mk runs a shell to make a temp file gcc_ok.$$$$.tmp > (perhaps in the wrong directory) while several Makefiles have an > include rule for *.tmp which I believe is causing some occasional > parallel build issues. > > make[3]: Entering directory `/home/gene/s/g/bios/memdump' > gcc_ok.6333.tmp:1: warning: NUL

On 01/18/2014 12:58 PM, Gene Cumm wrote: > 1) mk/syslinux.mk runs a shell to make a temp file gcc_ok.$$$$.tmp > (perhaps in the wrong directory) while several Makefiles have an > include rule for *.tmp which I believe is causing some occasional > parallel build issues. > > make[3]: Entering directory `/home/gene/s/g/bios/memdump' > gcc_ok.6333.tmp:1: warning: NUL

Hi Peter, Please pull the following changes. Paulo, I had to revert your "pxe: resolve names via DNS from protected-mode code" change because dns_resolv() is only implemented for PXELINUX and causes undefined symbol references for ISOLINUX, etc. Feel free to make the change again on top of the revert. The following changes since commit e7bd19def830e8341b1a100956345f1028740b9e:

Well, here's the read-only shell (rosh) that I've been working on. It's functional but still quite rough. My primary intention of posting it at this time is such that people have an easy way to demonstrate to themselves that the library calls I made work. This should apply as a patch to the head of the "dir" branch and the patch for c_cflag/c_lflag. The patch is only

Hi, I've tried to compile syslinux under mandriva, and the compilation always bails out because it hasn't created win32/syslinux.exe. As far as I understand, the build will work fine on a Windows / mingw installation, but not Linux. I've modified my Makefile to remove the win32/syslinux.exe from the build, and it now builds OK. This happened on 3.3.6 and also on 4.0pre.

From: Gene Cumm <gene.cumm at gmail.com> COM32/rosh: Improvements; ls acts more like ls with -l -i and -F being understood; Lots of code clean up and user assistance. Clean up the MCONFIG file; Clean up the code to get it to pass checkpatch.pl (aside from confusion on multi-line strings); Add a little more in the error function to recognize different errors; Signed-off-by: Gene Cumm

Hi Peter, The main part of this pull request includes commits that try to replace as many __intcall() invocations as possible. Some remain, but not many (and eventually they'll be gone too). There's also a patch to make better use of ld's --as-needed option and various other bug fixes/cleanups. The following changes since commit ff7334a2ce536b7f4b1f6d6f93ff4e285a3bd45a: Only

From: Matt Fleming <matt.fleming at linux.intel.com> Don't link against libmenu.a, it no longer exists as it was removed in commit 74518b8b691c ("elflink: Make ELF the default object format"). This fixes the following build error, make[2]: *** No rule to make target `../cmenu/libmenu/libmenu.a', needed by `hdt.c32'. Stop. Signed-off-by: Matt Fleming