On Thu, 24 Jul 2008 23:05:01 +0100, Rob Kendrick wrote:
The defines enable the features of the C library that we require on
various operating systems. On *BSD libc, glibc and Solaris, you need
this collection of #defines to enable modern library functionality.
It surprises me that these matter, as if your C library triggers on
them, the only sensible thing it could do is enable more
functionality. This may point to an issue in the C library on your
host system. Try removing one at a time to see if it's just a specific
one that causes the issue, and then grep your standard headers to see
what triggers on it.
I put them all back and can't reproduce the problem again, although
strncasecmp is still crashing.
I've recompiled the whole caboodle with a different clib now and not a
single crash, so I think blaming the C library is the correct thing to
I now have lots of work to do writing native code, currently it opens
a window, fetches a page and sets the window's title - and then sits
in an endless loop doing nothing, as that's as far as I got.
btw, file: URLs seem to be adding a slash to the beginning of the
path, no matter how I specify them. This is very annoying, as a slash
at the start of a path indicates the parent of the current directory.
file://default.css will translate to /default.css which looks in the
parent directory for the file default.css. To get default.css in the
current directory I have to ask for file://netsurf/default.css (which
only works if the current directory is called "netsurf"). Absolute
paths are impossible as file://ram:default.css translates to
/ram:default.css which asks me to insert disk "/ram", which will never
How do I stop this?