similar to: LDFLAGS and distro overrides

Displaying 20 results from an estimated 1000 matches similar to: "LDFLAGS and distro overrides"

2013 Jul 11
0
LDFLAGS and distro overrides
Hi, Matt Fleming: > This just came up on IRC, > > 15:01 < chithead> the first one that fails is ld -m elf_i386 -Wl,-O1 -Wl,--as-needed -Bsymbolic -pie -E --hash-style=gnu -T /var/tmp/portage/sys-boot/syslinux-6.01_pre5/work/syslinux-6.01-pre5/core/i386/syslinux.ld -M -o ldlinux.elf ldlinux.o \ > 15:01 < chithead> --start-group libcom32.a --whole-archive
2015 Oct 28
2
Isohybrid wiki page and UEFI
On Tue, Oct 27, 2015 at 10:15 PM, Bruno Cornec via Syslinux <syslinux at zytor.com> wrote: > Bruno Cornec via Syslinux said on Wed, Oct 28, 2015 at 01:45:22AM +0100: >> >> Is there a way to increase the debug level of syslinux.efi in order to >> check what it tries to do and diagnose more precisely what happens ? > > > Ok, I tried to modify mk/devel.mk to put:
2015 Oct 28
3
Isohybrid wiki page and UEFI
Hello Thomas, Thomas Schmitt via Syslinux said on Sun, Oct 25, 2015 at 04:35:57PM +0100: >I assume you can boot Fedora Live CD on the same (virtual) hardware. Not sure for Fedora, but the system is installed with either RHEL6, RHEL7 or Ubuntu 14.04 depending on the Lab I'm making on it without issue. >Just to make sure that the firmware works so far. Globally they do ;-) >
2015 Oct 08
1
[PATCH 0/4] Improve linker scripts
2015-10-08 12:58 UTC+02:00, Gene Cumm <gene.cumm at gmail.com>: > On Mon, Oct 5, 2015 at 2:15 PM, celelibi--- via Syslinux > <syslinux at zytor.com> wrote: >> From: Sylvain Gault <sylvain.gault at gmail.com> >> >> These patches basically remove unused linker scripts and port a change >> that was >> made to an unused script. >> >>
2015 Oct 05
7
[PATCH 0/4] Improve linker scripts
From: Sylvain Gault <sylvain.gault at gmail.com> These patches basically remove unused linker scripts and port a change that was made to an unused script. Those are to be applied on top of the gcc 5 bug fixes as they would conflict otherwise. Sylvain Gault (4): diag/mbr: fix dependency to linker script Remove unused linker scripts core: Make symbols defined in linker script HIDDEN
2013 Apr 19
2
make issue with syslinux-5.01
Hi, I am trying to compile the version on rhel 5.x box. Nasm version 0.98.39 I extracted the tar.gz and ran make in the extracted directory. Here is where it stops. gcc -Wp,-MT,rawcon.o,-MD,./.rawcon.o.d -m32 -ffreestanding -fno-stack-protector -fwrapv -freg-struct-return -march=i386 -Os -fomit-frame-pointer -mregparm=3 -DREGPARM=3 -msoft-float -fno-exceptions -fno-asynchronous-unwind-tables
2014 Jan 18
4
Makefiles: includes and rule prerequisites
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.
2015 Oct 28
0
Isohybrid wiki page and UEFI
Bruno Cornec via Syslinux said on Wed, Oct 28, 2015 at 01:45:22AM +0100: >Is there a way to increase the debug level of syslinux.efi in order to >check what it tries to do and diagnose more precisely what happens ? Ok, I tried to modify mk/devel.mk to put: GCCWARN += -Wno-clobbered -DCORE_DEBUG=1 -DDEBUG_MALLOC -DDEBUG_THREAD And removing the -DDYNAMIC_DEBUG but now syslinux doesn't
2015 Oct 28
0
Isohybrid wiki page and UEFI
Gene Cumm said on Wed, Oct 28, 2015 at 05:58:59AM -0400: >> Ok, I tried to modify mk/devel.mk to put: >> GCCWARN += -Wno-clobbered -DCORE_DEBUG=1 -DDEBUG_MALLOC -DDEBUG_THREAD >> And removing the -DDYNAMIC_DEBUG but now syslinux doesn't want to build: > >MALLOC and THREAD are two debugs you probably don't want. Ok I can drop them, but that doesn't change the
2009 May 15
3
The "core32" development branch
Well, there is now a development branch in the git repository, which contains the infrastructure needed for rewriting the core in C. As an initial test case it simply contains a "Hello, World!" and a rewrite of rllpack in C. This is not production code in any way: SYSLINUX (the FAT version) is completely broken (I haven't had time to fix the installers yet) and the Linux kernel
2014 Jan 19
1
Makefiles: includes and rule prerequisites
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. >> >>
2015 Oct 08
0
[PATCH 0/4] Improve linker scripts
On Mon, Oct 5, 2015 at 2:15 PM, celelibi--- via Syslinux <syslinux at zytor.com> wrote: > From: Sylvain Gault <sylvain.gault at gmail.com> > > These patches basically remove unused linker scripts and port a change that was > made to an unused script. > > Those are to be applied on top of the gcc 5 bug fixes as they would conflict > otherwise. > > Sylvain
2004 Dec 08
4
malloc in libcom32 broken?
I get a link error when trying to call malloc from libcom32. I tried to simplify the case by adding the malloc to the sample hello.c in the modules directory, but I still get the following error: ld -m elf_i386 -T ../lib/com32.ld -o hello.elf hello.o ../libutil/libutil_com.a ../lib/libcom32.a /usr/lib64/gcc-lib/x86_64-suse-linux/3.3.3/32/libgcc.a ../lib/libcom32.a(malloc.o)(.text+0x13): In
2008 Oct 14
2
SYSLINUX 3.73-pre3
I just pushed out SYSLINUX 3.73-pre3. The only significant difference over -pre2 was changing MEMDISK to use "safeint" by default. -hpa
2012 Mar 23
19
[PATCH 00/19][elflink] Improve compatibility with 4.x
From: Matt Fleming <matt.fleming at intel.com> The following patch series is available at, git://git.zytor.com/users/mfleming/syslinux.git elflink All patches are against the 'elflink' branch. This series fixes a few serious bugs and some behavioural incompatibilities with the 4.x series. Matt Fleming (19): ldlinux: Initialise 'p' before using it. ldlinux: Parse
2007 Aug 07
1
Errors compiling wine under Red Hat
Hello, all, I'm trying to get Wine running on some Red Hat boxes at my University (don't worry, I have permission!) ... But, I don't have any root access to the boxes, and I'm limited to installing on my shared (AFS) space. In any case, I'd probably want it to run from my user space anyways, so that its accessible from all boxes on the network. Some required information,
2015 Oct 05
0
[PATCH 4/4] core: Move linker script in arch-agnostic dir
From: Sylvain Gault <sylvain.gault at gmail.com> As there is no need for an x86_64 linker script, the i386 one can be put in the core directory directly. This partially revert commit d8eede3f2a360163235fad222a0190cd7c5bef38 which splitted several linker scripts into i386 and x86_64 versions. Signed-off-by: Sylvain Gault <sylvain.gault at gmail.com> --- core/Makefile |
2007 Feb 07
2
SYSLINUX 3.36-pre6 (release candidate)
I have, hopefully, found and fixed the issue with non-kernel binaries that appeared in 3.35. As a result, I have pushed out 3.36-pre6 and am classifying it as a release candidate. Please try it out, especially if you have had problems with 3.35. ftp://ftp.kernel.org/pub/linux/utils/boot/syslinux/Testing/ -hpa
2014 Aug 24
1
Library_modules (list of & wiki write permissions)
Hello, I poked a little bit to extract the list of modules dependencies in Syslinux v6 (see below). I have attached a bash script that generate a nice table from the tarball. The output can either be an ASCII table, or wiki markup, typically for the page Library_modules[1]. I am not in the wiki Editor group, so I can't put that in the wiki. anyway, here's an updated dependency tree for
2004 Dec 03
3
libcom32 license and linking
Peter- Can you please clarify the license of libcom32, from the samples directory in syslinux? I am attempting to create .c32 files that are not encumbered by the GPL, but the conio.c file states that is is covered by the GPL. So far, I have resisted linking with libcom32.a, but is it really your intent to license the library code under GPL, and not something more like the LGPL?