All of lore.kernel.org
 help / color / mirror / Atom feed
From: Terry Barnaby <terry@beam.ltd.uk>
To: openembedded-devel@linuxtogo.org
Subject: Re: [Openembedded-users] Problem with building angstrom-2008.1 for at91sam9m10g45ek
Date: Wed, 16 Mar 2011 14:05:27 +0000	[thread overview]
Message-ID: <4D80C3A7.9030704@beam.ltd.uk> (raw)

-------- Original Message --------
Subject: Re: [Openembedded-users] Problem with building angstrom-2008.1 for
at91sam9m10g45ek
Date: Wed, 16 Mar 2011 00:45:30 -0700
From: Khem Raj <raj.khem@gmail.com>
To: openembedded-users@linuxtogo.org

On 3/16/2011 12:18 AM, Terry Barnaby wrote:
> On 03/15/2011 02:23 PM, Terry Barnaby wrote:
>> On 03/15/2011 01:03 PM, Ludovic Desroches wrote:
>>> Hello,
>>>
>>> On 3/15/2011 1:36 PM, Terry Barnaby wrote:
>>>> Hi,
>>>>
>>>> I am trying to build angstrom-2008.1 for a at91sam9m10g45ek but am
>>>> having
>>>> an error.
>>>>
>>>> NOTE: Applying patch 'tclprivate.diff'
>>>> (openembedded/recipes/tcltk/tcl-8.5.8/tclprivate.diff)
>>>> NOTE: Applying patch 'mips-tclstrtod.patch'
>>>> (openembedded/recipes/tcltk/tcl-8.5.8/mips-tclstrtod.patch)
>>>> ERROR: Task 693
>>>> (virtual:native:/scratch/OpenEmbedded/openembedded/recipes/tcltk/tcl_8.5.8.bb,
>>>>
>>>> do_patch) failed with exit code 1
>>>> FATAL: Execution of 'quilt
>>>> --quiltrc=/scratch/OpenEmbedded/tmp/sysroots/i686-linux/usr/bin/quiltrc
>>>> push'
>>>> failed with exit code 1:
>>>> Applying patch mips-tclstrtod.patch
>>>> patch: **** rejecting target file name with ".." component:
>>>> ../generic/tclStrToD.c
>>>> Patch mips-tclstrtod.patch does not apply (enforce with -f)
>>>
>>> The problem seems to be only with the last patch applied onto tcl
>>> sources. Since
>>> it concerns only MIPS architecture, you can skip it for your ARM chip by
>>> removing into tcl_8.5.8.bb the line
>>> file://mips-tclstrtod.patch;striplevel=0 \
>>>
>>> It doesn't solve the problem but then you could continue. You have a
>>> look on the
>>> sources to see if the patches can be applied, maybe the problem is
>>> the patch level.
>>>
>>>
>>> Regards
>>>
>>> Ludovic Desroches
>>>
>>>
>>> _______________________________________________
>>> Openembedded-users mailing list
>>> Openembedded-users@linuxtogo.org
>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-users
>> Hi Ludovic,
>>
>> Thanks, that has allowed the build to continue, I will see what happens.
>>
>> Cheers
>>
>>
>> Terry
>>
>> _______________________________________________
>> Openembedded-users mailing list
>> Openembedded-users@linuxtogo.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-users
>
> Should I report this as an OpenEmbedded bug somewhere ?

please forward this to openembedded-devel@lists.openembedded.org

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



             reply	other threads:[~2011-03-16 14:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-16 14:05 Terry Barnaby [this message]
2011-03-16 15:20 ` [Openembedded-users] Problem with building angstrom-2008.1 for at91sam9m10g45ek Tom Rini
2011-03-16 15:27   ` Gary Thomas

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=4D80C3A7.9030704@beam.ltd.uk \
    --to=terry@beam.ltd.uk \
    --cc=openembedded-devel@linuxtogo.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.