On Wed, Apr 22, 2020 at 06:05:57PM +0200, Florian Weimer wrote:
> * Jerry James:
>
> > On Wed, Apr 22, 2020 at 6:01 AM Richard W.M. Jones
> > wrote:
> >> It turns out it comes from dune (the build tool), although I'm still
> >> unclear how and why. In any case I added a rather hacky workaround
* Jerry James:
> On Wed, Apr 22, 2020 at 6:01 AM Richard W.M. Jones wrote:
>> It turns out it comes from dune (the build tool), although I'm still
>> unclear how and why. In any case I added a rather hacky workaround so
>> I can get the build going again:
>
> No, it isn't dune; it's ocaml itself
On Wed, Apr 22, 2020 at 6:01 AM Richard W.M. Jones wrote:
> It turns out it comes from dune (the build tool), although I'm still
> unclear how and why. In any case I added a rather hacky workaround so
> I can get the build going again:
No, it isn't dune; it's ocaml itself. From "Changes" under
m/redhat/redhat-hardened-cc1
> -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic
> -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fPIC
> -I . -DUSEGLPK -g -o removed_criteria.o -c removed_criteria.cpp)
> cc1plus: sorry, unimplemented: '
d-tables -fstack-clash-protection -fcf-protection -fPIC -I
. -DUSEGLPK -g -o removed_criteria.o -c removed_criteria.cpp)
cc1plus: sorry, unimplemented: '-fexcess-precision=standard' for C++
gcc src/notuptodate_criteria.o (exit 1)
What I don't understand is where/what adds
