Paul Edwards wrote: > First of all, I got link errors, because sched-ebb etc were trying > to call various functions, but those functions were not being > compiled in because INSN_SCHEDULING was not defined > (that's my quick analysis, anyway). So I just grepped those > files out of the "source list".
This is apparently a bug in the 3.4 version of sched-ebb.c. This whole file should be in a #ifdef INSN_SCHEDULING, just like the other sched-*.c files. This is fixed in current GCC. > Next, a stack of libiberty files were not compiled - strcasecmp, > vasprintf, asprintf, getpagesize, strdup. I don't know why this > would be the case, because e.g. HAVE_STRCASECMP is > not defined. Anyway, I added them to the source list manually, > and with a script, awk and m4, I was able to produce my > traditional compile script (which is a stepping stone for doing > the same thing on MVS). The libiberty configure process attempts to detect which functions need to be built via link tests by default. As you don't have a cross-linker, something may be going wrong here. As an alternative, you can hard-code which functions to use in libiberty's configure.ac. > Oh, one other change I made - I normally define PREFIX in a > common header file. However, this caused a conflict between > prefix.c and regex.c which both try to use this keyword. It > would be good if this define was made unique within the > source base. I realise there are different ways around this, > but it would still be good to be unique. For now I just updated > prefix.c to use "" as a default prefix if none is provided. That's > neater than any immediate alternative I can think of. Why would you define this by hand? The usual make process will define PREFIX while building prefix.c, using the appropriate value determined at configure time ... Bye, Ulrich -- Dr. Ulrich Weigand GNU Toolchain for Linux on System z and Cell BE ulrich.weig...@de.ibm.com
