On Tue, 9 Apr 2019, Burton, Ross wrote:
> On Tue, 9 Apr 2019 at 11:14, Robert P. J. Day wrote:
> > so, to confirm what i thought, this is a bug in gnulib which
> > suggests i should dig through the build configuration to see where i
> > can, say, set a PREFERRED_VERSION of a newer version of
On Tue, 9 Apr 2019 at 11:14, Robert P. J. Day wrote:
> so, to confirm what i thought, this is a bug in gnulib which
> suggests i should dig through the build configuration to see where i
> can, say, set a PREFERRED_VERSION of a newer version of gnulib that
> no longer has tat bug? or, barring
On Mon, 8 Apr 2019, Burton, Ross wrote:
> Looks like that bug in gnulib that broke m4 (and others) when glibc
> changed.
>
> Fixed upstream
> https://git.savannah.gnu.org/cgit/gnulib.git/commit/?id=4af4a4a718
> and oe-core master/thud/possibly sumo also carry the relevant patch
> for m4.
>
> If
Looks like that bug in gnulib that broke m4 (and others) when glibc changed.
Fixed upstream
https://git.savannah.gnu.org/cgit/gnulib.git/commit/?id=4af4a4a718
and oe-core master/thud/possibly sumo also carry the relevant patch
for m4.
If you're using older releases against a newer release then
On Mon, 8 Apr 2019, Robert P. J. Day wrote:
>
> a few months ago, i ran into (and asked about) a failure building
> m4-native that you can read here:
>
> https://yocto.yoctoproject.narkive.com/6KyM5UvS/m4-native-zedboard-please-port-gnulib-fseeko-c-to-your-platform
>
> first, i will admit i'm
