public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Michael Craft <mcraft@peak15.org>
To: Ian Lance Taylor <iant@google.com>, gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Compiling with OpenMP support.
Date: Thu, 29 Jan 2009 00:57:00 -0000	[thread overview]
Message-ID: <453a08ae0901281657i4caab883sb4272653e36805ac@mail.gmail.com> (raw)
In-Reply-To: <m3fxj358e2.fsf@google.com>

I think you mean to enable OpenMP support on a specific program, use
the -fopenmp option when you are compiling a program. I know this, but
when I do it, it gives me errors about not being able to find libgomp,
like GCC its self was not compiled with OpenMP support. Is there
something I need to do at the time I compile GCC to enable it to
compile OpenMP programs?

Or do you mean something like doing "./configure -fopenmp" or "make
-fopenmp" when I compile GCC?

On Wed, Jan 28, 2009 at 6:16 PM, Ian Lance Taylor <iant@google.com> wrote:
> Michael Craft <mcraft@peak15.org> writes:
>
>> On Wed, Jan 28, 2009 at 3:54 PM, Ian Lance Taylor <iant@google.com> wrote:
>>> Michael Craft <mcraft@peak15.org> writes:
>>>
>>>> I'm trying to compile GCC 3.4.2 with OpenMP support. How can I enable
>>>> this at compile time?
>>>
>>> gcc 3.4.2 does not support OpenMP.  The first version of gcc which
>>> supported OpenMP was gcc 4.2.
>>
>> Woops, EXTREME TYPO! I meant 4.3.2. I am using GCC 4.3.2.
>
> Ah.  In that case, use the -fopenmp option.
>
> Ian
>

  reply	other threads:[~2009-01-29  0:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-28 20:43 Michael Craft
2009-01-28 20:54 ` Ian Lance Taylor
2009-01-28 23:01   ` Michael Craft
2009-01-28 23:16     ` Ian Lance Taylor
2009-01-29  0:57       ` Michael Craft [this message]
2009-01-29  1:05         ` Ian Lance Taylor

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=453a08ae0901281657i4caab883sb4272653e36805ac@mail.gmail.com \
    --to=mcraft@peak15.org \
    --cc=gcc-help@gcc.gnu.org \
    --cc=iant@google.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).