I'm sorry to say this, but I've the impression that you are
just attempting to blindly skip build issues one at each time
without any real effort for understanding what's really
happening, and that's not good at all.
first of all, we absolutely need to clear up a dangerous
"Do you I required specific version of proj, geos, sqlite
version to build libspatialite-5.0.1?"
absolutely no, because 5.0.1 is able to interact
with a wide range of different versions.
but you must necessarily update your super-Makefile
so to be able to adequately support the more recent
versions of all required libraries.
each time that you'll get some compilation error
the right action cannot be "gosh, I've to disable
something" but instead "why this is failing ?
what I'm expected to correct or integrate so
to resolve this issue ?"
general remark: your super-Makefile is not at all
bad, but is surely become obsolete or inaccurate
in many ways. just few exemples:
- you are keeping disabled libxml2, but I'm unable
to see any good reason for doing such a thing,
because libxml2 has no further dependency and
usually builds without any problem.
I suppose that you simply have to add few lines
in your super makefile in order to build it
then enabling it.
- the same is for librrtopo, that just depends
- your super makefile configures PROJ-6.3.0 that
is nowadays badly outdated, the current version
note: recent versions of PROJ strictly require
to be supported by libcurl and libgeotiff,
and both them are lacking in your configuration
- final remark: an error message like "undefined
symbol _sqlite3_enable_load_extension" usually
means that libsqlite3 was incorrectly built by
disabling dynamic extensions.
conclusions: your porting of libspatialite for
iOS is surely affected by several troubles of
different origins that patiently requiring
to be solved one at each time.
prepare yourself for a long debugging/updating
session patiently fixing a library after the
useful resources: please carefully study my build
recipes for MinGW on Windows  .
yes, iOS actually is a very different platform,
but they'll surely help you to better understand
the complex chain of dependencies and the more
recent specific requirements of each library.