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] Frama-C 15 Phosphorus is out

  • Subject: [Frama-c-discuss] Frama-C 15 Phosphorus is out
  • From: Andre.OLIVEIRAMARONEZE at cea.fr (Andre Maroneze)
  • Date: Fri, 1 Sep 2017 10:41:34 +0200
  • In-reply-to: <CABbVA-Amik1s+r3GXaGa+y7MfYQsQZurjnsoCS9j5sjN0CacYA@mail.gmail.com>
  • References: <CA+yPOVgmjyU_h8_Y8+bdfQMbtUfTK-6hT_cqTJKbwV_7rvCOmw@mail.gmail.com> <504e680c-88b0-5ad5-9111-c3f6fa91b58c@dogguy.org> <CABbVA-Amik1s+r3GXaGa+y7MfYQsQZurjnsoCS9j5sjN0CacYA@mail.gmail.com>
We have just committed some patches to the Frama-C snapshot Github 
repository <https://github.com/Frama-C/Frama-C-snapshot> which fix the 
native dynlink issue and also export the _frama-c ZSH auto-completion 
script (the Bash version was already exported).

The auto-completion scripts (share/autocomplete_frama-c 
<https://raw.githubusercontent.com/Frama-C/Frama-C-snapshot/master/share/autocomplete_frama-c> 
for Bash, share/_frama-c 
<https://raw.githubusercontent.com/Frama-C/Frama-C-snapshot/master/share/_frama-c> 
for Zsh) themselves contain instructions on how to install them.


--

André


On 13/08/17 00:26, Boris Yakobowski wrote:
> On Fri, Aug 11, 2017 at 10:19 PM, Mehdi Dogguy <mehdi at dogguy.org 
> <mailto:mehdi at dogguy.org>> wrote:
>
>     Do you still support architecture w/o native dynlink? I didn't see
>     this
>     statement in the changelog whereas I get this build failure on
>     (e.g. mips)
>     when I try to compile Frama-C:
>
> [...]
>
>     So it tests two things at once:
>     - presence of a native compiler
>     - native dynlink
>
>     So bytecode architectures look like they are not supported anymore
>     as well,
>     which is a pity.
>
>
> This was not intended. We only wanted to get rid of the platforms 
> where native dynlink does not work. When native compilation is not 
> available, we probably should not test for native dynlink at all. And 
> better yet, when native compilation is available, but not native 
> dynlink, only compile the bytecode version.
>
>     > - Bash and Zsh completion for Frama-C options
>
>     Can you please clarify where are the completion scripts? I didn't
>     find them
>     in the tarball, but maybe I was looking at the wrong place.
>
>
> We apparently forgot to package the scripts... The frama-c 
> -autocomplete option is used to generate the autocompletion tables, 
> but we have also written scripts to parse this output and to feed it 
> to bash and zsh. There are two scripts available for zsh in the our 
> dev tree, I will let someone more familiar with them comment and/or 
> post them here.
>
> -- 
> Boris
>
>
> _______________________________________________
> Frama-c-discuss mailing list
> Frama-c-discuss at lists.gforge.inria.fr
> https://lists.gforge.inria.fr/mailman/listinfo/frama-c-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gforge.inria.fr/pipermail/frama-c-discuss/attachments/20170901/98845d21/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3797 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.gforge.inria.fr/pipermail/frama-c-discuss/attachments/20170901/98845d21/attachment.bin>