netbase-4.47 vs. -5.0 build breakage

netbase-4.47 vs. -5.0 build breakage

[Thilo Fromm]

Hi guys,

is anything happening to fix the current build breakage against
oe-core? oe-core moved on to netbase-5.0, meta-texasinstruments is
still referring to netbase-4.47 with a .bbappend. Andreas Müller
submitted a patch on 9th of July which fixes this. Please apply the
patch; currently the meta-ti build is broken.

Regards,
Thilo

-- 
Dipl.-Ing (FH) Thilo Fromm, MSc., Embedded Systems Architect
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, D-10319 Berlin, Germany
Tel: +49 (30) 515 932 228   mailto:fromm@dresearch-fe.de
Fax: +49 (30) 515 932 77    http://www.dresearch.de
Amtsgericht: Berlin Charlottenburg, HRB 130120 B
Ust.-IDNr. DE273952058
Geschäftsführer: Dr. M. Weber, W. Mögle

Re: netbase-4.47 vs. -5.0 build breakage

[Denys Dmytriyenko]

On Fri, Jul 13, 2012 at 04:47:22PM +0200, Thilo Fromm wrote:
> Hi guys,
> 
> is anything happening to fix the current build breakage against
> oe-core? oe-core moved on to netbase-5.0, meta-texasinstruments is
> still referring to netbase-4.47 with a .bbappend. Andreas M??ller
> submitted a patch on 9th of July which fixes this. Please apply the
> patch; currently the meta-ti build is broken.

Thilo,

People do have vacations, you know, hence the 4-day delay. It is now in.

--
Denys

Re: netbase-4.47 vs. -5.0 build breakage

[Koen Kooi]

Op 14 jul. 2012, om 01:30 heeft Denys Dmytriyenko het volgende geschreven:

> On Fri, Jul 13, 2012 at 04:47:22PM +0200, Thilo Fromm wrote:
>> Hi guys,
>> 
>> is anything happening to fix the current build breakage against
>> oe-core? oe-core moved on to netbase-5.0, meta-texasinstruments is
>> still referring to netbase-4.47 with a .bbappend. Andreas M??ller
>> submitted a patch on 9th of July which fixes this. Please apply the
>> patch; currently the meta-ti build is broken.
> 
> Thilo,
> 
> People do have vacations, you know, hence the 4-day delay. It is now in.

Now that master is broken with denzil, can we have a branch to track yocto 1.2/denzil please?

Re: netbase-4.47 vs. -5.0 build breakage

[Denys Dmytriyenko]

On Sat, Jul 14, 2012 at 08:32:09AM +0200, Koen Kooi wrote:
> 
> Op 14 jul. 2012, om 01:30 heeft Denys Dmytriyenko het volgende geschreven:
> 
> > On Fri, Jul 13, 2012 at 04:47:22PM +0200, Thilo Fromm wrote:
> >> Hi guys,
> >> 
> >> is anything happening to fix the current build breakage against
> >> oe-core? oe-core moved on to netbase-5.0, meta-texasinstruments is
> >> still referring to netbase-4.47 with a .bbappend. Andreas M??ller
> >> submitted a patch on 9th of July which fixes this. Please apply the
> >> patch; currently the meta-ti build is broken.
> > 
> > Thilo,
> > 
> > People do have vacations, you know, hence the 4-day delay. It is now in.
> 
> Now that master is broken with denzil, can we have a branch to track yocto 
> 1.2/denzil please?

Yes, I was going to branch off of
http://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/tag/?id=v2012.05-yocto1.2

-- 
Denys

Re: netbase-4.47 vs. -5.0 build breakage

[Koen Kooi]

Op 14 jul. 2012, om 08:50 heeft Denys Dmytriyenko het volgende geschreven:

> On Sat, Jul 14, 2012 at 08:32:09AM +0200, Koen Kooi wrote:
>> 
>> Op 14 jul. 2012, om 01:30 heeft Denys Dmytriyenko het volgende geschreven:
>> 
>>> On Fri, Jul 13, 2012 at 04:47:22PM +0200, Thilo Fromm wrote:
>>>> Hi guys,
>>>> 
>>>> is anything happening to fix the current build breakage against
>>>> oe-core? oe-core moved on to netbase-5.0, meta-texasinstruments is
>>>> still referring to netbase-4.47 with a .bbappend. Andreas M??ller
>>>> submitted a patch on 9th of July which fixes this. Please apply the
>>>> patch; currently the meta-ti build is broken.
>>> 
>>> Thilo,
>>> 
>>> People do have vacations, you know, hence the 4-day delay. It is now in.
>> 
>> Now that master is broken with denzil, can we have a branch to track yocto 
>> 1.2/denzil please?
> 
> Yes, I was going to branch off of
> http://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/tag/?id=v2012.05-yocto1.2

I was thinking of using 30fb40ebc13614a74c2e237927c60ac43e01d1bc

That would save me from send a huge pull request :)

regards,

Koen