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] Error on using pp-annot

  • Subject: [Frama-c-discuss] Error on using pp-annot
  • From: pascal.cuoq at (Pascal Cuoq)
  • Date: Sun, 6 Apr 2014 11:45:04 +0200
  • In-reply-to: <>
  • References: <> <> <> <> <> <>

On Tue, Apr 1, 2014 at 9:36 PM, Frank Dordowsky <frank at> wrote:

> That was a pointer to the right direction. However, the option
> -ffreestanding did not work. With help of a C guru at my office I
> found another option that did the trick: -fpreprocessed <stdc-predef.h>.
> My complete command now reads:
> frama-c -cpp-extra-args="-I `frama-c -print-share-path`/libc"
> -cpp-extra-args="-nostdinc" -cpp-extra-args="-fpreprocessed
> </path/to/stdc-predef.h>" -wp -wp-rte -pp-annot constant.c

According to a later message in a GCC mailing list, you still seem to be
having problems ( ).

An alternative solution would be to use Clang to pre-process your files. It
uses the same syntax for its commandline down to the options that cause
only pre-processing to happen.

Could we see the file stdc-predef.h that is so terrible, or a minimal C
file pre-processed by GCC 4.8.2?


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