public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: niXman <i.nixman@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Some questions about adding mingw support for std::random_device
Date: Fri, 28 Dec 2012 14:12:00 -0000	[thread overview]
Message-ID: <CAH6eHdTr1zj8z2hjEidRihn5Au+Bw2P6=yY51O9HE82_AOnQhw@mail.gmail.com> (raw)
In-Reply-To: <CAMPTgK2qNNXooyo3+d_4DVgYpEEDEfTC46=6CfSQNfTjy3ckcA@mail.gmail.com>

On 28 December 2012 08:05, niXman wrote:
> Hi,
>
> I want to add mingw support for std::random_device and I have a few questions.
>
> 1) When configuring libstdc++, the GLIBCXX_CHECK_RANDOM_TR1 test
> passes successfully, because MSYS is used. But the compiler and the
> programs created by it can not use '/dev/urandom' || '/dev/random',
> because they do not use MSYS-runtime.

As I know nothing about MSYS I don't understand this. Why do the files
exist but can't be used?
Do you mean the files are present on the system where GCC is built,
but not on the system where compiled programs run?

> The first question is, do I need
> to change the GLIBCXX_CHECK_RANDOM_TR1 test itself so that for mingw
> it would be not successful, or I have to add in the file
> 'libstdc++-v3/include/bits/random.h' an additional checking by the
> preprocessor and ignore the value of _GLIBCXX_USE_RANDOM_TR1 macro? I
> think the first variant is more logical because the second variant
> seems to be some cleaning up.

Fixing the test would be better, but if it's not possible to tell
whether the files are usable until runtime then no preprocessor test
can work.

> 2) Since the I'm very new in autotools, tell me please, how should I
> change the GLIBCXX_CHECK_RANDOM_TR1 test?

Change the acinclude.m4 file, then regenerate the other files by
running autoreconf. You'll need the right version of autoconf, which
is 2.64

  reply	other threads:[~2012-12-28 14:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-28  8:05 niXman
2012-12-28 14:12 ` Jonathan Wakely [this message]
2013-01-05 13:25   ` niXman
2013-01-05 15:35     ` Jonathan Wakely
2013-01-05 18:51       ` NightStrike

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='CAH6eHdTr1zj8z2hjEidRihn5Au+Bw2P6=yY51O9HE82_AOnQhw@mail.gmail.com' \
    --to=jwakely.gcc@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=i.nixman@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).