[sage-devel] Re: Error building Sage on UM 16.04: error making OpenBLAS

2017-07-21 Thread Christopher Phoenix 
BTW, forgot to link this, but you can see the full list of OpenBLAS targets 
here: https://github.com/xianyi/OpenBLAS/blob/develop/TargetList.txt

This shows the reason why ATOM isn't the default choice. It would be bad if 
OpenBLAS picked that and you were actually running an AMD cpu, or if you 
had a 32-bit system (Atom refers to X86_64 cpus). And while I don't even 
know what MIPS or SPARC arch is, someone is probably building OpenBLAS on 
it. There's just too many possible hardware configurations for OpenBLAS to 
make assumptions about what you are running!

On Friday, July 21, 2017 at 10:28:00 AM UTC-7, John H Palmieri wrote:
>
> I just had the same problem with a new computer (Kaby Lake processor, 
> apparently). Can we patch OpenBLAS to fall back to ATOM if it's x86_64 but 
> can't detect the precise CPU? (I can't do this, but maybe someone else can.)
>
>   John
>
>
> On Friday, July 14, 2017 at 12:25:57 AM UTC-7, Dima Pasechnik wrote:
>>
>> Indeed, OPENBLAS_CONFIGURE="TARGET=ATOM" is a catch-all x86_64 processors 
>> target.
>> Perhaps one can try the development version of openblas on these 
>> processors
>> (from https://github.com/xianyi/OpenBLAS)
>>
>> On Friday, July 14, 2017 at 12:29:12 AM UTC+1, Christopher Phoenix wrote:
>>>
>>> I'm building Sage 7.6 on my laptop, and there was an error making 
>>> openblas that directed me to the log files for that package. The log file 
>>> said that detecting CPU failed, and to set TARGET explicitly. It also 
>>> suggested I email this google group to explain the problem, with the 
>>> relevant part of the log files. So I've attached it below. 
>>>
>>> OS: Ubuntu Mate 16.04 LTS
>>> Sage Version: 7.6
>>> HW: Lenovo Thinkpad 11e, 500gb HD, 4 gb ram, Intel Celeron N2940 with 4 
>>> cpu cores
>>>
>>> Before the build, I made sure that I had all the listed dependencies and 
>>> suggested packages already installed. Then I cloned the Git repo, set 
>>> MAKE='make -j5 -4' and typed make. Make ran for about 45 min or more before 
>>> it stopped and reported the error. I asked about this issue on sage-support 
>>> earlier (
>>> https://groups.google.com/forum/#!topic/sage-support/NlRyew12xDQ).
>>>
>>> Someone had the same issue on very similar hardware (another 11e) here: 
>>> https://groups.google.com/d/msg/sage-devel/zQsZsivts0I/cblwvEkNDgAJ The 
>>> log files look almost exactly the same. They reported that setting 
>>> OPENBLAS_CONFIGURE="TARGET=ATOM" resolved this cpu detection issue, so I'm 
>>> going to try setting this and building Sage again later today. I was a 
>>> little confused since a Celeron is not an Atom afaik, I'm guessing this is 
>>> a catch-all setting for lower-end processors?
>>>
>>> Any advice will be greatly appreciated!
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Error building Sage on UM 16.04: error making OpenBLAS

2017-07-21 Thread Christopher Phoenix 
I'm pretty sure that's an issue for upstream, not the Sage devs, maybe we 
should ask the OpenBLAS devs? But I suspect that the problem here is that 
there isn't a default choice that covers all CPU types. Atom is a catch-all 
for many low-end X86_64 cpus (like my Celeron), but it's not the best 
choice for all. People on this help topic suggested using TARGET=HASWELL 
for Kaby Lake: https://github.com/xianyi/OpenBLAS/issues/1006

I believe there are some specific optimizations applied to each setting 
that help it run faster on particular CPUs. If OpenBLAS fails to detect 
your cpu, its probably better that make simply stops the process and asks 
for the user to apply the right setting instead of just falling on a 
default that may or may not be appropriate for your situation. Fixing it 
just requires setting a single env variable before the build, after all. 

On Friday, July 21, 2017 at 10:28:00 AM UTC-7, John H Palmieri wrote:
>
> I just had the same problem with a new computer (Kaby Lake processor, 
> apparently). Can we patch OpenBLAS to fall back to ATOM if it's x86_64 but 
> can't detect the precise CPU? (I can't do this, but maybe someone else can.)
>
>   John
>
>
> On Friday, July 14, 2017 at 12:25:57 AM UTC-7, Dima Pasechnik wrote:
>>
>> Indeed, OPENBLAS_CONFIGURE="TARGET=ATOM" is a catch-all x86_64 processors 
>> target.
>> Perhaps one can try the development version of openblas on these 
>> processors
>> (from https://github.com/xianyi/OpenBLAS)
>>
>> On Friday, July 14, 2017 at 12:29:12 AM UTC+1, Christopher Phoenix wrote:
>>>
>>> I'm building Sage 7.6 on my laptop, and there was an error making 
>>> openblas that directed me to the log files for that package. The log file 
>>> said that detecting CPU failed, and to set TARGET explicitly. It also 
>>> suggested I email this google group to explain the problem, with the 
>>> relevant part of the log files. So I've attached it below. 
>>>
>>> OS: Ubuntu Mate 16.04 LTS
>>> Sage Version: 7.6
>>> HW: Lenovo Thinkpad 11e, 500gb HD, 4 gb ram, Intel Celeron N2940 with 4 
>>> cpu cores
>>>
>>> Before the build, I made sure that I had all the listed dependencies and 
>>> suggested packages already installed. Then I cloned the Git repo, set 
>>> MAKE='make -j5 -4' and typed make. Make ran for about 45 min or more before 
>>> it stopped and reported the error. I asked about this issue on sage-support 
>>> earlier (
>>> https://groups.google.com/forum/#!topic/sage-support/NlRyew12xDQ).
>>>
>>> Someone had the same issue on very similar hardware (another 11e) here: 
>>> https://groups.google.com/d/msg/sage-devel/zQsZsivts0I/cblwvEkNDgAJ The 
>>> log files look almost exactly the same. They reported that setting 
>>> OPENBLAS_CONFIGURE="TARGET=ATOM" resolved this cpu detection issue, so I'm 
>>> going to try setting this and building Sage again later today. I was a 
>>> little confused since a Celeron is not an Atom afaik, I'm guessing this is 
>>> a catch-all setting for lower-end processors?
>>>
>>> Any advice will be greatly appreciated!
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Error building Sage on UM 16.04: error making OpenBLAS

2017-07-21 Thread John H Palmieri 
I just had the same problem with a new computer (Kaby Lake processor, 
apparently). Can we patch OpenBLAS to fall back to ATOM if it's x86_64 but 
can't detect the precise CPU? (I can't do this, but maybe someone else can.)

  John


On Friday, July 14, 2017 at 12:25:57 AM UTC-7, Dima Pasechnik wrote:
>
> Indeed, OPENBLAS_CONFIGURE="TARGET=ATOM" is a catch-all x86_64 processors 
> target.
> Perhaps one can try the development version of openblas on these processors
> (from https://github.com/xianyi/OpenBLAS)
>
> On Friday, July 14, 2017 at 12:29:12 AM UTC+1, Christopher Phoenix wrote:
>>
>> I'm building Sage 7.6 on my laptop, and there was an error making 
>> openblas that directed me to the log files for that package. The log file 
>> said that detecting CPU failed, and to set TARGET explicitly. It also 
>> suggested I email this google group to explain the problem, with the 
>> relevant part of the log files. So I've attached it below. 
>>
>> OS: Ubuntu Mate 16.04 LTS
>> Sage Version: 7.6
>> HW: Lenovo Thinkpad 11e, 500gb HD, 4 gb ram, Intel Celeron N2940 with 4 
>> cpu cores
>>
>> Before the build, I made sure that I had all the listed dependencies and 
>> suggested packages already installed. Then I cloned the Git repo, set 
>> MAKE='make -j5 -4' and typed make. Make ran for about 45 min or more before 
>> it stopped and reported the error. I asked about this issue on sage-support 
>> earlier (https://groups.google.com/forum/#!topic/sage-support/NlRyew12xDQ
>> ).
>>
>> Someone had the same issue on very similar hardware (another 11e) here: 
>> https://groups.google.com/d/msg/sage-devel/zQsZsivts0I/cblwvEkNDgAJ The 
>> log files look almost exactly the same. They reported that setting 
>> OPENBLAS_CONFIGURE="TARGET=ATOM" resolved this cpu detection issue, so I'm 
>> going to try setting this and building Sage again later today. I was a 
>> little confused since a Celeron is not an Atom afaik, I'm guessing this is 
>> a catch-all setting for lower-end processors?
>>
>> Any advice will be greatly appreciated!
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Reviewing 'Memory leak in algebraic_immunity of BooleanFunction class' #14549

2017-07-21 Thread Friedrich Wiemer 
And here, too: may I ask again for a review of this ticket?
Does anyone has an opinion on the discussion, where to fix the memory leak?

Should I provide more info in this posts here, or is the discussion 
supposed to take place in the comments of the tickets?

Am Mittwoch, 7. Juni 2017 10:55:21 UTC+2 schrieb Friedrich Wiemer:
>
> Hi
>
> Does someone has time to review my commit on issue #14549?
> https://trac.sagemath.org/ticket/14549#comment:10
>
> Cheers
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Reviewing list of SBox instances

2017-07-21 Thread Friedrich Wiemer 
May I ask again for someone to review this ticket? Roed offere to do so, 
but I'm not sure what the "official" way to ask for this reviews again, is.

Am Mittwoch, 7. Juni 2017 14:58:43 UTC+2 schrieb Friedrich Wiemer:
>
> Hi
>
> Does someone has time to review my work on #22988?
> https://trac.sagemath.org/ticket/22988
>
> Cheers
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Error installing package linbox-1.4.2

2017-07-21 Thread Clement Pernet 

Le 19/07/2017 à 22:32, François Bissey a écrit :

One thing that I don’t remember seeing
anywhere before and that I find suspicious “-fabi-version=6” in CFLAGS.


For the record, this -fabi-version=6 option is forced by givaro (a dependency of LinBox) to avoid a 
demangling bug with the standard abi when using SIMD vector types __m128 and __m256.


As for the bug, I confirm that 768Mo of RAM is likely the reason for the 
compilation failure.

Clément


Is this something you somehow added or you have no ideas what I am talking
about?

François


On 20/07/2017, at 06:22, Jose Luis Bracamonte Amavizca  
wrote:

I was trying to install SageMathCell on a VPS with Ubuntu 16.04.2 LTS (GNU/Linux 
2.6.32-042stab120.20 x86_64) following the instructions form the oficial GitHub repository page on 
https://github.com/sagemath/sagecell . In the section "Simple Installation" on the step 3 
after the "make" command, and after waiting a log time for building, an error occurs , 
displaying the following on the terminal.

[linbox-1.4.2] 


[linbox-1.4.2] Error installing package linbox-1.4.2

[linbox-1.4.2] 


[linbox-1.4.2] Please email sage-devel 
(http://groups.google.com/group/sage-devel)

[linbox-1.4.2] explaining the problem and including the relevant part of the 
log file

[linbox-1.4.2]   /home/luisjba/sc_build/sage/logs/pkgs/linbox-1.4.2.log

[linbox-1.4.2] Describe your computer, operating system, etc.

[linbox-1.4.2] If you want to try to fix the problem yourself, *don't* just cd 
to

[linbox-1.4.2] 
/home/luisjba/sc_build/sage/local/var/tmp/sage/build/linbox-1.4.2 and type 
'make' or whatever is appropriate.

[linbox-1.4.2] Instead, the following commands setup all environment variables

[linbox-1.4.2] correctly and load a subshell for you to debug the error:

[linbox-1.4.2]   (cd 
'/home/luisjba/sc_build/sage/local/var/tmp/sage/build/linbox-1.4.2' && 
'/home/luisjba/sc_build/sage/sage' --sh)

[linbox-1.4.2] When you are done debugging, you can type "exit" to leave the 
subshell.

[linbox-1.4.2] 


Makefile:2103: recipe for target 
'/home/luisjba/sc_build/sage/local/var/lib/sage/installed/linbox-1.4.2' failed

make[2]: *** 
[/home/luisjba/sc_build/sage/local/var/lib/sage/installed/linbox-1.4.2] Error 1

make[2]: Leaving directory '/home/luisjba/sc_build/sage/build/make'

Makefile:912: recipe for target 'all' failed

make[1]: *** [all] Error 2

make[1]: Leaving directory '/home/luisjba/sc_build/sage/build/make'



real2m43.118s

user1m54.334s

sys 0m13.253s

***

Error building Sage.



The following package(s) may have failed to build (not necessarily

during this run of 'make all'):



* package: linbox-1.4.2

   log file: /home/luisjba/sc_build/sage/logs/pkgs/linbox-1.4.2.log

   build directory: 
/home/luisjba/sc_build/sage/local/var/tmp/sage/build/linbox-1.4.2



The build directory may contain configuration files and other potentially

helpful information. WARNING: if you now run 'make' again, the build

directory will, by default, be deleted. Set the environment variable

SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.



Makefile:16: recipe for target 'all' failed

make: *** [all] Error 1


  The log file linbox-1.4.2.log is attached here.

--
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.





--
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.