Hi Corbin,
Sorry for the delayed reply.
Please tell me if I should submit this to a different one of the mailing
No, you sent it to the right place. I've never been very familiar with
the cross-compiling niceties, basically just integrating patches from
others. In any case, I think the bottom line is that you'll be a lot
better off waiting for a pretest (hopefully coming in the
not-impossibly-distant future), and/or building from the development
sources, rather than worrying about 4.13. Which predates the existence
of Android.
But anyway, here are some brief replies:
> Does the make flow not build libgnu.a automatically?
Sure, generally it does. Why it didn't in your case is not immediately
apparent to me.
> index.c:52: error: 'mbscasecmp' undeclared here (not in a function)
> I don't see where mbscasecmp.h is being included by any file. How
> is this not normally a problem?
index.c includes mbswidth.h, which probably defined mbscasecmp at the
time, on the systems people tried anyway. I don't recall that ever
being reported before. I suspect it is due to gnulib rearrangements.
> ./sys/time.h:23: error: stray '@' in program
> What normally fills in those @PRAGMA@ lines in the gnulib files?
configure and/or make. Again I suspect the gnulib update you did has
left you with a mix of old and new gnulib stuff.
> I had to update which config.guess and config.sub I used, but I have had
> to do that for just about everything I have built for Android.
Sure. The config.* and other infrastructure files in 4.13 were current
as of the time of the 4.13 release, of course ...
Best,
Karl