Frama-C-discuss mailing list archives

This page gathers the archives of the old Frama-C-discuss archives, that was hosted by Inria's gforge before its demise at the end of 2020. To search for mails newer than September 2020, please visit the page of the new mailing list on Renater.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Frama-c-discuss] Installation problem with Neon release

  • Subject: [Frama-c-discuss] Installation problem with Neon release
  • From: rovedy at (rovedy at
  • Date: Tue, 18 Nov 2014 10:09:33 -0200
  • In-reply-to: <>
  • References: <> <>



Thank you for reply.
We tried to fix the problem clang/XCode without sucess.

We have another laptop with Frama-C Fluorine (20130601) release, Why3
Verification Platform 0.81 in a OS X Mountain Lion Version 10.8.2.
Because of our previous experience, we intend to update only the Frama-C
version in this laptop.
Will the following commands work?

$ opam remove frama-c
$ opam install frama-c

Best regards,
Rovedy, Nanci

Em 17/11/2014 15:21, Virgile Prevosto escreveu: 

> Hello,
> 2014-11-17 18:03 GMT+01:00 <rovedy at>:
>> In order to install the Neon release, we updated to: - OS X Yosemite Version 10.10 - XCode 6.1 - opam 1.2.0 - ocaml 4.02.1 # + gcc -fno-defer-pop -Wall -D_FILE_OFFSET_BITS=64 -D_REENTRANT -c
> This is apparently a known issue with Clang/XCode, but it should be
> solved in 4.02 according to this report:
> [1]
> If this is not the case, you should report the problem to either OCaml
> or Opam. Frama-C has nothing to do with it.
> Best regards,

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>