Tom Wurgler wrote:
I am running HP-UX 11.0 and am attempting to build gcc and gpc. I can build the gcc fine by itself, but when I attempt gcc with gpc, I get the failure listed below.
I am trying to build gcc 3.2.1 and the alpha version of gpc-20030209. I start with a freshly unpacked gcc, then unpack the gpc and move the "p" directory into the gcc subdir of the build dir. Is all this correct?
Yes (assuming you mean the source directory, which should
I know about the quadlib path bug in gcc 3.2.1.
Well, I don't. ;-)
cc1: warning: -g is only supported when using GAS on this processor, cc1: warning: -g option disabled
So cc1 (i.e., GCC) is giving this warning already.
../.././xgpc -B../.././ -I../.././p/rts -I. -W -Wall -Wpointer-arith -Wwrite-strings -Wmissing-prototypes -Wmissing-declarations -g -O2 --unit-path=/u/rdstt1/t901353/src/gcc-3.2.1/gcc/p/rts --automake --print-needed-options "/u/rdstt1/t901353/src/gcc-3.2.1/gcc/p/rts/endian.pas" 2> "needed-options" || true if grep -v '^--' "needed-options" > /dev/null; then echo "needed-options: `cat "needed-options"`" >&2; rm -f "needed-options"; false; else true; fi needed-options: gpc1: warning: -g is only supported when using GAS on this processor, gpc1: warning: -g option disabled
And GPC just checks for it.
The solution seems to be to avoid using `-g' (i.e., `CFLAGS="-O2"', something without `-g', or with an explicit `-g0' if necessary), or to install gas (if it supports this target).
Frank