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] Beryllium does not compile on FreeBSD 7.2

Anyway, using ./configure && gmake on FreeBSD 7.2 results in the error message I posted earlier. I made different unsuccessful attempts to build Beryllium, including running ./configure in bash. The only solution I found was to use env MAKE=gmake bash ./configure CFLAGS="-I/usr/local/include" LDFLAGS="-L/usr/local/lib".

Therefore, I feel inclined to submit the issue to the bts, as Julien suggested.



-----Urspr?ngliche Nachricht-----
Von: frama-c-discuss-bounces at lists.gforge.inria.fr [mailto:frama-c-discuss-bounces at lists.gforge.inria.fr] Im Auftrag von CUOQ Pascal
Gesendet: Mittwoch, 14. Oktober 2009 14:51
An: Frama-C public discussion; Frama-C public discussion
Betreff: Re: [Frama-c-discuss] Beryllium does not compile on FreeBSD 7.2


> There seem to be two bugs in the configure script:
> - it requires bash, which doesn't have to be present on all systems.

Unlike Julien, I would not encourage you to report this as a bug,
because it will just stay there and take up space.
Indeed, bash does not have to be present on all systems,
but it has to be present on all systems on which Frama-C can
be compiled.
I believe it can be installed in a single port command.
It's a prerequisite, just as OCaml is. We might accept a patch
that removes the bash dependency without making anything else
worse.

> - it doesn't detect the location of include and of library files.

I am very surprised by this. I routinely compile on
a freeBSD variant (with bash installed and "make" calling GNU
make). All my libraries are in a non-standard place
(/usr/local/Frama-C_Be) because it's by copying a
selection of them that I build a binary release.

The only thing I need is to have in my path the ocaml
compilers (ocamlc knows its own installation path
and ocaml libraries are installed there)
and pkg-config (which knows where it is installed and how to
find all the gtk+-related libraries that are a prerequisite to
lablgtk).

Pascal