All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Mills <wmills@ti.com>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: meta-ti@yoctoproject.org
Subject: Re: Building Yocto for Pandaboard
Date: Mon, 27 Feb 2012 12:06:09 -0500	[thread overview]
Message-ID: <4F4BB801.3090108@ti.com> (raw)
In-Reply-To: <3A03FCB1-56B0-42C4-9260-24B10EF4531E@dominion.thruhere.net>



On 02/27/2012 11:19 AM, Koen Kooi wrote:
> Op 27 feb. 2012, om 17:06 heeft Philip Balister het volgende geschreven:
>
>> On 02/27/2012 03:50 AM, Koen Kooi wrote:
>>> Op 27 feb. 2012, om 09:26 heeft<Christian.Schulenberg@bmw.de>  <Christian.Schulenberg@bmw.de>  het volgende geschreven:
>>>
>>>> I already added to following line to my local.conf:
>>>>
>>>> BBMASK = ".*/meta-ti/recipes-misc/"
>>>>
>>>> which helps to bypass the first build problem. The next show stopper is building the boot loader (denx version of u-boot):
>>>>
>>>> clocks.c:415:13: internal compiler error: in decode_addr_const, at varasm.c:2632
>>>>
>>>> This seems to be a problem with the used version of gcc. I guess there are two ways to work around this: Use older version of gcc (4.5) or change compiler optimization from -Os to -O0. Unfortunately, neither can I find the right place to switch from gcc 4.6 to 4.5, nor the place to change compiler flags.
>>> Have you read the README in the meta-ti layer yet? That explains how to setup a working environment.
>> The README contains instructions for building Angstrom, which is not the
>> right answer for everyone trying to use meta-ti.
> Since the recipe in question break with gcc 4.6 and/or binutils 2.22 *and* you need SOC_FAMILY in overrides angstrom is the only "out of the box" option. Other routes will involve heavy patching. I agree that needs to be addressed, but it doesn't change the solution *right now*.
>
> And the instructions in the README set things for 'yocto', which is what people are asking for. If they asked for 'poky', that would be a totally different thing.

Denis or Koen:  Before today is over please modify the README.txt to 
describe where we are going and what is possible right now.  If Angstrom 
is the only thing possible right now it should say that until we can 
build with other layer stacks.  However it should also say that we are 
working toward a solution that will build with multiple layer stacks 
including poky.




  reply	other threads:[~2012-02-27 17:06 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-27  8:26 Building Yocto for Pandaboard Christian.Schulenberg
2012-02-27  8:50 ` Koen Kooi
2012-02-27 16:06   ` Philip Balister
2012-02-27 16:19     ` Koen Kooi
2012-02-27 17:06       ` William Mills [this message]
2012-02-27 18:56         ` Denys Dmytriyenko
2012-02-28  7:52         ` Christian.Schulenberg
2012-02-28  7:56           ` Koen Kooi
2012-02-28  8:15             ` Christian.Schulenberg
2012-03-05  8:58               ` Christian.Schulenberg
2012-03-05 13:04                 ` Robert P. J. Day
2012-03-05 14:21                   ` Christian.Schulenberg
2012-03-05 15:16                     ` Robert P. J. Day
2012-03-05 15:29                       ` Christian.Schulenberg
2012-03-05 15:48                         ` Robert P. J. Day
2012-03-05 16:39                     ` Robert P. J. Day
2012-03-05 16:43                       ` Gary Thomas
2012-03-05 16:58                         ` Denys Dmytriyenko
2012-03-05 17:13                           ` Robert P. J. Day
2012-03-05 17:15                             ` Koen Kooi
2012-03-05 20:29                               ` Denys Dmytriyenko
2012-03-05 20:31                                 ` Koen Kooi
2012-03-05 22:28                                   ` Denys Dmytriyenko
2012-03-06  1:39                                     ` Denys Dmytriyenko
2012-03-06  2:20                                       ` Brian Hutchinson
2012-03-05 20:26                             ` Marc Butler
  -- strict thread matches above, loose matches on Subject: below --
2012-02-08 21:58 building " jfabernathy
2012-02-08 22:04 ` Koen Kooi
2012-02-08 22:05 ` Gary Thomas
2012-02-08 22:11   ` jfabernathy
2012-02-08 22:18     ` Koen Kooi
2012-02-08 22:22       ` Gary Thomas
2012-02-08 22:27         ` Koen Kooi
2012-02-08 22:34           ` Gary Thomas
2012-02-08 22:51             ` James Abernathy
2012-02-09  1:16               ` William Mills
     [not found]                 ` <CAFZh4h_dVaOnbYMZjnAc34upJqoPKK4AaPEOEHPTQL6ZEyU-6w@mail.gmail.com>
2012-02-09 16:23                   ` Brian Hutchinson
2012-02-09 16:36                     ` Denys Dmytriyenko
2012-02-09 16:54                       ` Brian Hutchinson
2012-02-09 17:53                         ` Denys Dmytriyenko
2012-02-09 16:59                       ` Philip Balister
2012-02-09 17:05                         ` Brian Hutchinson
2012-02-09 18:17                           ` Jeff Osier-Mixon
2012-02-09 18:20                             ` Denys Dmytriyenko
2012-02-09 18:23                               ` Jeff Osier-Mixon
2012-02-09 17:12                         ` Gary Thomas
2012-02-09 17:15                           ` Denys Dmytriyenko
2012-02-09 17:25                             ` Gary Thomas
2012-02-09 17:14                         ` Denys Dmytriyenko
2012-02-09 13:01               ` Maupin, Chase
2012-02-09 13:11                 ` jfabernathy
2012-02-09 13:54                   ` Koen Kooi
2012-02-09 15:21                     ` Maupin, Chase
2012-02-09 15:33                     ` Richard Purdie
2012-02-09 16:30                       ` jfabernathy
2012-02-09 16:36                         ` Jack Mitchell
2012-02-09 16:53                         ` Philip Balister
2012-02-09 16:57                       ` Denys Dmytriyenko
2012-02-08 22:20     ` 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=4F4BB801.3090108@ti.com \
    --to=wmills@ti.com \
    --cc=koen@dominion.thruhere.net \
    --cc=meta-ti@yoctoproject.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.