Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/2] make: add make-replacement-native 3.81
Date: Thu, 16 Aug 2012 23:55:42 +0200	[thread overview]
Message-ID: <20120816215542.GA3625@jama.jama.net> (raw)
In-Reply-To: <CALbNGRQSzVnbgMZXeS2eWONCWbpdDRL3K7kGAJqj2Jq5dERDJw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2027 bytes --]

On Thu, Aug 16, 2012 at 10:30:37PM +0200, Andreas Müller wrote:
> On Wed, Aug 15, 2012 at 11:40 PM, Phil Blundell <philb@gnu.org> wrote:
> > On Wed, 2012-08-15 at 22:17 +0100, Burton, Ross wrote:
> >> On 15 August 2012 22:12, Martin Jansa <martin.jansa@gmail.com> wrote:
> >> > eglibc was failing to build with make-3.81
> >> > https://bugzilla.yoctoproject.org/show_bug.cgi?id=2314
> >> >
> >> > so I guess once this is built (as webkit-gtk dependency), eglibc will maybe sometimes fail again..
> >>
> >> Interesting, this is the first time I've encountered 3.81 having
> >> problems.  So we can't use 3.81 and we can't use 3.82 either. :)
> >
> > You can use 3.81, you just need to install it either under a different
> > name (e.g. call it "make-3.81" and set $MAKE) or in a different
> > directory (e.g. ${bindir}/make-3.81/make and set $PATH) so that other
> > recipes don't pick it up unexpectedly.
> >
> > p.
> >
> The following is really dirty but at least to me it succeeds and to me
> it seems to have less influences than the 'make 3.81 dance':
> 
> # dirty hack for gnu make 3.82 race condition
> do_compile() {
>     if [ x"$MAKE" = x ]; then MAKE=make; fi
>     bbnote make ${PARALLEL_MAKE} "$@"
>     for error_count in 1 2 3; do
>         bbnote "Number of trials: $error_count"
>         exit_code=0
>         make ${PARALLEL_MAKE} "$@" || exit_code=1
>         if [ $exit_code = 0 ]; then
>             break
>         fi
>     done
>     if [ ! $exit_code = 0 ]; then
>         die "oe_runmake failed"
>     fi
> }
> 
> I have make 3.82 and before this I had 100% error at first do_compile.
> For rerun (without cleanup) I had 100% success. Now I get 100% success
> with make called twice. Would something like have a chance to be
> accepted?

Same for me, except I didn't go that far to reexecute make from recipe,
just executing feed build twice in for loop to be sure it will succeed.

Cheers,

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

  reply	other threads:[~2012-08-16 22:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-15 16:18 [PATCH 0/2] Make webkit-gtk depend on make-replacement-native 3.81 Ross Burton
2012-08-15 16:18 ` [PATCH 1/2] make: add " Ross Burton
2012-08-15 21:12   ` Martin Jansa
2012-08-15 21:17     ` Burton, Ross
2012-08-15 21:40       ` Phil Blundell
2012-08-16 20:30         ` Andreas Müller
2012-08-16 21:55           ` Martin Jansa [this message]
2012-08-15 21:39   ` Richard Purdie
2012-08-15 21:44     ` replacement natives - was " Mark Hatle
2012-08-15 16:18 ` [PATCH 2/2] webkit-gtk: add depends on make-replacement-native Ross Burton

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=20120816215542.GA3625@jama.jama.net \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-core@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