similar to: Making the linker output the relevant dynamic stuff

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. >> >>

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

On 08.02.2016 19:04, H. Peter Anvin wrote: > On 02/03/16 10:30, H. Peter Anvin via Syslinux wrote: >> On February 3, 2016 7:17:37 AM PST, Celelibi <celelibi at gmail.com> wrote: >>> 2016-02-02 18:50 UTC+01:00, poma via Syslinux <syslinux at zytor.com>: >>>> On 30.01.2016 16:59, poma wrote: >>>>> ... >>>>> >>>>>

Hello Rui, I'm enabling the LLD in the Uefi firmware edk2 build. I meet a problem about the -pie option and cannot output the executable type obj file correctly. I need your advice. The Uefi firmware executable binary is the position independent + small code mode in 64bits. So we always add the options "-Wl,-pie -mcmodel=small" in our clang build toolchain. These options work well

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

On 02/03/16 10:30, H. Peter Anvin via Syslinux wrote: > On February 3, 2016 7:17:37 AM PST, Celelibi <celelibi at gmail.com> wrote: >> 2016-02-02 18:50 UTC+01:00, poma via Syslinux <syslinux at zytor.com>: >>> On 30.01.2016 16:59, poma wrote: >>>> ... >>>> >>>> https://sourceware.org/bugzilla/show_bug.cgi?id=19538 >>>>

On 13.02.2016 10:01, Ady via Syslinux wrote: > >>> Yes, it is a bug in ld. I have been working with H.J. and we have just tracked it down. >>> >> >> >> It seems that hjl helped, after all. >> >> Syslinux built, or better to write, linked with: >> binutils 2.26.51.20160212 git 95c00d1 is salt-n-pepa. >> >> Both, ISOLINUX and

On 8 January 2018 at 09:32, James Henderson via llvm-dev <llvm-dev at lists.llvm.org> wrote: > On 8 January 2018 at 08:14, Rui Ueyama <ruiu at google.com> wrote: >> >> On Mon, Jan 8, 2018 at 3:55 AM, Sean Silva via llvm-dev >> <llvm-dev at lists.llvm.org> wrote: >>> >>> >>> >>> On Jan 7, 2018 5:02 PM, "Cary Coutant via

> > Considering that a Mass Rebuild was already performed for F24, then an > > updated, patched binutils would probably generate new, working > > Syslinux-related packages. Otherwise, these packages for/in F24 will be > > probably failing. > > > > Binutils: > "Enable -Bsymbolic and -Bsymbolic-functions to PIE" >

"syslinux-bot for H. Peter Anvin" <hpa at zytor.com> on Wed, 2013/12/04 12:39: > Commit-ID: ef81a3ad54845ffb5ad62714cd62db4740ad5cff > Gitweb: > http://www.syslinux.org/commit/ef81a3ad54845ffb5ad62714cd62db4740ad5cff > Author: H. Peter Anvin <hpa at zytor.com> AuthorDate: Wed, 4 Dec 2013 > 12:35:09 -0800 Committer: H. Peter Anvin <hpa at zytor.com>

I was thinking specifically of the subset of the commands for dealing with files, for example INPUT, GROUP and SEARCH_DIR. I agree that it would not be wise to allow the full generality of linker scripts. Thinking about this a bit more I think my main concern is that we should try hard to make sure that any commands that are embedded in an object file are compatible with any equivalent linker

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

Commit-ID: 84d319b2fda958d73a58bf338ee212da772d0cc6 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=84d319b2fda958d73a58bf338ee212da772d0cc6 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Sun, 6 Jan 2019 03:44:40 +0000 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Fri, 18 Jan 2019 03:10:14 +0000 [klibc] Disable PIE We link all

On 14.02.2016 18:08, Ady via Syslinux wrote: > >>> Considering that a Mass Rebuild was already performed for F24, then an >>> updated, patched binutils would probably generate new, working >>> Syslinux-related packages. Otherwise, these packages for/in F24 will be >>> probably failing. >>> >> >> Binutils: >> "Enable

On Mon, Jan 8, 2018 at 3:22 AM, Peter Smith <peter.smith at linaro.org> wrote: > On 8 January 2018 at 09:32, James Henderson via llvm-dev > <llvm-dev at lists.llvm.org> wrote: > > On 8 January 2018 at 08:14, Rui Ueyama <ruiu at google.com> wrote: > >> > >> On Mon, Jan 8, 2018 at 3:55 AM, Sean Silva via llvm-dev > >> <llvm-dev at

> You used -noinhibit-exec to ignore the diagnostic, which is usually a bad thing. I certainly agree with that. The point I was trying to make in my original email is that, specifically for kernel objects, this diagnostic is incorrect. R_X86_64_PC32 can be used safely against the symbol foo in that specific context, and should be possible without ignoring diagnostics. I wondered if there

On 11/18/2014 10:20 AM, Didier Spaier wrote: > > On 18/11/2014 18:55, H. Peter Anvin wrote: >> On 11/17/2014 12:55 AM, Didier Spaier wrote: >>> So one more question: why can one boot with a GRUB EFI bootloader >>> but not with the SYSLINUX bootloader, using the same kernel? >>> >>> More accurately, I know why: because of the aforementioned patch,

More recent versions of the GNU linker (>= 2.31) create a separate code "PT_LOAD" segment by default (as of https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=f6aec96dce1ddbd8961a3aa8a2925db2021719bb). Building syslinux EFI images with this -zseparate-code enabled creates broken EFI images, since efi/wrapper.c only copies the first PT_LOAD segment to the EFI. This patch adds

Hi all, Working on lld aarch64 support I came across an issue where I am not sure which would be best design approach to solve. The aarch64 R_AARCH64_ABS64 relocation for PIC/PIE build requires a dynamic relocation (R_AARCH64_RELATIVE) with the value set as the addend of the relocation. For instance, when linking the crtbeginS.o which contains: Relocation section '.rela.init_array' at

Is the new EH scheme completely compatible with the existing linker in Xcode 4.1? I am finding that today's changes break the ability to link xplor-nih with dragonegg under FSF gcc 4.6.2... de-g++46 -c thread.cc -O3 -ffast-math -funroll-loops -g -DX_MMAP_FLAGS=0 -DFORTRAN_INIT -fno-common -DDARWIN -D_REENTRANT -DNDEBUG -I/Users/howarth/xplor-nih-2.27/vmd/