Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Dallas Foley <dfoley@telus.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: testing 2010-10-04
Date: Thu, 07 Oct 2010 12:04:33 -0700	[thread overview]
Message-ID: <4CAE19C1.4060406@telus.net> (raw)
In-Reply-To: <AANLkTimOrM-DCsoP4yoo14g_wJ_h0ZVaY99R7UJ=TGmJ@mail.gmail.com>

On 10-10-07 11:26 AM, Khem Raj wrote:
> On Thu, Oct 7, 2010 at 8:34 AM, dfoley<dfoley@telus.net>  wrote:
>> On 10-10-06 03:37 AM, Stefan Schmidt wrote:
>>>
>>> Hello.
>>>
>>> On Tue, 2010-10-05 at 07:50, dfoley wrote:
>>>>
>>>> May not be correct, but I ran into the same problem and patched.
>>>>
>>>> diff --git a/recipes/cacao/cacao.inc b/recipes/cacao/cacao.inc
>>>> index c366b74..70bda75 100644
>>>> --- a/recipes/cacao/cacao.inc
>>>> +++ b/recipes/cacao/cacao.inc
>>>> @@ -23,7 +23,7 @@ EXTRA_OECONF = "\
>>>>         ${@['','--enable-softfloat'][bb.data.getVar('TARGET_FPU',d,1) ==
>>>> 'soft']} \
>>>>         --enable-debug \
>>>>         --with-vm-zip=${datadir}/cacao/vm.zip \
>>>> -       --with-cacaoh=${STAGING_BINDIR_NATIVE}/cacaoh-${PV} \
>>>> +       --with-cacaoh=${STAGING_BINDIR_NATIVE}/cacaoh-${PV}/cacaoh \
>>>>
>>>>   --with-build-java-runtime-library-classes=${STAGING_DATADIR}/classpath/glibj.zip
>>>> \
>>>>       --with-java-runtime-library-classes=${datadir}/classpath/glibj.zip \
>>>>       --with-java-runtime-library-libdir=${libdir_jni}:${libdir} \
>>>
>>> This does it fix for me as well. I wonder from which commit the  directory
>>> change was triggered in the last week.
>>>
>>> Care to send a git formatted patch with PR bump I could apply? As you did
>>> the
>>> work you should get the credits for it. :)
>>>
>>> regards
>>> Stefan Schmidt
>>
>> I don't mind if you commit it. You can put me in signed off by.
>> Should the maintainer (MAINTAINERS file) verify it ?
>
> what would be your sign off? your email does not reveal your full name :)

No need to include me in the sign off.
I believe I've corrected my full name now.

>
>>
>>
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel





  reply	other threads:[~2010-10-07 19:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-04 18:05 testing 2010-10-04 Cliff Brake
2010-10-05 10:27 ` Frans Meulenbroeks
2010-10-05 11:39   ` Frans Meulenbroeks
2010-10-05 14:21     ` Cliff Brake
2010-10-05 12:32 ` Stefan Schmidt
2010-10-05 13:23   ` Frans Meulenbroeks
2010-10-05 14:00     ` Stefan Schmidt
2010-10-05 14:24     ` Cliff Brake
2010-10-05 13:28   ` Koen Kooi
2010-10-05 13:57     ` Stefan Schmidt
2010-10-05 14:50   ` dfoley
2010-10-06 10:37     ` Stefan Schmidt
2010-10-07 15:34       ` dfoley
2010-10-07 18:26         ` Khem Raj
2010-10-07 19:04           ` Dallas Foley [this message]
2010-10-08  5:44             ` Stefan Schmidt

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=4CAE19C1.4060406@telus.net \
    --to=dfoley@telus.net \
    --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