All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: gcc errors while building core-image-sato-sdk
Date: Fri, 06 Jul 2012 10:23:52 -0700	[thread overview]
Message-ID: <4FF71F28.70302@linux.intel.com> (raw)
In-Reply-To: <CAMKF1so=LN+cXK37B9Eu1msE-kmVUJDkSzvcCLm9jSFNDaZM_w@mail.gmail.com>

On 07/06/2012 09:00 AM, Khem Raj wrote:
> On Fri, Jul 6, 2012 at 1:55 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
>>
>> I merged a couple of gcc changes fairly quickly to address a variety of
>> problems people started hitting (including the autobuilder). The svn
>> nature of the recipe is causing a few issues with the subversion 1.7
>> change. I am wondering if we should just point it to the svn checkout
>> tarball by default and leave the svn url for use when updating only and
>> populating the mirror?
>
> or we can use git instead of svn. http://gcc.gnu.org/git/?p=gcc.git
>
That sounds like a good idea.

Sau!

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




  reply	other threads:[~2012-07-06 17:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-04 12:55 gcc errors while building core-image-sato-sdk Damian, Alexandru
2012-07-04 14:32 ` Mihai Lindner
2012-07-04 14:45   ` Richard Purdie
2012-07-04 14:50     ` Damian, Alexandru
2012-07-04 15:02       ` Richard Purdie
2012-07-04 15:06         ` Damian, Alexandru
2012-07-04 15:21           ` Martin Jansa
2012-07-05  6:51             ` Damian, Alexandru
2012-07-05 20:03               ` Khem Raj
2012-07-06  8:55                 ` Richard Purdie
2012-07-06 16:00                   ` Khem Raj
2012-07-06 17:23                     ` Saul Wold [this message]
2012-07-07  0:54                       ` Khem Raj

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=4FF71F28.70302@linux.intel.com \
    --to=sgw@linux.intel.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 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.