Re: fix gcc 4.9 -static

Tobias Ulmer wrote: > Sync STARTFILE_SPEC, fixes egcc -static producing crashing programs > > I don't expect any fallout from this (builtin spec file change only) Checking with gcc -v, it seems to work on amd64. gcc 4.9 and our base gcc behave the same given various

CVS: cvs.openbsd.org: ports

CVSROOT:/cvs Module name:ports Changes by: ste...@cvs.openbsd.org 2016/07/06 10:33:35 Modified files: devel/llvm : Makefile devel/llvm/patches: patch-tools_clang_lib_Driver_Tools_cpp Log message: Make clang build working binaries by linking against rcrt0

Re: devel/llvm: make clang build working static PIE programs

ping? Stefan Kempf wrote: > clang currently links against /usr/lib/crt0.o when building > a binary with the -static -pie options. That makes such > programs segfault on startup (gcc 4.9 seems to have the same > problem). > > When building a static PIE program, we need to link

devel/llvm: make clang build working static PIE programs

clang currently links against /usr/lib/crt0.o when building a binary with the -static -pie options. That makes such programs segfault on startup (gcc 4.9 seems to have the same problem). When building a static PIE program, we need to link against /usr/lib/rcrt0.o, as shown below. Bitrig has this

Re: avoid W|X mappings in libffi

Jeremie Courreges-Anglas wrote: > Stuart Henderson writes: > > > This disables PROT_EXEC mappings in libffi (and thus python). > > I'm running with it in a bulk build with the "mandatory W^X" > > printfs that are going into snapshots and haven't triggered > > them yet,