[[!meta copyright="Copyright © 2012, 2013 Free Software Foundation, Inc."]] [[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable id="license" text="Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled [[GNU Free Documentation License|/fdl]]."]]"""]] [[!meta title="Position-Independent Executables"]] [[!tag open_issue_glibc]] # IRC, freenode, #debian-hurd, 2012-11-08 tschwinge: i'm not totally sure, but it seems the pie options for gcc/ld are causing issues namely, producing executables that sigsegv straight away pinotree: OK, I do remember some issues about these, too. Also for -pg. These have in common that they use different crt*.o files for linking. Might well be there's some bugs there. one way is to try the w3m debian build: the current build configuration enables also pie, which in turns makes an helper executable (mktable) sigsegv when invoked if «,-pie» is appended to the DEB_BUILD_MAINT_OPTIONS variable in debian/rules, pie is not added and the resulting mktable runs correctly ## IRC, OFTC, #debian-hurd, 2012-11-09 youpi: ah, as i noted to tschwinge earlier, it seems -fPIE -pie miscompile stuff uh this causes the w3m build failure and (indirectly, due to elinks built with -pie) aptitude ## id:"20130211040854.GN5926@type.youpi.perso.aquilenet.fr" [[glibc]] `t/pie-sbrk` branch.