From: Ian Lance Taylor <iant@google.com>
To: Nick Stokes <randomaccessiterator@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: g++ cross distro compilation problem
Date: Wed, 19 Jan 2011 00:57:00 -0000 [thread overview]
Message-ID: <mcripxlbtha.fsf@google.com> (raw)
In-Reply-To: <AANLkTi=Et26_0c0sU4S+6b-cA_=YXA2_Mt0tiN3VUTsd@mail.gmail.com> (Nick Stokes's message of "Tue, 18 Jan 2011 19:39:27 -0500")
Nick Stokes <randomaccessiterator@gmail.com> writes:
> The current distro versions of GCC (4.5.0 for login, and 4.1.2 for
> computes) are incompatible and insufficient anyway since we need to
> maintain multiple versions of GCC to address user needs. The idea was
> to install all of 4.3, 4.4 and 4.5 versions on different prefixes
> (/opt/gcc/4.3, /opt/gcc/4.4 and /opt/gcc/4.5, respectively) and NFS
> mount these on the login node for users.
>
> We stage the compilers, install, and test them on the compute nodes.
> Everything seems ok. But on the login node the C++ compiler spits out
> the following errors (for a simple hello world program):
This must have something to do with the different versions of glibc
being used on the different machines. I'm not sure what the exact
problem is, though.
Ian
next prev parent reply other threads:[~2011-01-19 0:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 0:39 Nick Stokes
2011-01-19 0:57 ` Ian Lance Taylor [this message]
2011-01-19 1:14 ` Jonathan Wakely
2011-01-19 1:17 ` Jonathan Wakely
2011-01-19 23:27 ` Nick Stokes
2011-01-20 0:47 ` Jonathan Wakely
2011-01-20 15:53 ` Nick Stokes
2011-01-20 16:40 ` Jonathan Wakely
2011-01-20 19:29 ` Nick Stokes
2011-01-20 19:58 ` Jonathan Wakely
2011-01-20 20:01 ` Jonathan Wakely
2011-01-21 0:57 ` Nick Stokes
2011-01-21 2:03 ` Nick Stokes
2011-01-21 9:16 ` Jonathan Wakely
2011-01-21 14:35 ` Nick Stokes
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=mcripxlbtha.fsf@google.com \
--to=iant@google.com \
--cc=gcc-help@gcc.gnu.org \
--cc=randomaccessiterator@gmail.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).