Dear Camm,

> This seems to be the problem.  Do you still get a relocation error
> message?

Yep.

> It owuld be very helpful if you you determine what gcc compiler switches
> your hardening setup is adding that produce these relocs.  Gcl does not
> attempt to support all of them, especially as it thinks it is
> controlling the switches to the C compiler.  (lisp variable
> compiler::*cc*).   Maybe you could run under strace -f and grep the exec
> gcc?

I did a "strace -f -ff -o blub axiom" and the lines you're probably interested 
in are

execve("/usr/bin/gcc", ["gcc", "-c", "-Wall", "-DVOL=volatile", 
"-fsigned-char", "-Wno-unused-but-set-variable", "-pipe", "-I../h", "-O3", 
"-fomit-frame-pointer", "-c", "/tmp/gazonk2.c", "-o", "/tmp/gazonk2.o", "-w"], 
[/* 47 vars */]) = 0

and

execve("/usr/bin/gcc-4.7.real", ["/usr/bin/gcc-4.7.real", "-fstack-protector", 
"--param=ssp-buffer-size=4", "-fPIE", "-D_FORTIFY_SOURCE=2", "-Wformat", 
"-Wformat-security", "-Werror=format-security", "-c", "-Wall", 
"-DVOL=volatile", "-fsigned-char", "-Wno-unused-but-set-variable", "-pipe", 
"-I../h", "-O3", ...], [/* 47 vars */]) = 0


Thank you very much.

Regards,
Edi


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to