Do I have a bug?

Jim Wilson wilson@specifixinc.com
Fri Feb 20 02:24:00 GMT 2004


Buehler, Bob wrote:
> Make: gmake bootstrap ran and ended with these lines, so I assume it was
> O.K.:
> gmake install produces:
> cc   -g -DIN_GCC     -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-typec
> k.o c-convert.o c-aux-info.o c-common.o c-opts.o c-format.o
> c-semantics.o c-objc-common.o c-dump.o l
> ibcpp.a rs6000-c.o main.o libbackend.a   ../libiberty/libiberty.a
> ld: 0711-317 ERROR: Undefined symbol: .__lshrdi3

gmake install should not have tried to build anything.  The attempted 
build failed because it used the wrong compiler, cc instead of gcc.

This implies that there was a problem with timestamps.  If you 
accidentally touched a file after or during the make bootstrap, it could 
have caused this problem.  If you are using a remote filesystem, such as 
NFS, and the time/date on the server does not match the time/date on the 
client, then you could see a problem like this.  If you have a very fast 
machine, which can compile multiple files in under a second, and the 
version of gmake you have does not handle sub-second timing correctly, 
then you could see this problem.  Check the gmake version number, the 
current docs recommend 3.79.1 or later.

It is better to file bug reports into our bugzilla database than to send 
mail to gcc-bugs.  We don't track bug reports that are emailed, but we 
do track the ones files into the bug database.
-- 
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com



More information about the Gcc-bugs mailing list