[Bug 592579] Review Request: Frama-c - Framework for source code analysis of C software

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=592579

--- Comment #14 from David A. Wheeler <dwheeler at dwheeler.com> 2010-05-24 13:50:49 EDT ---
The updated rpm fails on 32-bit systems.  You have a built-in assumption that
there is a "lib64", but on 32-bit system it's just "lib".  Here's the error:
cp -f man/frama-c.1
/home/dwheeler/rpmbuild/BUILDROOT/frama-c-1.4-1.fc11.i386/usr/share/man/man1/frama-c-gui.1
for plugin in ; do \
   MAKEFLAGS="" make
FRAMAC_LIBDIR=/home/dwheeler/rpmbuild/BUILDROOT/frama-c-1.4-1.fc11.i386/usr/lib/frama-c
FRAMAC_SHARE=/home/dwheeler/rpmbuild/BUILD/frama-c-Beryllium-20090902/share -C
$plugin install; \
 done
+ strip
/home/dwheeler/rpmbuild/BUILDROOT/frama-c-1.4-1.fc11.i386/usr/bin/frama-c
+ strip
/home/dwheeler/rpmbuild/BUILDROOT/frama-c-1.4-1.fc11.i386/usr/bin/frama-c-gui
+ strip
/home/dwheeler/rpmbuild/BUILDROOT/frama-c-1.4-1.fc11.i386/usr/bin/frama-c.byte
+ strip
/home/dwheeler/rpmbuild/BUILDROOT/frama-c-1.4-1.fc11.i386/usr/bin/frama-c-gui.byte
+ strip
/home/dwheeler/rpmbuild/BUILDROOT/frama-c-1.4-1.fc11.i386/usr/lib64/frama-c/plugins/Ltl_to_acsl.cmxs
strip:
'/home/dwheeler/rpmbuild/BUILDROOT/frama-c-1.4-1.fc11.i386/usr/lib64/frama-c/plugins/Ltl_to_acsl.cmxs':
No such file
error: Bad exit status from /var/tmp/rpm-tmp.TXN0rD (%install)

Can you fix this soon?

Although I haven't looked in detail at the packaging of "why", I suspect it'd
be fairly easy to create a new subpackage "why-jessie"; the new subpackage
would include Jessie and the Jessie plug-in, and depend on frama-c.  I think
that would accurately reflect the situation.  Jessie is delivered as part of
the source code of "why", you can use other parts of "why" without using
Jessie, but Jessie requires the use of frama-c (to create its data format and
the drop-in location for its plug-in).  That shouldn't be hard to do once the
"frama-c" package is in the repository.

Go ahead and package the Frama-C version you're using.  I hope that in the
not-to-distant future you'll update this package to the just-released new
version, but I understand that it's easier to not change versions midstream. 
And I don't know who's had experience with the newly-released version; it might
be best to wait a little bit, until any problems have been shaken out, before
updating the package.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.