Perhaps you can tell us what CYGWIN_NT-10.0 is, and how is it
different from the usual 64-bit Cygwin?
The most recent version 3.1.4, cf
https://sourceware.org/legacy-ml/cygwin-announce/2020-02/msg6.html
On Sun, Apr 5, 2020 at 4:01 PM Jakub Jabłoński wrote:
>
> Didn't help, started installing
Didn't help, started installing ubuntu on virtual machine, will try here.
Thanks for helping.
On Saturday, April 4, 2020 at 5:04:57 AM UTC+2, Dima Pasechnik wrote:
>
> On Fri, Apr 3, 2020 at 11:04 PM Jakub Jabłoński > wrote:
> >
> > Sorry, didn't notice it's not rebuilding. Done it now and
On Fri, Apr 3, 2020 at 11:04 PM Jakub Jabłoński wrote:
>
> Sorry, didn't notice it's not rebuilding. Done it now and issue with omp
> still occurs.
hmm. Somewhere something instists on using openmp.
Perhaps, do
make distclean
make
>
> On Friday, April 3, 2020 at 4:13:39 PM UTC+2, Dima
Sorry, didn't notice it's not rebuilding. Done it now and issue with omp
still occurs.
On Friday, April 3, 2020 at 4:13:39 PM UTC+2, Dima Pasechnik wrote:
>
> have you rebuilt fflas-ffpack after your addition of flags?
>
> On Fri, Apr 3, 2020 at 10:00 PM Jakub Jabłoński > wrote:
> >
> >
have you rebuilt fflas-ffpack after your addition of flags?
On Fri, Apr 3, 2020 at 10:00 PM Jakub Jabłoński wrote:
>
> Current version:
>
> # If SAGE_FAT_BINARY is set, disable all processor-specific optimizations
> if [ "$SAGE_FAT_BINARY" = yes ]; then
>
it seems that your addition is conditional on SAGE_FAT_BINARY being set to
yes.
It should not be so.
On Fri, 3 Apr 2020, 19:56 Jakub Jabłoński, wrote:
> I have added --disable-openmp here in spkg-install.in:
> if [ "$SAGE_FAT_BINARY" = yes ]; then
> FFLAS_FFPACK_CONFIGURE="--disable-openmp
I have added --disable-openmp here in spkg-install.in:
if [ "$SAGE_FAT_BINARY" = yes ]; then
FFLAS_FFPACK_CONFIGURE="--disable-openmp --disable-sse --disable-sse2
--disable-sse3 --disable-ssse3 --disable-sse41 --disable-sse42
--disable-fma --disable-fma4 --disable-avx --disable-avx2
could you post the top-level config.log ?
On Fri, 3 Apr 2020 at 16:59, Dima Pasechnik wrote:
> you are building fflas-ffpack with OpenMP on, for some reason.
> it should be possible to modify its spkg-install.in file so that it does
> not happen, rebuild it, and sagelib itself.
>
>
> On Fri, 3
you are building fflas-ffpack with OpenMP on, for some reason.
it should be possible to modify its spkg-install.in file so that it does
not happen, rebuild it, and sagelib itself.
On Fri, 3 Apr 2020 at 16:40, Jakub Jabłoński wrote:
> Okay, uploaded only log which seems to be relevant (it's
from this part of the log it is not possible to see much, except that
Sage's Python library has failed to build.
Please paste as many lines above these from the output as you can.
On Fri, 3 Apr 2020, 15:09 Jakub Jabłoński, wrote:
> I have removed whole cygwin and reinstalled everything, now
I have removed whole cygwin and reinstalled everything, now ecl is not
failing. However sage is still not building.
Building log ends with following text (can't upload logs as attachment,
don't know why)
[sagelib-9.1.beta9] collect2: error: ld returned 1 exit status
[sagelib-9.1.beta9] error:
I have removed whole cygwin and reinstalled everything, now ecl is not
failing. However sage is still not building.
--
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
$ set|grep BASH
BASH=/bin/bash
BASHOPTS=cmdhist:complete_fullquote:expand_aliases:extquote:force_fignore:hostcomplete:interactive_comments:login_shell:progcomp:promptvars:sourcepath
BASH_ALIASES=()
BASH_ARGC=()
BASH_ARGV=()
BASH_CMDS=()
BASH_LINENO=()
BASH_SOURCE=()
BASH_VERSINFO=([0]="4" [1]="4"
Could you post the output of "env" and of "set | grep BASH"?
On Wednesday, April 1, 2020 at 11:53:54 AM UTC-4, Jakub Jabłoński wrote:
>
> And gcc -V is not working on my cygwin, "-V" is unrecognized command line
> option. What is it supposed to do?
>
> On Wednesday, April 1, 2020 at 5:23:16 PM
On Wed, Apr 1, 2020 at 11:53 PM Jakub Jabłoński wrote:
>
> And gcc -V is not working on my cygwin, "-V" is unrecognized command line
> option. What is it supposed to do?
this is normal - but it should not crash, it should exit gracefully.
The configure script it trying to figure out how to talk
And gcc -V is not working on my cygwin, "-V" is unrecognized command line
option. What is it supposed to do?
On Wednesday, April 1, 2020 at 5:23:16 PM UTC+2, Jakub Jabłoński wrote:
>
> result.txt is the output, config.log is from ecl build dir.
>
> On Wednesday, April 1, 2020 at 4:41:03 PM
Very strange, it looks like configure dies after running "gcc -V".
You could try the following
(cd '/home/Kuba/sage/local/var/tmp/sage/build/ecl-16.1.2.p5' &&
'/home/Kuba/sage/sage' --sh)
export CONFIG_SHELL="bash -x"
./spkg-install
and post output and the log file again
On Wednesday,
Indeed it was there
On Wednesday, April 1, 2020 at 12:41:14 AM UTC+2, Matthias Koeppe wrote:
>
> Try local/var/tmp/sage/build/ecl-16.1.2.p5/src/build/config.log
>
> On Tuesday, March 31, 2020 at 5:31:21 PM UTC-4, Jakub Jabłoński wrote:
>>
>> I have rebuilt everything from scratch, this time on
Try local/var/tmp/sage/build/ecl-16.1.2.p5/src/build/config.log
On Tuesday, March 31, 2020 at 5:31:21 PM UTC-4, Jakub Jabłoński wrote:
>
> I have rebuilt everything from scratch, this time on develop branch.
>> Attached logs. There waas no config.log in sage\build\pkgs\ecl
>>
>
--
You
When the build fails, there should be a message like:
The following package(s) may have failed to build...
* package: ecl
last build time: ...
log file:...
build directory: /build/directory/is/here/
Check the build directory listed at the end for the file config.log. It
On Tuesday, March 31, 2020 at 11:08:58 AM UTC-4, Jakub Jabłoński wrote:
>
> I'm trying to build sage on windows using CYGWIN_NT-10.0.
> Revision I was trying to build is latest one from here:
> https://trac.sagemath.org/ticket/29269
>
> Failure log in attachment, do you know how to fix that?
>
21 matches
Mail list logo
