Re: [OE-core] [PATCH v4 02/12] acpica: work around flex 2.6.2 code generation issue

2017-01-30 Thread Khem Raj
On Mon, Jan 30, 2017 at 11:53 AM, Denys Dmytriyenko wrote: > On Sat, Jan 21, 2017 at 08:00:13PM -0800, Khem Raj wrote: >> On Fri, Jan 20, 2017 at 6:54 AM, Patrick Ohly wrote: >> > On Fri, 2017-01-20 at 15:12 +0100, Patrick Ohly wrote: >> >> Without this

Re: [OE-core] [PATCH v4 02/12] acpica: work around flex 2.6.2 code generation issue

2017-01-30 Thread Denys Dmytriyenko
On Sat, Jan 21, 2017 at 08:00:13PM -0800, Khem Raj wrote: > On Fri, Jan 20, 2017 at 6:54 AM, Patrick Ohly wrote: > > On Fri, 2017-01-20 at 15:12 +0100, Patrick Ohly wrote: > >> Without this patch, linking fails with a missing implementation of > >> yy_scan_string. This

Re: [OE-core] [PATCH v4 02/12] acpica: work around flex 2.6.2 code generation issue

2017-01-21 Thread Khem Raj
On Fri, Jan 20, 2017 at 6:54 AM, Patrick Ohly wrote: > On Fri, 2017-01-20 at 15:12 +0100, Patrick Ohly wrote: >> Without this patch, linking fails with a missing implementation of >> yy_scan_string. This looks like a regression in flex, because 2.6.0 generated >> different

Re: [OE-core] [PATCH v4 02/12] acpica: work around flex 2.6.2 code generation issue

2017-01-20 Thread Patrick Ohly
On Fri, 2017-01-20 at 15:12 +0100, Patrick Ohly wrote: > Without this patch, linking fails with a missing implementation of > yy_scan_string. This looks like a regression in flex, because 2.6.0 generated > different code that called PrParser_scan_string > resp. DtParser_scan_string. > > Working

[OE-core] [PATCH v4 02/12] acpica: work around flex 2.6.2 code generation issue

2017-01-20 Thread Patrick Ohly
Without this patch, linking fails with a missing implementation of yy_scan_string. This looks like a regression in flex, because 2.6.0 generated different code that called PrParser_scan_string resp. DtParser_scan_string. Working around that in acpica until this is better understood or fixed in