On Dec 5, 2014, at 20:33 , kcrisman wrote:
>
>>
>> Built from the tarball, w/o problems. All tests ('ptestlong') passed.
>> OS X, 10.6.8 (Dual 6-core Xeons) and 10.10.1 (Quad-core Core i7).
>>
>
> If you were able to make some 10.6 binaries for us, that would be awesome.
> I assume you ha
Don’t remember where I got the C++11 from but Volker is correct according to
the gcc folks themselves:
https://gcc.gnu.org/install/prerequisites.html
> On 6/12/2014, at 17:33, kcrisman wrote:
>
>
>
> The C++ compiler needs some elements of C++11.
>
> In theory everything should work with a C+
>
> The C++ compiler needs some elements of C++11.
>
>
> In theory everything should work with a C++98 compiler only. But it needs
> to not bail out when encountering options to turn off warnings that it
> doesn't understand. Really, if you don't know what narrowing is then
> "-Wno-narrowing"
>
> Built from the tarball, w/o problems. All tests ('ptestlong') passed.
> OS X, 10.6.8 (Dual 6-core Xeons) and 10.10.1 (Quad-core Core i7).
>
If you were able to make some 10.6 binaries for us, that would be awesome.
I assume you have an older Xcode as well?
--
You received this message
Rebuilding everything serial is not necessary. You can change the MAKE command
and then do ./sage -f pkgX it will work perfectly.
In your case my suspicion is that it will be broken until
local/lib/pkgconfig/freetype2.pc
is fixed.
François
> On 6/12/2014, at 09:07, Emmanuel Charpentier
> wrote
On Fri, Dec 5, 2014 at 12:42 PM, Emmanuel Charpentier <
emanuel.charpent...@gmail.com> wrote:
> Le jeudi 4 décembre 2014 20:48:20 UTC+1, Volker Braun a écrit :
>>
>> As usual, get the "develop" git branch or the self-contained tarball at
>> http://boxen.math.washington.edu/home/release/pub/sage-6.
On Thu, Dec 4, 2014 at 11:26 PM, Justin C. Walker wrote:
>
> On Dec 4, 2014, at 11:48 , Volker Braun wrote:
>
>> As usual, get the "develop" git branch or the self-contained tarball
>> at http://boxen.math.washington.edu/home/release/pub/sage-6.5.beta2.tar.gz
>
> Built from the tarball, w/o proble
Le vendredi 5 décembre 2014 20:56:12 UTC+1, François a écrit :
>
> Could please people submitting logs generate them serially “-j1”.
> The following line probably explains a lot of things:
> /bin/bash ../libtool --tag=CC --mode=compile gcc -std=gnu99
> -DHAVE_CONFIG_H -I. -I/usr/local/sage-6
Could please people submitting logs generate them serially “-j1”.
The following line probably explains a lot of things:
/bin/bash ../libtool --tag=CC --mode=compile gcc -std=gnu99 -DHAVE_CONFIG_H
-I. -I/usr/local/sage-6.4/local/include/libpng12
-I/usr/local/sage-6.3/local/include/freetype2 -
On Friday, December 5, 2014 7:23:52 PM UTC+1, Volker Braun wrote:
>
> We need a different tarball name or our caching will break. If upstream
> doesn't rename it then you have to.
>
> Ok, I'll suggest to add p1 to the version number.
And if needed will do it for Sage only.
--
You received thi
On Friday, December 5, 2014 7:44:33 PM UTC+1, Jean-Pierre Flori wrote:
>
>
>
> On Friday, December 5, 2014 7:06:48 PM UTC+1, Johan S. R. Nielsen wrote:
>>
>>
>> As long as the forced rebuild with the new tarball works there is nothing
>>> to worry about.
>>> Note that I meant run from "$SAGE_ROO
On Friday, December 5, 2014 7:06:48 PM UTC+1, Johan S. R. Nielsen wrote:
>
>
> As long as the forced rebuild with the new tarball works there is nothing
>> to worry about.
>> Note that I meant run from "$SAGE_ROOT" the "sage" script with "-sh
>> sage-fix-pkg-checksums" options and not go to "$S
We need a different tarball name or our caching will break. If upstream
doesn't rename it then you have to.
On Friday, December 5, 2014 5:23:56 PM UTC, Jean-Pierre Flori wrote:
>
>
>
> On Friday, December 5, 2014 5:23:27 PM UTC+1, Jean-Pierre Flori wrote:
>>
>> In fact there has been some failu
> As long as the forced rebuild with the new tarball works there is nothing
> to worry about.
> Note that I meant run from "$SAGE_ROOT" the "sage" script with "-sh
> sage-fix-pkg-checksums" options and not go to "$SAGE_ROOT/sage" and then
> run "sh sage-fix-pkg-checksums".
>
Ah, you meant "./
On Friday, December 5, 2014 6:38:37 PM UTC+1, Johan S. R. Nielsen wrote:
>
> On Friday, December 5, 2014 6:23:56 PM UTC+1, Jean-Pierre Flori wrote:
>>
>> François and Johan, could you try the tarball at:
>> http://boxen.math.washington.edu/home/jpflori/iml-1.0.4/iml-1.0.4.tar.bz2
>> which include
On Friday, December 5, 2014 6:23:56 PM UTC+1, Jean-Pierre Flori wrote:
>
> François and Johan, could you try the tarball at:
> http://boxen.math.washington.edu/home/jpflori/iml-1.0.4/iml-1.0.4.tar.bz2
> which includes the netlib cblas.h as intended.
>
> Please run "./sage -sh sage-fix-pkg-checksums
On Friday, December 5, 2014 5:23:27 PM UTC+1, Jean-Pierre Flori wrote:
>
> In fact there has been some failure from me when upstream updated IML.
>
> I somehow failed to leave the netlib cblas.h (which should get picked up
> if nothing else is found) in the tarball :(
> In the README there is :
In fact there has been some failure from me when upstream updated IML.
I somehow failed to leave the netlib cblas.h (which should get picked up if
nothing else is found) in the tarball :(
In the README there is : * add netlib cblas.h header as fallback header
On Friday, December 5, 2014 1:06:28
> Thanks for looking into this yourself.
>
Sure, I was the one without a functioning Sage :-D
I had a quick look at your config.log but it is exceptionally empty as far
> as the failure is concerned and I had no time to look at IML autotool stuff
> yet.
>
> Note that before we badly hacked IML
Note that for OS X where the headers are missing I copied headers in the source.
IML is the only package I can think of requiring cblas.h we could just always
copy
the header I don’t know how it would hurt.
François
> On 6/12/2014, at 00:55, Jean-Pierre Flori wrote:
>
>
>
> On Friday, Decembe
On Friday, December 5, 2014 12:35:24 PM UTC+1, Johan S. R. Nielsen wrote:
>
> I seem to have solved it: compilation halted when it wasn't able to find
> the ATLAS header files. So I extracted the header files from
> upstream/atlas-3.10.0.tar.bz2/ATLAS/include to some folder and set the
> envir
I seem to have solved it: compilation halted when it wasn't able to find
the ATLAS header files. So I extracted the header files from
upstream/atlas-3.10.0.tar.bz2/ATLAS/include to some folder and set the
environment variable ATLAS_HEADER_PATH to this path. Then compilation
succeeded.
It's pos
On Friday, December 5, 2014 10:40:46 AM UTC, François wrote:
>
> The C++ compiler needs some elements of C++11.
In theory everything should work with a C++98 compiler only. But it needs
to not bail out when encountering options to turn off warnings that it
doesn't understand. Really, if you don
99% sure. The C++ compiler needs some elements of C++11. I am fairly sure that
nothing below 4.2 will build gcc 4.9, but I think the barrier is either 4.5 or
4.6.
I would to check but I think I build it with 4.6 (on AIX 5.3).
François
> On 5/12/2014, at 22:58, Jeroen Demeyer wrote:
>
> On 2014-1
On 2014-12-04 21:03, François Bissey wrote:
gcc 4.0.1 is definitely too old to build 4.9.x.
Are you sure about this statement or are you just guessing?
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this group and stop rec
On 2014-12-05, Justin C. Walker wrote:
>
> On Dec 4, 2014, at 11:48 , Volker Braun wrote:
>
>> As usual, get the "develop" git branch or the self-contained tarball
>> at http://boxen.math.washington.edu/home/release/pub/sage-6.5.beta2.tar.gz
>
> Built from the tarball, w/o problems. All tests ('
26 matches
Mail list logo
