Re: Ann: SWI-Prolog 6.6.3 (MacOSX issues)

Jan Wielemaker <[email protected]>
Newsgroups gmane.comp.ai.prolog.swi
Message-ID <[email protected]>
On 03/18/2014 02:32 PM, Jan Wielemaker wrote:
> Hi,
>
> Unlike previously promised, I've released SWI-Prolog 6.6.3 because of
> two issues:
>
>   - Fixed compile with libreadline 6.3 (non-windows versions).
>     Found by Maks Verver.
>   - Fixed another Atom-GC crash, notably triggering on slow hardware.
>     Isolated by Eugeniy Meshcheryakov (Debian maintainer),
>     fixed by Keri Harris.
>
> Also cherry-picked some other obvious fixes and additions from the
> development branch.  See below.
>
> Enjoy --- Jan

Hmmm. Unfortunately the sources do not build using Macports on some
MacOSX versions :-( I found a hack around that. Trying to release
7.1.10, I stumbled on some more MacOSX issues:

  - library(archive) seems badly broken because the MacOSX version is
    something different from what is expected.  Not sure what.  Looks
    like libarchive V2 without headers, so it picks the headers from
    Macports and gets confused due to the mismatched library. I hacked
    around that, now including the Macports version in the binary :-(

  - library(odbc) does not build.  I'm unsure here.  MacOSX Maverics
    still ships with libiodbc.dylib, which is fine for SWI-Prolog, but
    it no longer provides [i]sql.h in its SDK headers!??  How is a
    binary package supposed to provide ODBC support?  Options:

    - Conclude that MacOS no longer supports ODBC?
    - Include Macports unixODBC with all related tools as
      part of the binary distribution.  Seems odd at best.
    - ???

    I did a bit of searching.  Found other systems complaining about
    this as well, but no clear evaluation of the status and way out.

The plan is to fix these issues and release 6.6.4.  I only expect
changes for MacOS.  Of course, unless other hot fixes show up.

	Cheers --- Jan
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.