Hello,

i am trying to get running gcc 4.0.0 on a Sun-Blade-1000 sparc host with SunOS 
5.8
for installation path (prefix) /apl/gnu/sol58/gcc/4.0.0.
(Note: i cannot install on /usr/local because its a readonly mount point)

I am using the following GNU components that allready work fine for 
/apl/gnu/sol58/...


# GNU BUILD COMPONENTS under /appl/gnu/sol58 USED FOR COMPILATION
# ===============================================================
#
#   perl                5.6.1
#   gnupg               1.2.4
#   patch               2.5.4
#   m4          1.4.3
#   texinfo             4.2
#   sed         4.1.2
#   pkgconfig   0.15.0
#   autoconf    2.59
#   automake    1.9.5
#   bc          1.06
#   tar         1.15.1
#   gzip                1.2.4a
#   bzip2               1.0.3
#   gettext             0.14.1
#   diffutils           2.8.1
#   flex                2.5.4a
#   bison               2.0
#   gawk                3.1.3
#   grep                2.4.2
#   libiconv    1.9.1
#   make                3.80
#   binutils    2.14
#   gcc         boot compilation        2.95.3 --> 3.4.2 (discarded after 
creating 3.4.2s)
#                       sanity compilation      3.4.2  --> 3.4.2s
#
#   gmp         1.4.1 build the GNU MP 32-bit library as follows:
#               ./configure --with-gnu-ld --enable-mpfr 
--prefix=/apl/gnu/sol58/gmp/4.1.4 ABI=32
#


During Compilation i have seen warnings about nonexisting format parameter "q" 
in name-lookup.c

You can find statements like "error("declaration of %q#D", decl)"
                          or "cp_error_at (%qD is not a function,", f1 )"
                          or "pedwarn ("redeclaration of %<wchar_t> as %qT", 
TREE_TYPE (x));"
( the string "%q" can be found with fgrep 50 times in name-lookup.c )


I have browsed the GNU GCC 4.0.0 bug list and found that name-lookup is broken.
The build was not stopped by above mentioned warnings (that could be the reason 
why it didn't get recognized).
Maybe above information can help fixing the problem.


kind regards
  Daniel Wyss


Reply via email to