Re: [OE-core] [PATCH 3/5] x264: Use updated gnu-config artifacts

Huh, I was hoping that passing a path would just force it. Maybe we should stop the script being so "clever". Ross On 19 March 2018 at 17:48, Khem Raj wrote: > On Mon, Mar 19, 2018 at 10:23 AM, Burton, Ross > wrote: > > On 19 March 2018 at 16:54,

Re: [OE-core] [PATCH 3/5] x264: Use updated gnu-config artifacts

On Mon, Mar 19, 2018 at 10:23 AM, Burton, Ross wrote: > On 19 March 2018 at 16:54, Khem Raj wrote: >> >> this only works if the system uses autotools >> in full respect. x264 has a hand woven configure >> but rely on other parts of autotools. So we have

Re: [OE-core] [PATCH 3/5] x264: Use updated gnu-config artifacts

On 19 March 2018 at 16:54, Khem Raj wrote: > this only works if the system uses autotools > in full respect. x264 has a hand woven configure > but rely on other parts of autotools. So we have to > stay with proposed solution. > gnu-configize should be sufficiently dumb that

Re: [OE-core] [PATCH 3/5] x264: Use updated gnu-config artifacts

On Mon, Mar 19, 2018 at 4:36 AM, Burton, Ross wrote: > On 17 March 2018 at 03:40, Khem Raj wrote: >> >> It is not using autoconf completely, therefore there >> is no autoreconf happening, so when we depend on latest >> gnu-config changes e.g. new

Re: [OE-core] [PATCH 3/5] x264: Use updated gnu-config artifacts

Thanks for the tip! On Mon, Mar 19, 2018 at 4:37 AM Burton, Ross wrote: > On 17 March 2018 at 03:40, Khem Raj wrote: > >> It is not using autoconf completely, therefore there >> is no autoreconf happening, so when we depend on latest >> gnu-config

Re: [OE-core] [PATCH 3/5] x264: Use updated gnu-config artifacts

On 17 March 2018 at 03:40, Khem Raj wrote: > It is not using autoconf completely, therefore there > is no autoreconf happening, so when we depend on latest > gnu-config changes e.g. new architectures like riscv > the build does not see them and fails. > > Installing these