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] preprocessor problems with jessie
- Subject: [Frama-c-discuss] preprocessor problems with jessie
- From: regehr at cs.utah.edu (John Regehr)
- Date: Thu, 7 Nov 2013 10:11:42 -0700 (MST)
- In-reply-to: <527B6A13.6090605@inria.fr>
- References: <527B1BE5.6040306@cs.utah.edu> <527B6A13.6090605@inria.fr>
> I have encountered the same issue. Let me guess, your gcc compiler is version > 4.8, right? For some reason, it seems Frama-C Fluorine cannot cope with the > output of cpp-4.8. My workaround is to explicitly set the preprocessor as > cpp-4.7 with the -cpp-command of Frama-C. Yes, my distro uses gcc-4.8, and yes this workaround succeeds, thanks! John
- References:
- [Frama-c-discuss] preprocessor problems with jessie
- From: regehr at cs.utah.edu (John Regehr)
- [Frama-c-discuss] preprocessor problems with jessie
- From: guillaume.melquiond at inria.fr (Guillaume Melquiond)
- [Frama-c-discuss] preprocessor problems with jessie
- Prev by Date: [Frama-c-discuss] how jessie and why platform work to generate a .v output?
- Next by Date: [Frama-c-discuss] preprocessor problems with jessie
- Previous by thread: [Frama-c-discuss] preprocessor problems with jessie
- Next by thread: [Frama-c-discuss] lots of unproved goals for simple example
- Index(es):