0000225: Incorrect linking order for the viewer

(0000370)
monate (reporter)
2009-09-02 16:47

Can you confirm if the bug is still present in Beryllium?

(0000371)
mehdi (reporter)
2009-09-04 16:08

I would have been able to answer if the interface of Jessie doesn't change. I'll answer then when I'll resolve this issue:

File "src/jessie/interp.ml", line 2093, characters 54-60:
Error: This expression has type
         ((bool * bool) * Jc.Jc_constructors.ptype * string * int option)
         list
       but an expression was expected of type
         (bool * Jc.Jc_ast.ptype * string * int option) list
make[2]: *** [src/jessie/interp.cmx] Erreur 2

Cheers,

(0000373)
signoles (manager)
2009-09-04 18:43
edited on: 2009-09-04 18:44

You're right: you have to wait the next version of why or to use the synchronized version of why comming within Frama-C. You can also configure frama-c with "./configure --disable-jessie"

(0000374)
mehdi (reporter)
2009-09-05 00:50

My plan was to come up with a patch to make it compile. I don't feel like disabling the Jessie plugin, nor using Why shipped within Frama-c.

It would have been so nice to have stable versions (frama-c and why) synchronized. IMHO, synchronizing a beta version of Frama-c and a stable one of Why seems to me like a no-sense.

Do you have any idea on the release date of the next stable version of Why?

(0000384)
signoles (manager)
2009-09-09 08:55

Already fixed in Beryllium. Thank's for the report and the patch.

Issue History
Date Modified	Username	Field	Change
2009-09-01 14:12	mehdi	New Issue
2009-09-01 14:12	mehdi	File Added: 0002-Do-not-add-GRAPH_GUICMO-to-BYTE_GUI_LIBS.patch
2009-09-02 10:48	signoles	Status	new => assigned
2009-09-02 10:48	signoles	Assigned To	=> signoles
2009-09-02 16:47	monate	Note Added: 0000370
2009-09-04 16:08	mehdi	Note Added: 0000371
2009-09-04 16:17	signoles	Status	assigned => acknowledged
2009-09-04 18:43	signoles	Note Added: 0000373
2009-09-04 18:44	signoles	Note Edited: 0000373
2009-09-05 00:50	mehdi	Note Added: 0000374
2009-09-07 13:29	virgile	Status	acknowledged => resolved
2009-09-07 13:29	virgile	Fixed in Version	=> Frama-C Beryllium
2009-09-07 13:29	virgile	Resolution	open => fixed
2009-09-09 08:55	signoles	Note Added: 0000384
2009-09-09 08:55	signoles	Status	resolved => closed

Notes
(0000370) monate (reporter) 2009-09-02 16:47	Can you confirm if the bug is still present in Beryllium?

(0000371) mehdi (reporter) 2009-09-04 16:08	I would have been able to answer if the interface of Jessie doesn't change. I'll answer then when I'll resolve this issue: File "src/jessie/interp.ml", line 2093, characters 54-60: Error: This expression has type ((bool * bool) * Jc.Jc_constructors.ptype * string * int option) list but an expression was expected of type (bool * Jc.Jc_ast.ptype * string * int option) list make[2]: *** [src/jessie/interp.cmx] Erreur 2 Cheers,

(0000373) signoles (manager) 2009-09-04 18:43 edited on: 2009-09-04 18:44	You're right: you have to wait the next version of why or to use the synchronized version of why comming within Frama-C. You can also configure frama-c with "./configure --disable-jessie"

(0000374) mehdi (reporter) 2009-09-05 00:50	My plan was to come up with a patch to make it compile. I don't feel like disabling the Jessie plugin, nor using Why shipped within Frama-c. It would have been so nice to have stable versions (frama-c and why) synchronized. IMHO, synchronizing a beta version of Frama-c and a stable one of Why seems to me like a no-sense. Do you have any idea on the release date of the next stable version of Why?

(0000384) signoles (manager) 2009-09-09 08:55	Already fixed in Beryllium. Thank's for the report and the patch.

Relationships