Re: Can't compile SWI on FreeBSD

Jan Wielemaker <jan@xxxxxxxxxxxxxxxxxxx> wrote:
[...]
Some of those are fixed recently.

I finally got hold of the specific version mentiond and found the problem
mentioned.

I also see that 5.6.20 it was a very clean build apart from -- as USUAL :) --
jpl. (It has some problem finding the "defaul" places for the various
java hdrs and libs. They are scattered around even more than the config
expects.)
Even xpce seemed to give none of the old niggles. :)

[...]
Some parts of the system are very old and ported to many weird OSes
:-) Removed the sys/malloc.h.
[...]

Brother, I *know* how that is. :)

As configure doesn't even test for it
anymore and it was included conditionally, I wonder how it can cause a
problem. I won't take out malloc.h for now as I think there are still
ports out there that needs it.

The compile was getting some syntax error -- I didn't check too closely. Maybe
some other needed headr is not included. Anyway, the "std" malloc.h works fine
for the moment. It does give a warning, which will turn fatal if -Werror
is on.

[Re ERROR: messages from later parts of xpce build]
Sounds a bit worrying. Please send details to me or post them to the Bugzilla
at http://www.swi-prolog.org.
[...]

OK. I'll send that ovr. But that problem seems to have gone away with .20.

With help from various people, the CVS version now contains code that
appears to run on FreeBSD.

OK. I did look into it, and as you probably heard on both obsd and fbsd
(and, no doubt, nbsd as well) the clib "localtime.c" module does have those
daylight, timzone variables but under a USG conditional. I.e. old.
Probably now has something to do with avoiding reentrancy problems. You can
never tell when 2 threads might want to run in different timezones. :o

Looking through the std libs there appeared to be no "compatibility"
version of localtime that had been compiled with the USG option enabled
and stashed somehwere in /usr/lib.

And the fbsd/obsd time.h &ct hdr files do not include any ifdef to
make it work in the posix manner.

So it's a hack with a "my_tzset" that works with those vars, or something
similar.

Cheers, and thanks for all the swipl. :)
.