Sanity check: Build with gcc3 known to fail?

Wed May 21 23:09:21 CEST 2003

Nigel Head writes:
 > Having just tried to build r9b1 on a SuSe8.2 system (which has gcc3) and got reams and reams of compare signed/unsigned warnings -- which look benign -- and some token pasteing errors -- which look less benign -- and a failed install I thought I'd check if this is known to be a problem by any of you old hands. I don't easily have an older gcc available to go the 'trial and error' route and I'm new enough to erlang to have only used the windows binary distribution for toy things so far, so I have no basis for comparison.

The patch below should fix the token pasting problem. It works for me.

I got an unexpected failure in one of our test suites today with gcc-3.3
on SPARC Solaris 9. I'll retest tomorrow on x86. gcc-3.2.3 seems Ok though.


Index: otp/erts/etc/unix/run_erl.c
RCS file: /it/project/fo/hipe/repository/otp/erts/etc/unix/run_erl.c,v
retrieving revision 1.5
diff -u -r1.5 run_erl.c
--- otp/erts/etc/unix/run_erl.c	16 May 2003 12:15:06 -0000	1.5
+++ otp/erts/etc/unix/run_erl.c	21 May 2003 16:12:28 -0000
@@ -130,7 +130,7 @@
 #ifdef NO_SYSLOG
 #define OPEN_SYSLOG() ((void) 0)
-#define ERROR(Parameters) stderr_error##Parameters
+#define ERROR(Parameters) stderr_error Parameters
 #define OPEN_SYSLOG()\
@@ -138,9 +138,9 @@
 #define ERROR(Parameters)			\
 do {						\
     if (run_daemon) {			        \
-	syslog##Parameters;			\
+	syslog Parameters;			\
     } else {					\
-	stderr_error##Parameters;		\
+	stderr_error Parameters;		\
     }						\
 } while (0)

More information about the erlang-questions mailing list