Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: openmp in gcc-cross
Date: Tue, 05 Aug 2008 14:26:04 +0200	[thread overview]
Message-ID: <g79gss$vrd$1@ger.gmane.org> (raw)
In-Reply-To: <1217938413.24777.148.camel@mill.internal.reciva.com>

Phil Blundell wrote:
> On Tue, 2008-08-05 at 12:35 +0200, Koen Kooi wrote:
>> It broke builds for some people (but not all).
>
> What was the breakage?  It seems like it would be a better idea to fix
> that than just to disable it.

I wasn't one of the people seeing the breakage, so I'll leave it to the 
people that reported to respond.

regards,

Koen




  reply	other threads:[~2008-08-05 12:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-05  8:19 openmp in gcc-cross Phil Blundell
2008-08-05 10:35 ` Koen Kooi
2008-08-05 12:13   ` Phil Blundell
2008-08-05 12:26     ` Koen Kooi [this message]
2008-08-06  0:57       ` Khem Raj
2008-08-06  7:49         ` Phil Blundell
2008-08-06 10:41           ` Koen Kooi

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='g79gss$vrd$1@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.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