Do not call printf from sigaction (XCC)
authorBarret Rhoden <brho@cs.berkeley.edu>
Mon, 14 Dec 2015 19:44:46 +0000 (14:44 -0500)
committerBarret Rhoden <brho@cs.berkeley.edu>
Wed, 16 Dec 2015 23:23:10 +0000 (18:23 -0500)
commit7eec4d440a75090271d36ec6ddd300f31bdd0572
tree474281b06a1cb5f45252792dbff6235fc5feb551
parent97e5dc75c4b08d95095dc472f5a2b723e0dcfdd3
Do not call printf from sigaction (XCC)

Right now, it's okay, since parlib redefines printf to akaros_printf.  That
tricks whatever dark magic that triggers the 'multiple libcs' problem.  But
when we fix printf to not use a macro-based solution, this breaks.

Until we understand more, we need to continue to be careful about where we
call printf or similar functions within glibc.  Normally, we'll find out
when the toolchain build fails, but with the #undef printf in
parlib/stdio.h, we were hiding those failures.  That will be fixed shortly.

Rebuild glibc.

Signed-off-by: Barret Rhoden <brho@cs.berkeley.edu>
tools/compilers/gcc-glibc/glibc-2.19-akaros/sysdeps/akaros/Versions
tools/compilers/gcc-glibc/glibc-2.19-akaros/sysdeps/akaros/parlib-compat.c
tools/compilers/gcc-glibc/glibc-2.19-akaros/sysdeps/akaros/sigaction.c