> The idea is quite simple. Rather than having a copy of the gcc source for
> each recipe variant
> (-cross-initial, -cross, -crosssdk-initial, -crosssdk, -cross-canadian etc.)
> we have a single copy of the source.
>We tried an older shared stamp scheme which was fragile and prone to weird
On Tue, 2015-09-22 at 11:03 +, Reshetova, Elena wrote:
> > The idea is quite simple. Rather than having a copy of the gcc source for
> > each recipe variant
> > (-cross-initial, -cross, -crosssdk-initial, -crosssdk, -cross-canadian
> > etc.)
> > we have a single copy of the source.
>
>
On Tue, 2015-09-22 at 11:03 +, Reshetova, Elena wrote:
> > The idea is quite simple. Rather than having a copy of the gcc
> > source for each recipe variant (-cross-initial, -cross,
> > -crosssdk-initial, -crosssdk, -cross-canadian etc.) we have a single
> > copy of the source.
>
> >We tried
On Fri, 2015-09-04 at 17:03 +, Reshetova, Elena wrote:
> I have a simple problem but not able to come with simple and elegant
> solution for it, so would be very thankful for the suggestions.
>
> I have a task that is specified to run after do_fetch. The task needs
> the source to be
On Tue, 2015-09-15 at 22:37 -0400, Randy MacLeod wrote:
> I haven't been able to come up with a scheme that works yet.
> With the patch below, I get:
>
> I'll need someone to explain the intent of the gcc-* pkgs
> design or more time to dig though the files and history.
>
> Robert tells me that
On 2015-09-14 01:55 PM, Randy MacLeod wrote:
On 2015-09-09 12:09 PM, Reshetova, Elena wrote:
Maybe we have to fix gcc-source after all rather than use the
EXCLUDE_WORLD
change I made in:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=7878
Should I file a bug about this for easy
On 2015-09-09 12:09 PM, Reshetova, Elena wrote:
Maybe we have to fix gcc-source after all rather than use the EXCLUDE_WORLD
change I made in:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=7878
Should I file a bug about this for easy tracking? My problem really seems
that do_fetch on
On 2015-09-09 12:09 PM, Reshetova, Elena wrote:
>> Maybe we have to fix gcc-source after all rather than use the
>> EXCLUDE_WORLD
> change I made in:
>> https://bugzilla.yoctoproject.org/show_bug.cgi?id=7878
>
> Should I file a bug about this for easy tracking? My problem really
> seems
On Tue, 2015-09-08 at 22:45 -0400, Randy MacLeod wrote:
> Maybe we have to fix gcc-source after all rather than use the
> EXCLUDE_WORLD change I made in:
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=7878
> Does your scheme work for the kernel source? See:
>
> Search for "kernel-devsrc"
On Tue, 2015-09-08 at 22:45 -0400, Randy MacLeod wrote:
> Maybe we have to fix gcc-source after all rather than use the
> EXCLUDE_WORLD change I made in:
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=7878
> Does your scheme work for the kernel source? See:
>
> Search for "kernel-devsrc"
>Maybe we have to fix gcc-source after all rather than use the EXCLUDE_WORLD
change I made in:
>https://bugzilla.yoctoproject.org/show_bug.cgi?id=7878
Should I file a bug about this for easy tracking? My problem really seems
that do_fetch on some related to gcc packages doesn't result in
On 2015-09-04 01:03 PM, Reshetova, Elena wrote:
Hi,
I have a simple problem but not able to come with simple and elegant
solution for it, so would be very thankful for the suggestions.
I have a task that is specified to run after do_fetch. The task needs
the source to be **actually** fetched,
Hi,
I have a simple problem but not able to come with simple and elegant
solution for it, so would be very thankful for the suggestions.
I have a task that is specified to run after do_fetch. The task needs the
source to be *actually* fetched, since it operates on archives. It works
well
13 matches
Mail list logo
