similar to: [PATCH] Fix gpxe compilation when gcc is patched to compile by default with -fPIE -Wl, -pie

gcc hardened by default is seen on gentoo, alt-linux, HLFS, etc. Patch fix on syslinux this error during gpxe compilation: [BUILD] bin/cpu.o arch/i386/core/cpu.c: In function 'get_cpuinfo': arch/i386/include/bits/cpu.h:79: error: can't find a register in class 'BREG' while reloading 'asm' arch/i386/include/bits/cpu.h:79: error: can't find a register in class

I'm going to try to push 4.05 out this week, so please holler if there is anything critical missing. -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.

Hello everyone, Clang seems to only define __PIE__ when both –fPIC and –fPIE is used in the command line whereas gcc defines both __PIC__ and __PIE__. Is this intended or a bug in clang? Thanks. Command line: clang -fPIC -fPIE -dM -E - < /dev/null | grep __PI -- Tareq

Hi All, I compiled the following code on my linux PC using clang with PIE option- struct struct4 {char a; char b; char c; char d; }; struct struct4 foo4 = {'a','2','c','4'}; struct struct4 fun4() { return foo4; } int main() { fun4(); return 0; } > clang -g -fPIE structs.c In GDB session when i call p/c fun4() i get something like below- (gdb) p/c

If I create an llvm IR file (.ll) using clang like this: clang -v -emit-llvm -fPIC -O0 -S global_dat.c -o global_dat_x86_pic.ll And then take a look at the resulting .ll file, I see near the bottom: !0 = !{i32 1, !"PIC Level", i32 2} Now if I do the same, but specify -fPIE: clang -v -emit-llvm -fPIE -O0 -S global_dat.c -o global_dat_x86_pie.ll And then look at the resulting

On Fri, Nov 6, 2015 at 10:46 AM, Tim Northover <t.p.northover at gmail.com> wrote: > On 6 November 2015 at 10:32, Phil Tomson via llvm-dev > <llvm-dev at lists.llvm.org> wrote: > > So if I were to pass this .ll file (global_dat_x86_pie.ll) to llc how > would > > llc know that the PIE Level is 2? Is this an oversight, bug, or expetcted > > behaviour with a

On Fri, Nov 6, 2015 at 11:10 AM, Tim Northover <t.p.northover at gmail.com> wrote: > On 6 November 2015 at 11:00, Phil Tomson <phil.a.tomson at gmail.com> wrote: > > With 3.6 I get an unused argument warning with -enable-pie: > > > > $ clang -v -emit-llvm -enable-pie -O0 -S global_dat.c -o > > global_dat_x86_pie.ll > > Yes, it's an llc option not a

https://bugzilla.netfilter.org/show_bug.cgi?id=1052 Bug ID: 1052 Summary: iptables -wL fails Product: netfilter/iptables Version: unspecified Hardware: x86_64 OS: Ubuntu Status: NEW Severity: normal Priority: P5 Component: ip_tables (kernel) Assignee: netfilter-buglog at

On Wed, 2 Mar 2005, Markus F.X.J. Oberhumer wrote: > When running the current CVS version on an AMD64 (targeted at 64-bits) I hit > the following when trying to link with -Wl,native-cbe: > > march=c((anonymous namespace)::PrintStackTrace()+0x1e)[0x847a17e] > /lib/libc.so.6(abort+0xcc)[0x556abbbc] > -march=c[0x8261958] > [0x8afe738] > gccld: /usr/lib/../lib64/X11:

On Tue, 2005-03-01 at 22:07, Markus F.X.J. Oberhumer wrote: > Follow up: After removing the dangling symlink the problem now looks: > > -march=c((anonymous namespace)::PrintStackTrace()+0x1e)[0x847a17e] > -fno-strict-aliasing: example.out.cbe.c: No such file or directory > gccld: example.out.cbe.c: Can't destroy file: > make: *** [example.out] Error 1 > At a minimum that

