clang/rust finds it when linking some rust code - somewhat needed by
stylo (the css engine written in rust within mozilla). Modeled after
what is done in lang/g77.
From semarie@, who discussed it with espie@.
- we don't have xlocale
- so we use __bsd_locale_fallbacks_h, yes even for #include <iostream>
- that depends on mbsnrtowcs and wcsnrtombs from wchar.h
- those require __POSIX_VISIBLE to be >= 200809...
bump accordingly. tested by naddy@, no breakage on gcc platforms.
ghc uses cc for generating object files from assembler files and
passes the CONF_CC_OPTS_STAGE? flags to it, which clang doesn't
like, so add -Wno-unused-command-line-argument to the flags passed
to cc if it's clang.
To let this work for the bootstrap compiler, properly CONFIGURE_ENV
when installing the bootstrap (in post-patch:). This also makes the
hack patching the bootstrap/bin/ghc script in post-patch: obsolete.
prodded by (and with some hints from) espie@
~here are still a lot of warnings, most about macros #defined in
storage/ClosureMacros.h. Those should be fixed in a separate step,
probably after an update to ghc-8.
SECURITY:
"A security vulnerability in the `racket/sandbox` library and Typed
Racket allowed malicious Typed Racket code to escape the sandbox.
This vulnerability has been fixed in Racket version 6.9. Anyone using
`racket/sandbox` to execute untrustworthy code with access to Typed
Racket should upgrade to version 6.9 immediately.
While this known vulnerability has been eliminated, it is possible that
similar errors in other installed collections could also be exploited,
although we are not currently aware of any existing vulnerabilities. We
recommend that if you use the Racket sandbox to execute untrustworthy
Racket code, you should also employ additional operating system or
virtual machine level protections. The documentation for `racket/sandbox`
has been updated to list recommended security practices for using the
library."
https://download.racket-lang.org/v6.9.html
as the patch shows).
you'll need to wait for a bootstrap/rebootrap yourself so this is actually
effective.
(should cut down *a lot* on the insane number of warnings produced due to
unknown compile options on a clang system)
okay kili@
