From: Nick Stokes <randomaccessiterator@gmail.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: g++ cross distro compilation problem
Date: Thu, 20 Jan 2011 15:53:00 -0000 [thread overview]
Message-ID: <AANLkTinGAdT=3MQXz_q-5TEm=SbwUGEMB0X3+CLT4C6o@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=CwVi2NRb1UOUXruOUwsXbyKdvbk5o+yj-95VW@mail.gmail.com>
On Wed, Jan 19, 2011 at 7:47 PM, Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
> On 19 January 2011 23:27, Nick Stokes wrote:
>>
>> Ian, you are right on. The versions are different:
>> compute node (where gcc is built): /lib64/libc-2.5.so
>> login node (where gcc is used): /lib64/libc-2.11.2.so
>>
>> Jonathan, I looked at the config.logs (attached). Both seem to use gnu.
>
> Yes, both your distros have a new enough glibc, so the problem might be simpler:
> does it make any difference if you define _GNU_SOURCE when compiling?
>
Assuming you are referring to compiling a code with g++ (and not
compiling gcc itself), then no it doesn't make a difference. (in fact,
g++ -v shows that _GNU_SOURCE is already defined).
Could it be some other silly mistake on my part, e.g forgetting to set
an environment variable or something? Indeed there is the distro's g++
compiler installed on the login node, and most of these headers --
that are potentially incompatible with the gcc versions I am trying to
install under /opt -- are under common places /usr/include etc.
>
> The GNU model, which requires glibc 2.3 or later, supports a
> per-thread locale (via the uselocale function) so that the locale can
> be changed temporarily by the C++ runtime library without affecting
> the global process-wide locale. I believe this avoids possible race
> conditions in multithreaded programs which make use of locales.
>
I see. Thanks for this info, it seems I should not be using generic
locale then.
- Nick
next prev parent reply other threads:[~2011-01-20 15:53 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
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 [this message]
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='AANLkTinGAdT=3MQXz_q-5TEm=SbwUGEMB0X3+CLT4C6o@mail.gmail.com' \
--to=randomaccessiterator@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=jwakely.gcc@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).