This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: GCC ToT boostrap error on hppa64* platform

> I was wondering if anyone is boostrapping the ToT GCC on
> hppa64-hp-hpux11.00.  I am currently getting an error but was thinking
> it might be the version of GCC I am using in the build or it might be an
> issue with using the HP linker.  If others are successfully building
> then I will look at those possibilities first.  If no one else is
> building then maybe it is a recent code change.  I didn't see any ToT
> results in the gcc-testsuite list, only 3.3.1 results.
> The error I get is:
> /extra4/be64/bin/gcc   -g  -DIN_GCC   -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -fno-common   -DHAVE_CONFIG_H -o cc1 \
>         c-parse.o c-lang.o c-pretty-print.o attribs.o c-errors.o c-lex.o c-pragma.o c-decl.o c-typeck.o c-convert.o c-aux-info.o c-common.o c-opts.o c-format.o c-semantics.o c-incpath.o cppdefault.o c-ppoutput.o c-cppbuiltin.o prefix.o c-objc-common.o c-dump.o c-pch.o libcpp.a  main.o libbackend.a ../libiberty/libiberty.a
> ld: Unsatisfied symbol "$$dyncall" in file libbackend.a[expr.o]
> ld: The value 0xfff7fffffffff9c7 does not fit when applying the relocation PCREL21L for symbol "$$dyncall" at offset 0x5f35c in section index 1 of file libbackend.a[expr.o]

I think you should check your bootstrap compiler.  Only the 32-bit port uses
$$dyncall.  I just posted build results for 3.4 and started a new build.
It's past the point where your error occured.

J. David Anglin                        
National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]