> On Thu, 23 Oct 2025, Siddhesh Poyarekar wrote:
>
> > IMO the best way forward here would be adding a configure check for
> > libxml2 specifically for libgcobol (and maybe gcc/cobol if the
> > frontend needs it too).
Siddhesh, thanks. In the specific, you're talking about
AC_SEARCH_LIBS
I think I can do that, but
> On Thu, 23 Oct 2025 15:32:20 +0000 (UTC)
> Joseph Myers <[email protected]> wrote:
>
> > Note that a configure test for target libxml2 as used by libgcobol
> > (as opposed to one for host libxml2 if needed by the compiler) can
> > only happen at a fairly late stage (i.e. when configuring libgcobol
> > for each multilib; libxml2 availability may vary between multilibs;
> > before then, there might not be a compiler for the target at all to
> > use in running such a configure test).
I wish I knew what that means for me, Joseph. IIUC the definition of
"exists" depends on a target combination of architecture and multilib
flavor. If that means searching for a library that supports
xmlSAXUserParseMemory
and using
ac_cv_search_xmlSAXUserParseMemory
then fine. If it's more than that, I don't know what to do.
I do what I know how to (fsvo "know") and we can carry on from there.
Maybe you're just saying that the test comes late, so the user won't
find out until late. Technology, right?
--jkl
