I just tried to build the newest polymake (2.12.rc3) and it doesn't compile
because it uses some bit of boost that is not in our cropped boost. It has
a configure switch to specify a particular boost, but since it also uses
gmp/mpfr it still picks up our cropped boost. And the cropped boost is n
Le vendredi 18 mai, Volker Braun a écrit:
> I just had a look at boost, if we delete the documentation then it is
> 25MB. Without documentation and tests it is 15MB, though I'd rather
> have the tests included.
>
> Although most of boost is headers, some libraries need to be
> compiled. The bigges
I just had a look at boost, if we delete the documentation then it is 25MB.
Without documentation and tests it is 15MB, though I'd rather have the
tests included.
Although most of boost is headers, some libraries need to be compiled. The
biggest question is probably if we want to build boost/Py
Le vendredi 18 mai, Jeroen Demeyer a écrit:
> On 2012-05-18 10:14, Julien Puydt wrote:
> > The second point has bothered me for quite some time already, so
> > with the first in the air, it might be time to ask : wouldn't it be
> > worth to have a proper boost spkg, which would contain the needed
>
On 2012-05-18 10:14, Julien Puydt wrote:
> The second point has bothered me for quite some time already, so
> with the first in the air, it might be time to ask : wouldn't it be
> worth to have a proper boost spkg, which would contain the needed
> frameworks, coming from upstream?
In principle I ha
Hi,
I raise the question of boost in sage because :
(1) of the recent "PolyBoRi requires boost library" thread on this
mailing-list ;
(2) because sage 5.0 has a boost_cropped spkg, whose SPKG.txt says it
was obtained by taking the sources out of polybori's, which means :
(i) it wasn't a proper p
