public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paul Mitchell <pmitchel@email.unc.edu>
To: gcc-help@gcc.gnu.org
Subject: Gcc problem
Date: Wed, 12 Oct 2005 19:09:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.44+UNC.0510121505140.26745-100000@ceili> (raw)

Folks,
 I'm a real newbie with Linux, and I've just been assigned to work on a
set of Opterons for a Beowulf cluster.  I've used gcc on the solaris boxes
(and Xserves for that mattera) without a problem, but I'm stuck on the
linux machines.

What am I doing wrong? This occurs on any opteron, and the login baobab
(out Beowulf cluster name) node:

ipm add gcc
Error: already subscribed to package gcc.
baobab$ ipm r gcc
baobab$ ipm add gcc
baobab$ ./configure
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu

Beginning configuration for readline-5.0 for x86_64-unknown-linux-gnu

checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking for C compiler default output... configure: error: C compiler
cannot create executables
See `config.log' for more details.
baobab$

ssh op74
Warning: Permanently added the RSA host key for IP address
'192.168.32.144' to the list of known hosts.
pmitchel@op74's password:
baobab$ cd admin/myrinet/mpichgm-1.2.6..14b
/afs/isis.unc.edu/home/p/m/pmitchel/admin/myrinet/mpichgm-1.2.6..14b
baobab$ ./configure
Configuring MPICH Version 1.2.6 (release) of : 2004/08/04 11:10:38
checking whether filesystem respects case in file names... yes
checking for current directory name...
/afs/isis.unc.edu/home/p/m/pmitchel/admin/myrinet/mpichgm-1.2.6..14b
checking for architecture... LINUX
checking device... ch_p4
checking for install
checking for ranlib
checking gnumake... yes using --no-print-directory
checking whether make supports include... yes
checking OSF V3 make... no
checking for virtual path format... VPATH
checking for xlC
checking for g++
*# C++ compiler g++ failed to compile a simple program
*# C++ interface will not be built with this compiler
checking for c++
*# C++ compiler c++ failed to compile a simple program
*# C++ interface will not be built with this compiler
checking for aCC
checking for CC
checking for cxx
checking for cc... found /usr/bin/cc (cc)
checking that the compiler cc accepts ANSI prototypes... no
*# The compiler cc does not accept ANSI prototypes
checking for gcc... found /afs/isis/pkg/gcc/bin/gcc (gcc)
checking whether cross-compiling... yes
checking that the compiler gcc runs... no
/tmp/cc8ZQSty.s: Assembler messages:
/tmp/cc8ZQSty.s:7: Error: suffix or operands invalid for `push'
/tmp/cc8ZQSty.s:9: Error: suffix or operands invalid for `movq'
/tmp/cc8ZQSty.s:19: Error: suffix or operands invalid for `push'
/tmp/cc8ZQSty.s:21: Error: suffix or operands invalid for `movq'

/afs/isis/pkg/gcc --> /afs/isis/pkg/gcc-343

Of course, anyone else in the place doesn't have this problem...

Any answers will be appreciated,

Paul Mitchell
==============================================================================
	Paul Mitchell
	email: pmitchel@email.unc.edu
	phone: (919) 962-9778
	office: I have an office, room 14, Phillips Hall
==============================================================================



             reply	other threads:[~2005-10-12 19:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-12 19:09 Paul Mitchell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-04-13 13:44 Seyed Abolfazl Mortazavizadeh
2022-04-13 13:57 ` Jonathan Wakely
2001-09-20 18:01 gcc problem mouhcin chergou
2000-09-20  8:32 GCC problem Djoko Djordjevic

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=Pine.GSO.4.44+UNC.0510121505140.26745-100000@ceili \
    --to=pmitchel@email.unc.edu \
    --cc=gcc-help@gcc.gnu.org \
    /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).