Your message dated Wed, 02 Dec 2009 12:31:19 +0100
with message-id <4b165007.9000...@dogguy.org>
and subject line Re: Bug#559130: FTBFS: inconsistent assumptions over interface
Gtk
has caused the Debian Bug report #559130,
regarding FTBFS: inconsistent assumptions over interface Gtk
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
559130: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=559130
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: frama-c
Version: 20090901+beryllium+dfsg-2
Severity: serious
Justification: FTBFS
Your package FTBFS on all architectures with:
| ocamlc -c -w Ael -warn-error A -annot -g -I src/misc -I src/ai -I
src/memory_state -I src/toplevel -I src/slicing_types -I src/pdg_types -I
src/kernel -I src/logic -I src/lib -I src/project -I src/buckx -I src/gui -I
external -I cil/src -I cil/src/ext -I cil/src/frontc -I cil/src/logic -I
cil/ocamlutil -I lib/plugins -I lib -I +ocamlgraph -I src/syntactic_callgraph
-I +lablgtk2 -I src/gui -I +lablgtk2 -I +ocamlgraph
src/syntactic_callgraph/cg_viewer.ml
| File "src/syntactic_callgraph/cg_viewer.ml", line 1, characters 0-1:
| Error: The files /usr/lib/ocaml/lablgtk2/gBin.cmi
| and /usr/lib/ocaml/ocamlgraph/dGraphView.cmi
| make inconsistent assumptions over interface Gtk
| make[2]: *** [src/syntactic_callgraph/cg_viewer.cmo] Error 2
Build logs at the usual place:
https://buildd.debian.org/status/package.php?suite=unstable&p=frama-c
Mraw,
KiBi.
--- End Message ---
--- Begin Message ---
notfound 559130 20090901+beryllium+dfsg-2
thanks
The FTBFS occured because it should have been built with the binNMUed
version of ocamlgraph.
Rebuilding the package with the correct build-dependencies fixes the problem.
Cheers,
--
Mehdi Dogguy مهدي الدڤي
http://dogguy.org/
--- End Message ---
