Am 17.08.2010 um 19:27 schrieb François Revol:
Le 17 août 2010 à 19:21, Andreas Färber a écrit :Am 17.08.2010 um 10:33 schrieb Axel Dörfler:andreas.faerber@xxxxxx wrote:Cygwin and Solaris rely on Haiku supplying a glibc-compatible regex.hheader.Before r38031, Solaris was able to reuse cygwin/regex.h successfully.Import the latest stable 2.11 posix/regex.h to avoid local trickery and to silence some RE_* errors.That sounds messy - why can't we use the host's regex.h header?Cygwin and Solaris host-compile libroot's glibc regex sources into the keymap tool - for that we need a matching header.Why Cygwin chose that route in the first place, I don't know. Probably because no fully GNU-compatible regex.h is available on the host?For instance, there's no single RE_* macro in OpenSolaris's regex.h header:http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/head/regex.hHmm neither in OSX' one, does that mean if I jam clean and try a full build it will screw up now ?
The Read Me [1] instructs to install gnuregex from Darwin Ports. It appears they do the work of compiling glibc's regex sources into a custom libgnuregex.dylib [2]. This requirement to use Darwin Ports along with that nested disk image thing ;) kept me from investigating building on OSX further...
Having stated "Cygwin and Solaris" above, not including Darwin, it may still work. It's just utterly non-standard and working around the same issue in a very different way.
Andreas [1] http://dev.haiku-os.org/browser/haiku/trunk/ReadMe.cross-compile?rev=31516#L32 [2] http://gnuregex.darwinports.com/