Adam, Looks like you have your first issue with the gccld patch. Could you please look into this for us? Markus seems to have detected a situation where -native-cbe is acting like -native ... On Wed, 2005-03-02 at 00:39, Markus F.X.J. Oberhumer wrote: > Short update: -native-cbe is currently broken as gccld/llc seems to generate > assembler code instead of C. To easy debugging of such

I will definately look into this tonight and see if it is a problem with my recent patch. On Wednesday 02 March 2005 3:39 am, Markus F.X.J. Oberhumer wrote: > Reid Spencer wrote: > > On Tue, 2005-03-01 at 22:07, Markus F.X.J. Oberhumer wrote: > >>Follow up: After removing the dangling symlink the problem now looks: > >> > >>-march=c((anonymous

Hi. My system image is built on amd64 using Gentoo catalyst, and my target is x86. This works really well. However, OpenSSH configure adds -Wl,-rpath -Wl,/usr/lib to LIBS during build, which then causes a problem when trying to run sftp. (sftp has been linked with libedit, and /usr/lib/libedit.so exists but is a linker script that points to /lib/libedit.so. This linker script confuses ld.so

Hi everyone, Any chance I can get the card[1] in $subj to work under CentOS 5.1 ? The only thing I get in dmesg when inserting/removing the card, are messages from pccard: --- dmesg --- pccard: CardBus card inserted into slot 0 pccard: card ejected from slot 0 --- end --- When inserting, no new network interface becomes available, so I assume it doesn't recognize it. Any way I can get it to

Also what exact distro and version are you having the problem on and what version of ld does it have? Mine is $ ld --version GNU ld version 2.29.1-23.fc28 -- Darren Tucker (dtucker at dtucker.net) GPG key 11EAA6FA / A86E 3E07 5B19 5880 E860 37F4 9357 ECEF 11EA A6FA (new) Good judgement comes with experience. Unfortunately, the experience usually comes from bad judgement.

Been experimenting with CentOS 5.4 some more. In order to get my wireless card to work (Broadcom BCM4311) I need Broadcom's wl.ko driver (http:// www.broadcom.com/support/802.11/linux_sta.php). It compiles fine after the necessary modification in typedef.h, loads and wireless works. However, as soon as I put some load on that interface (scp something from another machine, download

https://bugzilla.mindrot.org/show_bug.cgi?id=2030 Priority: P5 Bug ID: 2030 Assignee: unassigned-bugs at mindrot.org Summary: build of 6.0p1 fails @ "/usr/bin/ld: unrecognized option '-Wl,-rpath,/usr/local/ssl/lib64" Severity: major Classification: Unclassified OS: Linux Reporter:

On 8 June 2018 at 12:09, PGNet Dev <pgnet.dev at gmail.com> wrote: [...] > /usr/bin/ld -o ssh ssh.o readconf.o clientloop.o sshtty.o sshconnect.o sshconnect2.o mux.o -L. -Lopenbsd-compat/ -Wl,-z,relro -Wl,-z,now -Wl,-z,noexecstack -fstack-protector-strong -pie -lssh -lopenbsd-compat -lutil -lz -lcrypt -lresolv > /usr/bin/ld: unrecognized option

hi On 6/7/18 4:03 PM, Darren Tucker wrote: > On 8 June 2018 at 07:09, PGNet Dev <pgnet.dev at gmail.com> wrote: >> Verifying a report I just got pinged about, building vanilla openssh 7.7p1 on linux configures ok, but fails build around 'retpoline' > [...] >> Should the retpoline flag be getting added? If so, what's needed to make LD happy with it? > >

On 6/7/18 8:37 PM, Darren Tucker wrote: > On 8 June 2018 at 12:21, Darren Tucker <dtucker at dtucker.net> wrote: >> On 8 June 2018 at 12:09, PGNet Dev <pgnet.dev at gmail.com> wrote: >> [...] >>> /usr/bin/ld -o ssh ssh.o readconf.o clientloop.o sshtty.o sshconnect.o sshconnect2.o mux.o -L. -Lopenbsd-compat/ -Wl,-z,relro -Wl,-z,now -Wl,-z,noexecstack