Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Steffen Sledz <sledz@dresearch.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] epiphany-2.30.2: unbreak build by disabling CA files
Date: Thu, 30 Sep 2010 17:00:48 +0200	[thread overview]
Message-ID: <4CA4A620.6080104@dresearch.de> (raw)
In-Reply-To: <1285858596.3805.111.camel@mattotaupa>

Am 30.09.2010 16:56, schrieb Paul Menzel:
> Am Donnerstag, den 30.09.2010, 10:10 +0200 schrieb Steffen Sledz:
>> Signed-off-by: Steffen Sledz <sledz@dresearch.de>
> 
> What is your build error?
> 
> Building `epiphany-2.30.2-r2` with `MACHINE = "beagleboard"` for minimal
> (eglibc) worked for me.

see <http://tinderbox.openembedded.net/packages/797336/>

> Besides that would PR need to be increased?

Not sure, but i can do that of course.

Steffen




  reply	other threads:[~2010-09-30 15:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-27 19:37 testing branch 2010-09-27 Cliff Brake
2010-09-30  8:08 ` Steffen Sledz
2010-09-30  8:10   ` [PATCH] epiphany-2.30.2: unbreak build by disabling CA files Steffen Sledz
2010-09-30 14:56     ` Paul Menzel
2010-09-30 15:00       ` Steffen Sledz [this message]
2010-10-01 16:05     ` Steffen Sledz
2010-10-01 16:26       ` Khem Raj
2010-10-01 22:11         ` Paul Menzel
2010-10-01 23:13           ` Khem Raj
2010-10-01 23:14             ` Khem Raj
2010-10-04  7:10               ` [PATCH v2] " Steffen Sledz
2010-10-04 10:50                 ` [PATCH v3] epiphany-2.30.2: unbreak build by adding ca-certificates dependencies Steffen Sledz
2010-10-04 10:51                   ` Steffen Sledz
2010-10-04 11:53                   ` Koen Kooi
  -- strict thread matches above, loose matches on Subject: below --
2011-01-12 10:01 epiphany still broken Steffen Sledz
2011-01-12 10:09 ` [PATCH] epiphany-2.30.2: unbreak build by disabling CA files Steffen Sledz
2011-01-12 10:20   ` Graeme Gregory

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=4CA4A620.6080104@dresearch.de \
    --to=sledz@dresearch.de \
    --cc=openembedded-devel@lists.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