Open a ticket we forgot to make it depend from pkg-config. Probably
all the machines testing it had a system instal so we didn’t notice.
François
> On 5/09/2015, at 23:04, John Cremona wrote:
>
> I also got an error with the brial package (after the same sequence as
>
And the ticket is ready for review.
François
> On 6/09/2015, at 08:36, Francois Bissey
> wrote:
>
> No surprise on brial pig-config is not on OS X by default. That’s the thing
> I didn’t do while reviewing, build from scratch on OS X but then Andrew
> was
I cannot see the short log.
François
> On 6/09/2015, at 08:26, Justin C. Walker wrote:
>
> On 10.6.8 (Dual 6-core Xeons), it blew up building brial. The complaint was
> "no suitable python interpreter found". The (short) log file is attached.
> 48 spkgs built. This was
On Sep 5, 2015, at 14:05 , Francois Bissey wrote:
> I cannot see the short log.
Oh, come on. It is right down there ... :-}
I admit it would have been easier if I had attached it when I said I would.
> François
>
>> On 6/09/2015, at 08:26, Justin C. Walker wrote:
>>
>> On
On Sep 5, 2015, at 13:36 , Francois Bissey wrote:
> No surprise on brial pig-config is not on OS X by default. That’s the thing
> I didn’t do while reviewing, build from scratch on OS X but then Andrew
> was testing on OS X so I didn’t bother.
I may be missing something, but pkg-config is in
On Sep 4, 2015, at 11:29 , Volker Braun wrote:
> As always, you can get the latest beta version from the "develop" git
> branch. Alternatively, the self-contained source tarball is at
> http://www.sagemath.org/download-latest.html
Built from tarball on two OS X systems:
On 10.10.5 (Quad-core
On 5 September 2015 at 12:11, Francois Bissey <
francois.bis...@canterbury.ac.nz> wrote:
> Open a ticket we forgot to make it depend from pkg-config. Probably
> all the machines testing it had a system instal so we didn’t notice.
>
I did not open a ticket, but can confirm that after installing
On Sep 5, 2015, at 16:55 , Francois Bissey wrote:
> It is unrelated, I was expecting it to fail on OS X and didn’t read your
> message properly.
> It should depend on python as well.
> I haven’t seen any log in your initial message. May be something ate it in
> transit.
The log was