make proto on gcc trunk fails on Linux/x86_64 with:

/abuild/builds/gcc/./prev-gcc/xgcc -B/abuild/builds/gcc/./prev-gcc/ 
-B/opt/gcc/4.2-devel/x86_64-suse-linux-gnu/bin/ -c -DUNPROTOIZE   -g -O2 
-DIN_GCC   -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes 
-pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings 
-Wold-style-definition -Wmissing-format-attribute -Werror -fno-common   
-DHAVE_CONFIG_H -I. -I. -I/cvs/gcc-svn/trunk/gcc -I/cvs/gcc-svn/trunk/gcc/. 
-I/cvs/gcc-svn/trunk/gcc/../include -I/cvs/gcc-svn/trunk/gcc/../libcpp/include  
-I/cvs/gcc-svn/trunk/gcc/../libdecnumber -I../libdecnumber    \
  -DSTANDARD_STARTFILE_PREFIX=\"../../../\" 
-DSTANDARD_EXEC_PREFIX=\"/opt/gcc/4.2-devel/lib/gcc/\" 
-DSTANDARD_LIBEXEC_PREFIX=\"/opt/gcc/4.2-devel/libexec/gcc/\" 
-DDEFAULT_TARGET_VERSION=\"4.2.0\" 
-DDEFAULT_TARGET_MACHINE=\"x86_64-suse-linux-gnu\" 
-DSTANDARD_BINDIR_PREFIX=\"/opt/gcc/4.2-devel/bin/\" 
-DTOOLDIR_BASE_PREFIX=\"../../../../\"  `test "X${SHLIB_LINK}" = "X" || test 
"yes" != "yes" || echo "-DENABLE_SHARED_LIBGCC"` `test "X${SHLIB_MULTILIB}" = 
"X" || echo "-DNO_SHARED_LIBGCC_MULTILIB"` \
  /cvs/gcc-svn/trunk/gcc/protoize.c -o unprotoize.o)
cc1: warnings being treated as errors
/cvs/gcc-svn/trunk/gcc/protoize.c: In function ‘edit_fn_definition’:
/cvs/gcc-svn/trunk/gcc/protoize.c:3506: warning: argument ‘clean_text_p’ might 
be clobbered by ‘longjmp’ or ‘vfork’
make: *** [unprotoize.o] Error 1

I don't know what broke this since I haven't bootstrapped gcc the last
three weeks.    Any ideas?

The trivial workaround is to add to gcc/Makefile.in something like:

# Fix for argument ‘clean_text_p’ might be clobbered by ‘longjmp’ or ‘vfork’
unprotoize.o-warn = -Wno-error

If I should submit this as patch, please tell me,

Andreas
-- 
 Andreas Jaeger, [EMAIL PROTECTED], http://www.suse.de/~aj/
  SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
   GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126

Attachment: pgpk5Vo0QBTvD.pgp
Description: PGP signature

Reply via email to