"Sean C." <karasune@xxxxxxxxx> writes: > I'm having trouble building GCC 4.3.3 natively on a SUSE 8 box. > The machine in question is the master node of a rather dated cluster, > on which one of the users needed a fortran compiler with OpenMP. As > the cluster is running gcc 3.3.5, I decided to just compile gcc from > source like usual. The only configuration flag I provided was > --prefix; otherwise, I didn't do anything out of the ordinary.. After > running 'make bootstrap,' though, make recieved the following error: > " gcc-4.3.3/libiberty/strsignal.c:553: error: conflicting types for `psignal' " > I couldn't find someone with a similar error while building GCC in the > mail archives nor through Google. I realize I'm probably making some > kind of stupid mistake, but I'm clueless as to why this is happening. > Has anyone seen this before, or does anyone have an idea of why the > build is tanking at this point? This means that the libiberty configure script decided that your system does not have psignal, but that psignal is declared in a header file nevertheless. Either the libiberty configure script made a mistake, or you have psignal declared in a header file although it is not present in your C library. Looking in libiberty/config.log in your build directory may give you more information about what happened. The easy workaround is almost certainly going to be to change the line psignal (int signo, char *message) in strsignal.c to psignal (int signo, const char *message) Ian
