similar to: [PATCH v2 0/4] Allow cross-building of syslinux

Displaying 20 results from an estimated 600 matches similar to: "[PATCH v2 0/4] Allow cross-building of syslinux"

2017 Apr 05
5
[PATCH 0/2] Cross-compilation patches
Hi there, I've had issue with the integration of syslinux into the buildroot project [0]. After some research, it turned out that we were wrongly using the host toolchain instead of the target toolchain to build syslinux. This gave us bigger issues (for instance) when trying to link syslinux with gnu-efi, that was built using the target toolchain. The first one forces ld to output i386
2014 Jun 21
1
isohybrid has 2 variants
Op 2014-06-20 om 15:56 schreef Ady: > > The Perl variant, isohybrid.in, seems to be getting left behind > regarding several patches. I don't recall whether there is at least > some mention in the isohybrid docs about the existence of 2 variants > included in Syslinux (and that is in addition to other isohybrid > methods outside Syslinux). Is there any reference? >
2017 Jun 09
2
[PATCH 1/3] The VPrint definition is now part of the exports of gnu-efi
Signed-off-by: Beno?t Allard <benoit.allard at greenbone.net> --- efi/fio.h | 9 --------- 1 file changed, 9 deletions(-) diff --git a/efi/fio.h b/efi/fio.h index 65fff8d..a1bfe68 100644 --- a/efi/fio.h +++ b/efi/fio.h @@ -11,15 +11,6 @@ #define MAX_EFI_ARGS 64 #define WS(c16) (c16 == L' ' || c16 == CHAR_TAB) -/* VPrint is not in export declarations in gnu-efi lib yet
2008 Feb 26
2
3.62-pre16: Compiling on old (2.4 kernel) distros
I have put a compile hack in for older distros and pushed it out as syslinux-3.62-pre16; for those who have reported compilation problem on older distros I would greatly appreciate if you could confirm if it works now (it worked for me on a CentOS 3.9 VM.) -hpa
2010 Apr 12
2
Patch to port isohybrid.pl to isohybrid.c
Hello all, Past few days I was working on porting the isohybrid perl script to c. (-> https://fedorahosted.org/fedora-engineering-services/ticket/15) The first patch towards the same is attached with this mail. And the same could also be accessed from: http://pjp.dgplug.org/tools/syslinux-3.86-isohybrid.patch I would really appreciate it if somebody could have a look at it and let me know
2017 Apr 05
0
[PATCH 2/2] utils: Use the host toolchain to build.
The utilities are meant to run on the host machine, hence must be built using the host toolchain. Signed-off-by: Beno?t Allard <benoit.allard at greenbone.net> --- utils/Makefile | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/utils/Makefile b/utils/Makefile index dfe6259..f31f117 100644 --- a/utils/Makefile +++ b/utils/Makefile @@ -17,8 +17,9 @@ VPATH = $(SRC)
2011 Aug 05
3
isolinux: Generate GPT and Mac bootable images
EFI systems typically don't support booting off ISO 9660 filesystems, even if written to USB sticks. This patch adds support for generating a GPT that covers the stick as well, with an additional partition entry pointing purely at the secondary El Torito image. When burned to CD the secondary El Torito will be used as an EFI boot image, and when written to a USB stick the GPT partition
2017 Apr 05
0
[PATCH 1/2] memdisk: Force ld output format to 32-bits
On toolchains where the default output is x86_64, we need to be consistent with the other .o files Signed-off-by: Beno?t Allard <benoit.allard at greenbone.net> --- memdisk/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/memdisk/Makefile b/memdisk/Makefile index 42e56e0..ccd5738 100644 --- a/memdisk/Makefile +++ b/memdisk/Makefile @@ -78,7 +78,7 @@ memdisk16.o:
2017 Jun 30
0
[PATCH v2 1/4] memdisk: Force ld output format to 32-bits
On toolchains where the default output is x86_64, we need to be consistent with the other .o files Signed-off-by: Beno?t Allard <benoit.allard at greenbone.net> --- memdisk/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/memdisk/Makefile b/memdisk/Makefile index 42e56e0..ccd5738 100644 --- a/memdisk/Makefile +++ b/memdisk/Makefile @@ -78,7 +78,7 @@ memdisk16.o:
2014 Jan 20
3
[PATCH] Add some man pages.
Add very basic pages for: isohybrid - It's not particularly more useful than --help, but my QA department really wants this to exist. memdiskfind - Explain what it does and its invocation. Signed-off-by: Peter Jones <pjones at redhat.com> --- man/isohybrid.1 | 61 +++++++++++++++++++++++++++++++++++++++++++++++++++++++ man/memdiskfind.1 | 10 +++++++++ 2 files changed, 71
2015 Sep 14
2
[PATCH] Dont bypass compiler driver for Dependency generation options
> On Sep 13, 2015, at 11:04 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > > On Thu, Sep 10, 2015 at 1:55 AM, Khem Raj via Syslinux > <syslinux at zytor.com> wrote: >> We can let compiler driver pass the right options to preprocessor after >> processing -Mxy options, right now its bypassing the gcc driver and >> handing them straight to cpp >>
2017 Jun 26
2
Install locks up my server
On 06/26/17 14:42, Timo Sirainen wrote: > On 26 Jun 2017, at 23.19, Marc Perkel <marc at perkel.com> wrote: >> Ever since 2.26 I haven't been able to upgrade. In fact the install locks up my server. >> >> I get into and infinite recursive loop where the config-guess program calls itself until the server locks up from overload. >> >> I'm running Centos
2015 Sep 10
3
[PATCH] Dont bypass compiler driver for Dependency generation options
We can let compiler driver pass the right options to preprocessor after processing -Mxy options, right now its bypassing the gcc driver and handing them straight to cpp This also helps in other compilers processing these options correctly for their preprocessors consumption Signed-off-by: Khem Raj <raj.khem at gmail.com> --- mk/syslinux.mk | 4 ++-- 1 file changed, 2 insertions(+), 2
2017 Jun 26
2
Install locks up my server
Ever since 2.26 I haven't been able to upgrade. In fact the install locks up my server. I get into and infinite recursive loop where the config-guess program calls itself until the server locks up from overload. I'm running Centos 6 under OpenVZ. What am I missing? I think there's a serious bug. 31233 pts/3 S 0:00 /bin/sh ./config.guess 31235 pts/3 S 0:00 \_
2020 Aug 11
1
Install OpenVAS on CentOS Linux release 8.2.2004 (Core)
On Tue, Aug 11, 2020 at 9:24 PM Ralf Prengel <ralf.prengel at rprengel.de> wrote: > Hallo, > not direkt a solution but I m using a kali rolling release installation on > hard disk. > Works fine here. > > Ralf > > Hi, I am facing the below mentioned issue. #wget -q -O - http://www.atomicorp.com/installers/atomic |sh [root at openvas8 ~]# yum -y install openvas Last
2014 Jun 22
1
isohybrid has 2 variants
Op 2014-06-21 om 21:19 schreef intrigeri: > Hi, > > Ian Bannerman wrote (21 Jun 2014 15:49:51 GMT) : > > One advantage of the Perl one for me is that I can run it on Windows. > > We at Tails rely on isohybrid.pl for installing on OSX: > https://tails.boum.org/doc/first_steps/installation/manual/mac/ > > Of course, this does not mean that the current syslinux team
2020 Aug 11
4
Install OpenVAS on CentOS Linux release 8.2.2004 (Core)
Hi, I am running CentOS Linux release 8.2.2004 (Core). Are there any instructions to install OpenVAS for CentOS Linux release 8.2.2004 (Core)? Thanks in advance and I look forward to hearing from you. Best Regards, Kaushal
2008 Jan 01
8
DO NOT REPLY [Bug 5170] New: Cross compilation does not work
https://bugzilla.samba.org/show_bug.cgi?id=5170 Summary: Cross compilation does not work Product: rsync Version: 3.0.0 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: r.schwebel@pengutronix.de
2016 Dec 20
2
samba wins and MS11-035
Hello Samba, I'm running 4.2.14 (yes, will update;-) ) as a DC. In our network we run security scans with a greenbone.net system which is basically a OpenVAS.org appliance. OpenVAS reports the following security problem against the samba wins server: Microsoft Windows WINS Remote Code Execution Vulnerability (2524426)
2012 Oct 24
1
memdisk, memdiskfind and phram.ko
Hi, The method to boot an ISO using memdisk, memdiskfind and phram described in the wiki looks very promising to me. So, I looked into the sources trying to understand, how this works. Up to now, I could not find out how the memory containing the ISO image is preserved from being overwritten by the Linux kernel. Probably I'm missing something, could you please help me? Best regards, Bodo