From: John Barry <jbarry@eso.org>
To: binutils@sourceware.cygnus.com
Subject: strange compile problem
Date: Mon, 13 Sep 1999 06:54:00 -0000 [thread overview]
Message-ID: <199909131353.PAA11573@osc1.hq.eso.org> (raw)
Hi,
I'm getting this error when I try to build binutils-2.9.5.0.12 with gcc-2.95.1
(compiled for/on a native utrasparc running Solaris 2.6)
SunOS xxx 5.6 Generic_105181-05 sun4u sparc
gcc -DHAVE_CONFIG_H -I. -I../../binutils-2.9.5.0.12/gprof -I. -D_GNU_SOURCE -DDEBUG -I../bfd -I../../binutils-2.9.5.0.12/gprof/../include -I../../binutils-2.9.5.0.12/gprof/../bfd -I../../binutils-2.9.5.0.12/gprof/../intl -I../intl -DLOCALEDIR="\"/apps/gnu2/share/locale\"" -I/usr/openwin/include -I/usr/dt/include -I/apps/include -I/apps/gnu/include -I/apps/X11R6/include -I/apps/gnome/include -I/apps/kde/include -I/apps/ImageMagick/include -O3 -funroll-loops -D_LARGEFILE64_SOURCE=1 -D_FILE_OFFSET_BITS=64 -c ../../binutils-2.9.5.0.12/gprof/hist.c
/var/tmp/ccUupNBD.s: Assembler messages:
/var/tmp/ccUupNBD.s:1963: Error: Illegal operands
/var/tmp/ccUupNBD.s:1986: Error: Illegal operands
/var/tmp/ccUupNBD.s:2008: Error: Illegal operands
/var/tmp/ccUupNBD.s:2100: Error: Illegal operands
*** Error code 1
make: Fatal error: Command failed for target `hist.o'
Current working directory /apps/jbarry/gnu/gcc/bin-build/gprof
This error goes away if I remove the optimisation flag completeley, (even
with -O it still give me assembler errors) but I have my doubts about the
correctness of the code produced in this manner.
This error is reproducable on my system with both a full build:
#!/bin/sh
# This file was generated automatically by configure. Do not edit.
# This directory was configured as follows:
../binutils-2.9.5.0.12/configure --host=sparc-sun-solaris2.6 --prefix=/apps/gnu2
--enable-shared --enable-static --enable-bfd-assembler --enable-commonbfdlib --
enable-64-bit-bfd --with-included-gettext --enable-targets=all --enable-multilib
--enable-threads=posix --with-cpu=ultrasparc --norecursion
# using "mh-frag" and "mt-frag"
and with a seperate config in the gprof dir thus:
# configure --prefix=/apps/gnu2 --enable-shared --enable-static --with-included
-gettext --with-x --x-includes=/usr/openwin/include --x-libraries=/usr/openwin/l
ib
I'm including the compile flags -D_LARGEFILE64_SOURCE=1 -D_FILE_OFFSET_BITS=64
as recommended by Sun to ensure the apps are compliant with 2.6's 64 file
system, it make no difference if I take them out or not, the only thing that
affects it is -O (or not...)
as and ld are gnu-as & gnu-ld from binutils-2.9.1, but I've been getting screwy
errors out the compiler for a few days so I decided to see if upgrading
binutils would help...
I didn't have these problems with the egcs-1.1.2 release, any ideas?
later
jb
----
John Barry
Unix Network Administrator
European Southern Observatory
Karl-Schwarzschild-Strasse 2
D-85748 Garching b. Munchen
Germany
next reply other threads:[~1999-09-13 6:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-13 6:54 John Barry [this message]
1999-09-13 9:12 ` Ian Lance Taylor
1999-09-13 10:14 John Barry
1999-09-13 11:23 ` Ian Lance Taylor
1999-09-13 11:50 John Barry
1999-09-13 11:58 ` Ian Lance Taylor
1999-09-13 12:39 ` Roland McGrath
1999-09-13 12:53 ` Roland McGrath
1999-09-13 13:13 ` John Barry
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199909131353.PAA11573@osc1.hq.eso.org \
--to=jbarry@eso.org \
--cc=binutils@sourceware.cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).