bug-groff
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

groff 1.19.1 build glitches on Solaris 8 with GCC 3.4.0


From: Paul Eggert
Subject: groff 1.19.1 build glitches on Solaris 8 with GCC 3.4.0
Date: Sun, 23 May 2004 00:34:50 -0700
User-agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)

GROFF VERSION:
1.19.1

MACHINE:
Tatung COMPstation U10 (a Sun Ultra 10 clone)

OS:
Solaris 8

COMPILER:
GCC 3.4.0

INPUT FILES:
none

COMMAND LINE:
PSPRINT=lp \
BROKEN_SPOOLER_FLAGS=0 \
LDFLAGS=-R/opt/reb/lib/gcc/gcc-3.4.0/lib \
PAGE=letter \
./configure

make

DESCRIPTION OF INCORRECT BEHAVIOUR:

There are some spurious warnings generated during a build.  I think
they're OK but they're worrisome-looking.

First kind of problem:

gcc -I. -I.  -I/reb/src/base/groff/src/include 
-I/reb/src/base/groff/src/include -DHAVE_CONFIG_H -DSTDC_HEADERS=1 
-fno-for-scope -g -O2  -c getopt.c
cc1: warning: command line option "-fno-for-scope" is valid for C++/ObjC++ but 
not for C

Second kind of problem:

g++ -g -O2 -R/opt/reb/lib/gcc/gcc-3.4.0/lib -o troff dictionary.o  div.o  env.o 
 input.o  majorminor.o  node.o  number.o  reg.o 
/reb/src/base/groff/src/libs/libgroff/libgroff.a  -lm
ld: warning: relocation error: R_SPARC_UA32: file 
/reb/src/base/groff/src/libs/libgroff/libgroff.a(getopt.o): symbol optarg:
        external symbolic relocation against non-allocatable section 
.debug_info;
        cannot be processed at runtime: relocation ignored


The 2nd problem reminds me of a long-ago bug I tried to file against
the Sun linker.  See

http://groups.google.com/groups?selm=6ig3u8%248pg%241%40shade.twinsun.com

Sun has apparently rediscovered this bug using its own compiler; it's
Sun bugs 4910101 and 4910810, filed in September 2003.  There is no
public fix yet.

It's not surprising that the bug would occur with GCC 3.4.0, as GCC
changed the default debug format in the 3.4.0 release.

I have filed a bug report against GCC for generating the message of
the second kind; it's GCC bug #15599.

SUGGESTED FIX [optional]:

I suppose a workaround for the second problem is to not use -g on
Solaris with GCC 3.4.0.  I haven't tested this, though.

For the first problem, I guess -fno-for-scope should not be passed to
C compiles.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]