poma
2016-Feb-02 17:50 UTC
[syslinux] binutils (objcopy?) >= 2.26 breaks syslinux (bios) build
On 30.01.2016 16:59, poma wrote:> ... > > https://sourceware.org/bugzilla/show_bug.cgi?id=19538 > >Mister Anvin, care to share what's the status of the "ld?" problemo, is anyone working on it? It would be maravilloso if syslinux can continue to build and test with latest and greatest.
Celelibi
2016-Feb-03 15:17 UTC
[syslinux] binutils (objcopy?) >= 2.26 breaks syslinux (bios) build
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 >> >> > > Mister Anvin, > care to share what's the status of the "ld?" problemo, > is anyone working on it? > > It would be maravilloso if syslinux can continue to build and test with > latest and greatest.There have been a discussion about the -fPIC option a few month ago (november or december 2015). I don't remember what exactly it was about. I think I said I would submit a patch that add -fPIC for 32 bits even thought it wouldn't have an actual effect regarding current compilers. This option is definitely required for 64 bits, and it is theoretically required for 32 bits. But I haven't investigated the current issue. Celelibi
Ady
2016-Feb-03 16:39 UTC
[syslinux] binutils (objcopy?) >= 2.26 breaks syslinux (bios) build
> On 30.01.2016 16:59, poma wrote: > > ... > > > > https://sourceware.org/bugzilla/show_bug.cgi?id=19538 > > > > > > Mister Anvin, > care to share what's the status of the "ld?" problemo, > is anyone working on it? > > It would be maravilloso if syslinux can continue to build and test with latest and greatest. >Is there any chance that this issue might be somehow related to some 'make' parameter such as "make EFI_BUILD=1 ARCH=i386" (either, or both of them, or similars, or any other one), which we mildly discussed during 2015Nov? I cannot help but wonder whether executing a 'make spotless' before executing the final 'make' could generate a different result / message(s) (considering that the Syslinux binaries were built more than once while testing). Completely unrelated to my comments above... Some patches that "might" give some clue to some knowledgeable developer (let's hope): gnu-efi, syslinux: Support gcc < 4.7 cgit.openembedded.org/openembedded-core/commit/meta/recipes-devtools/sys linux/syslinux?id=90e7cfebc6a9ac4b229b45c6a7dc95218efe55c5 syslinux: Dont bypass gcc driver for dependency generation options cgit.openembedded.org/openembedded-core/commit/meta/recipes-devtools/sys linux/syslinux?id=f3ac32e0bc83d7aeea3e84258c258c2bb6dab44e syslinux: Set LD to avoid using build host ld cgit.openembedded.org/openembedded-core/commit/meta/recipes-devtools/sys linux/syslinux_6.03.bb?id=c4897af85eace49e3c27aebc1448227105286e30 Regarding "latest and greatest", there are several sections of (GPL) code being used in Syslinux that might benefit from some updated versions (some of them have not received updates in Syslinux's code since 2010). Regards, Ady.> _______________________________________________ > Syslinux mailing list > Submissions to Syslinux at zytor.com > Unsubscribe or set options at: > http://www.zytor.com/mailman/listinfo/syslinux >
H. Peter Anvin
2016-Feb-03 18:30 UTC
[syslinux] binutils (objcopy?) >= 2.26 breaks syslinux (bios) build
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 >>> >>> >> >> Mister Anvin, >> care to share what's the status of the "ld?" problemo, >> is anyone working on it? >> >> It would be maravilloso if syslinux can continue to build and test >with >> latest and greatest. > >There have been a discussion about the -fPIC option a few month ago >(november or december 2015). I don't remember what exactly it was >about. I think I said I would submit a patch that add -fPIC for 32 >bits even thought it wouldn't have an actual effect regarding current >compilers. > >This option is definitely required for 64 bits, and it is >theoretically required for 32 bits. But I haven't investigated the >current issue. > >CelelibiIt isn't just 32 vs 64 bits, it is also 32 bit BIOS vs 32 bit EFI, and their requirements differ. -- Sent from my Android device with K-9 Mail. Please excuse brevity and formatting.
poma
2016-Feb-09 11:23 UTC
[syslinux] binutils (objcopy?) >= 2.26 breaks syslinux (bios) build
On 03.02.2016 16:17, Celelibi 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 >>> >>> >> >> Mister Anvin, >> care to share what's the status of the "ld?" problemo, >> is anyone working on it? >> >> It would be maravilloso if syslinux can continue to build and test with >> latest and greatest. > > There have been a discussion about the -fPIC option a few month ago > (november or december 2015). I don't remember what exactly it was > about. I think I said I would submit a patch that add -fPIC for 32 > bits even thought it wouldn't have an actual effect regarding current > compilers. > > This option is definitely required for 64 bits, and it is > theoretically required for 32 bits. But I haven't investigated the > current issue. > > Celelibi >http://git.zytor.com/syslinux/syslinux.git/tree/core/Makefile#n119 # Set up the NASM and LD options for the architecture s/LD_PIE = -pie/LD_PIE =/ and/or s/LD_PIE = -pie/LD_PIE = -Bdynamic/ Failed to load ldlinux.c32 Boot failed: press a key to retry... _ Buildable but unusable.
Maybe Matching Threads
- binutils (objcopy?) >= 2.26 breaks syslinux (bios) build
- binutils (objcopy?) >= 2.26 breaks syslinux (bios) build
- binutils (objcopy?) >= 2.26 breaks syslinux (bios) build
- binutils (objcopy?) >= 2.26 breaks syslinux (bios) build
- binutils (objcopy?) >= 2.26 breaks syslinux (bios) build