Bug report for gcc 2.95.2 compilation on i386-pc-solaris2.7

[G. Liu]

Hi there,

I have gcc 2.95.1 running on an i386-pc-solaris2.7 system and I'm trying
to compile 2.95.2 on it. GNU make is installed as /usr/local/bin/gmake and
I set up the environment variable MAKE to gmake. The "configure" scripts
correctly identifies it as the make to use. I have versoin 2.9.1 of GNU as
installed at /usr/local/i386-pc-solaris2.7/bin/as.

I have the most recent versions of m4, autoconf, automake, texinfo just
compiled and installed to /usr/local/bin and "configure" finds them
without any problem.

The _objdir_ is called build-x86, and _srcdir_ is gcc-2.95.2. I used

../gcc-2.95.2/configure --with-gnu-as

to do the configuration and use "make bootstrap" to compile it. After the
compilation finished in gcc/intl/, it fails with the following complaint:

echo "void __foo () {}" > dummy.c
./xgcc -B/usr/local/i386-pc-solaris2.7/bin/ -B./
-I/usr/local/i386-pc-solaris2.7/include  -DIN_GCC     -g -I./include  -c dummy.c
/usr/local/i386-pc-solaris2.7/bin/as: option `-s' is ambiguous
gmake[2]: *** [libgcc1.null] Error 1
gmake[2]: Leaving directory `/home/isl031/system-stuff/gcc/build-x86/gcc'
gmake[1]: *** [bootstrap] Error 2
gmake[1]: Leaving directory `/home/isl031/system-stuff/gcc/build-x86/gcc'
make: *** [bootstrap] Error 2


Apparently, /usr/local/i386-pc-solaris2.7/bin/as (version 2.9.1 of gas)
does not have a "-s" option. I wonder if this is a bug, or there is
something that I did not do right.


I encounter an assembler problem again on a sparc-sun-sunos4.1.4, too.
Also gcc 2.95.1 running and trying to compile 2.95.2, with gmake, gas, ...
When building gcc/libgcc2.a
(target bootstrap/stmp-multilib/stmp-multilib-sub/libgcc2.a), I got (very
long lines wrapped to multiple lines in my mail composer)


for name in _eh; \
do \
  echo ${name}; \
  ./xgcc -B/usr/local/sparc-sun-sunos4.1.4/bin/ -B./
-I/usr/local/sparc-sun-sunos4.1.4/include -O2   -DIN_GCC -DHAIFA 
-g -I./include 
-g1  -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED    -fexceptions -I.
-I../../gcc-2.95.2/gcc -I../../gcc-2.95.2/gcc/config
-I../../gcc-2.95.2/gcc/../include -c \
      -DL${name} ../../gcc-2.95.2/gcc/libgcc2.c -o ${name}.o; \
  if [ $? -eq 0 ] ; then true; else exit 1; fi; \
  ar rc tmplibgcc2.a ${name}.o; \
  rm -f ${name}.o; \
done
_eh
/tmp/ccZpZeiJ.s: Assembler messages:
/tmp/ccZpZeiJ.s:1260: Error: Unknown pseudo-op:  `.uaword'
/tmp/ccZpZeiJ.s:1262: Error: Unknown pseudo-op:  `.uaword'
/tmp/ccZpZeiJ.s:1276: Error: Unknown pseudo-op:  `.uaword'
/tmp/ccZpZeiJ.s:1278: Error: Unknown pseudo-op:  `.uaword'
/tmp/ccZpZeiJ.s:1279: Error: Unknown pseudo-op:  `.uaword'
/tmp/ccZpZeiJ.s:1280: Error: Unknown pseudo-op:  `.uaword'
/tmp/ccZpZeiJ.s:1282: Error: Unknown pseudo-op:  `.uaword'
.....


Again, don't know if this is a bug or a problem with my setting. Don't see
anything about it in the documentation.

Sincerely,
-Gang