All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marko Katić" <dromede@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: gcc-4.7.inc wrong FILESPATH setting?
Date: Fri, 14 Dec 2012 17:49:41 +0100	[thread overview]
Message-ID: <1355503781.9104.27.camel@dromedary> (raw)
In-Reply-To: <CAOHjBZvW_wovoRDXuk=sbc-sgf64zLjsZYwDv+1UnXgkrLE_Nw@mail.gmail.com>

On Fri, 2012-12-14 at 17:41 +0100, Giuseppe Condorelli wrote:
> Hi All,
>  
> I've seen that, in the given .inc file, the FILESPATH is statically
> set to
>  
> FILESPATH = "${FILE_DIRNAME}/gcc-4.7"
>  
> This seems to avoid any FILESEXTRAPATHS_prepend usage on append file.
> I need to add further patches for gcc-4.7.2 in my own meta layer but
> if I set the FILESEXTRAPATHS_prepend as usual
> nothing happens, sources are taken only from the directory set by
> FILESPATH.
> Also I saw this setting was different in the past
> 
> FILESPATH = "${@base_set_filespath([ '${FILE_DIRNAME}/gcc-4.7' ], d)}"
>  
> Comments are welcome.
> Cheers,
> Giuseppe
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

I can confirm this. I also have patches for gcc-4.7.2 in my personal layer and i
also used FILESEXTRAPATHS_prepend in my bbappend files to add them. This used
to work before but now it seems as though FILESEXTRAPATHS_prepend is being
ignored.




  reply	other threads:[~2012-12-14 17:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-14 16:41 gcc-4.7.inc wrong FILESPATH setting? Giuseppe Condorelli
2012-12-14 16:49 ` Marko Katić [this message]
2012-12-14 16:58   ` Robert P. J. Day
2012-12-14 17:07     ` Giuseppe Condorelli
2012-12-14 17:09       ` Robert P. J. Day
2012-12-17 13:51         ` Giuseppe Condorelli
2012-12-19 10:45           ` Paul Eggleton
2013-01-04  8:32             ` Giuseppe Condorelli

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=1355503781.9104.27.camel@dromedary \
    --to=dromede@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 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.