Hi Dima,
My ./configure tells me I have additional packages to install, but
installing them seems not to change anything. e.g. the output from
./configure:
*configure:notice: the following SPKGs did not find equivalent system
packages:appdirs distlib filelock...*
so I apt-get ins
avoid building gcc. You don't need it. Read advice on packages printed by
./configure at the end of run, and follow it.
I'd give you more details over a teams or google meet call.
(Bruno is one of our 3rd year students I advise this year).
Dima
On Fri, 4 Nov 2022, 18:29 'bruno edwards' via sage-
Thanks again. I was able to build sage.
On Wednesday, 30 December 2020 at 17:55:12 UTC jambodev wrote:
> Thanks Dima,
>
> I'll remove that and will retry.
>
> cheers,
>
>
> On Wednesday, 30 December 2020 at 16:16:18 UTC dim...@gmail.com wrote:
>
>> in the install.log, one sees
>>
>> [sagelib-9.3
Thanks Dima,
I'll remove that and will retry.
cheers,
On Wednesday, 30 December 2020 at 16:16:18 UTC dim...@gmail.com wrote:
> in the install.log, one sees
>
> [sagelib-9.3.beta4] /usr/local/include/flint/fmpz_poly_mat.h:105:44:
> error: unknown type name ‘flint_bitcnt_t’; did you mean
> ‘flin
in the install.log, one sees
[sagelib-9.3.beta4] /usr/local/include/flint/fmpz_poly_mat.h:105:44:
error: unknown type name ‘flint_bitcnt_t’; did you mean
‘flint_rand_t’?
[sagelib-9.3.beta4] 105 | slong len,
flint_bitcnt_t bits);
[sagelib-9.3.beta4] |
^~~
Thanks! That was the clue I needed. I had a *lot* of "zombie" processes I
needed to kill.
I finished the install:
This looks like the first time you are running Sage.
Cleaning up, do not interrupt this.
Done cleaning.
┌┐
│
this looks like:
https://lists.apple.com/archives/xcode-users/2012/Nov/msg00215.html
On Thu, 30 May 2019 03:51 Brian Ball, wrote:
> I am attempting to build Sage from source with Python 3.7.3
>
> Logs attached.
>
> I run
>
> ./configure --with-python=3
>
>
> and at the end I get the following:
On Tue, Jan 22, 2019 at 12:53 PM Devika Sugathan <
devikasugathan...@gmail.com> wrote:
>
> Please find the markupsafe-1.0.log file attached.
>
Thanks - if you look into what's in the file you will see a failure to
download the package source.
Try running make again, making sure your machine is o
Hello,
Were your computer connected to internet when you tried to build?
If not then try again with internet.
According to the log a problem occurred when trying to download files.
On 22.01.19 13:53, Devika Sugathan wrote:
> Please find the markupsafe-1.0.log file attached.
>
>
>
> On Mon,
Please find the markupsafe-1.0.log file attached.
On Mon, Jan 21, 2019 at 11:33 PM Dima Pasechnik wrote:
> Well, post the log file then: it's
> /home/devikasugathan/sage/logs/pkgs/markupsafe-1.0.log
>
>
> On Mon, Jan 21, 2019 at 5:43 PM Devika Sugathan <
> devikasugathan...@gmail.com> wrote:
>
Well, post the log file then: it's
/home/devikasugathan/sage/logs/pkgs/markupsafe-1.0.log
On Mon, Jan 21, 2019 at 5:43 PM Devika Sugathan
wrote:
> I tried to rebuild it got a new error with some other package.
> Error:
>
> Error building Sage.
>
> The following package(s) may have failed to bui
I tried to rebuild it got a new error with some other package.
Error:
Error building Sage.
The following package(s) may have failed to build (not necessarily
during this run of 'make all-start'):
* package: markupsafe-1.0
log file: /home/devikasugathan/sage/logs/pkgs/markupsafe-1.0.log
build
FWIW this is another report (the second I've seen in a week) of
https://trac.sagemath.org/ticket/26996 which has a potential fix awaiting
review: https://trac.sagemath.org/ticket/27016
The issue only occurs when trying to install the gfortran SPKG on Linux
systems (which is usually unnecessary sin
The error message seems to imply that you tried to install (part of)
Sage as a different user. Maybe the safest option is to delete your
installation completely:
rm -rf /home/devikasugathan/sage
and then try again.
--
You received this message because you are subscribed to the Google Groups
Hi
On Sun, 20 Jan 2019 at 12:25, Dima Pasechnik wrote:
>
> E.g. on a debian system you'd do
>
> sudo apt-get install binutils gcc g++ gfortran make m4 perl tar \git openssl
> libssl-dev
>
> (I think it's actually outdated, you should add yasm,
> libcurl4-openssl-dev, lzma-dev, xz to this list o
Le dimanche 20 janvier 2019 11:25:36 UTC+1, Dima Pasechnik a écrit :
>
>
> First of all, on a Linux system you almost never would need to build
> Sage-supplied gfortran, it's much easier to install a system-wide gfortran
> using the system's package manager.
> See
> http://doc.sagemath.org/html/
Dear Devika,
On Sun, Jan 20, 2019 at 9:59 AM Devika Sugathan
wrote:
> Hello,
> I'm a second year engineering student and would like to contribute to sage
> math. Can someone please help me with my doubts on how to proceed and
> please do give me an idea of the skill sets required for contributin
I tried some of the suggestions:
1) deleting SAGE_LOCAL/lib/libpython* and then make -> failed
2) make distclean && make build -> success
I still have to add the optional packages I need, but it's working.
Thanks.
David.
--
You received this message because you are subscribed to the Google Grou
yeah, I agree that a stale library is the most probable reason for this error.
--
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.
OK this looks suspiciously like
https://bugs.python.org/issue30074
which was fixed by
https://github.com/python/cpython/pull/1154
which should be in 2.7.14.
What I suspect is happening is that those failures happen when
people upgrade python from 2.7.13 (or older) to 2.7.14.
I have a feeling that
it would be interesting that try to debug this.
You most probably can get a working version by doing
make distclean
(making sure it succeeds!)
and then building,
so please do
cp -a
of the whole tree before doing this...
--
You received this message because you are subscribed to the Google
On 2017-12-07 15:13, Simon King wrote:
How to fix that?
This is a bug that several people have reported but I don't know how to
reproduce it.
make distclean and start again?
That works.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To u
Hi!
On a laptop that I haven't used for a while, I tried to upgrade Sage.
I.e., I did "git checkout develop", "git pull" and "make".
While building python2-2.7.15.p2, I get
[python2-2.7.14.p2] ImportError: No module named _ctypes
[python2-2.7.14.p2] ctypes module failed to import
and
[pyt
You need to perform an explicit installation of the Xcode command line tools. I
had the same error recently and that solved it.
--
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
Not really without some logs. But I guess I’ll try locally at some point…
when I have dealt with other problems...
François
> On 8/06/2016, at 10:33, Rebecca Miller wrote:
>
> Any thoughts on how to get around this?
>
--
You received this message because you are subscribed to the Google Grou
I'm having trouble building the newest beta.
I have updated my OS X and XCode to the latest version.
I have make distclean.
The error I'm getting is " Error installing package gcc-4.9.3.p1".
Any thoughts on how to get around this?
Thanks,
Rebecca M
--
You received this message because you ar
I have personally mostly eliminated the use of LD_LIBRARY_PATH from my linux
cluster
in favour of coding runpath in programs and libraries so that it is never an
issue (the only
exception would be openfoam I think).
In the case of gcc, it means changing the specs (as in gcc -dumpspecs) to
enfor
The compile completed. I have installed it in the "official" location. I
will now ask the user to run it through its paces.
Thanks for your help
Cindy
On Tuesday, January 13, 2015 at 11:16:29 AM UTC-6, crook...@gmail.com wrote:
>
> Thank you. I had forgotten to include the gcc "lib64" dire
Thank you. I had forgotten to include the gcc "lib64" directory in my
LD_LIBRARY_PATH. I have updated the appropriate module file. I will see
what happens next.
Cindy
On Monday, January 12, 2015 at 5:59:51 PM UTC-6, François wrote:
>
> It looks like something has gone wrong with LD_LIBRARY_P
It looks like something has gone wrong with LD_LIBRARY_PATH & co. This means
that libstdc++ found when running sage is from older version of gcc than the
one used
to compile sage. Here you find libstdc++ from the system (gcc-4.3.4 I presume)
rather
than whatever you used to compile.
I assume yo
The webpage http://trac.sagemath.org/wiki/Cygwin64Port indicates that
sage can now be built under cygwin64 almost out of the box. So, I tried,
but I failed...
Here are the problems I encountered, maybe someone with better computer
skills can see what is going on. My sage version is sage 6.4bet
It didn't seem to like just changing the effective group and failed almost
immediately trying to build gcc. I have started afresh with hpcapps as the
effective group and will see how far I can get.
On Thursday, January 8, 2015 at 3:38:28 PM UTC-6, François wrote:
>
> Nothing to do apart from “m
Nothing to do apart from “make”.
> On 9/01/2015, at 10:21, crooksc...@gmail.com wrote:
>
> Thank you. I will give it a try.
>
> Pardon my ignorance, but is there anything I have to do to pick up the "make"
> where I left off? Or, do I need to start from the beginning?
>
> Cindy
>
> On Thur
Thank you. I will give it a try.
Pardon my ignorance, but is there anything I have to do to pick up the
"make" where I left off? Or, do I need to start from the beginning?
Cindy
On Thursday, January 8, 2015 at 2:41:12 PM UTC-6, François wrote:
>
> Not completely sure since the error is abou
Not completely sure since the error is about the folder’s group permission but
that’s worth a try.
I am not sure how the “security” stuff has been implemented, it may be that the
group is outside
a deemed safe range.
Hum, this was implemented here:
https://github.com/sagemath/sage/blob/master/bui
OSorry, I should have said I am NOT part of the root group. I was typing
too fast.
--
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...@googl
O
> I am part of the root group. Below is the list of groups that I am part
> of:
>
gid=255(hpcadmin)
groups=255(hpcadmin),254(hpc),702(techgrp),23171(hpcapps),23173(hpctrain),42124(hpc-vasp),44679(hpc-reems),47919(hpc-sys),61860(rsmadmins)
The directories and software that I have mentio
That’s interesting, would you belong to an admin group or even the root group?
Or more likely you set the group ownership and permission for this folder to
something that’s
not acceptable for the python shipped by sage.
François
> On 9/01/2015, at 08:43, crooksc...@gmail.com wrote:
>
> I am tryi
I am trying to compile sage-6.4.1 for one of my users. I am working on a
SLES11 SP2 machine using gcc 4.9.2 and python 2.7.7. I am using my
personal account and I own the build directory and all of the
directories/files for gcc and python. I am still getting the following
error:
checking fo
configure: error: cannot import Python module "distutils".
It is not a permission problem as shown by the above line in the log.
I have explained the matter in a new post as the same situation prevails in
sage-6.4.
On Saturday, 7 June 2014 02:22:13 UTC-4, vdelecroix wrote:
>
> From your logs it
Hey people,
FreeBSD people do like to build their ports as root. The problem
described below could be easily fixed by simply removing the group write
permissions of all the files in the tarball upstream/pynac-0.3.2.tar.bz2.
It's not such a great deal if this isn't fixed by the time sage-6.3
come
Have a look at the commands
chown: change the owner/group
chmod: change permissions
What you have to do is to make /opt/sage-6.2 writable by you, not the
whole /opt. The simplest way, assuming that your username is alasdair,
is to change the owner of everything in /opt/sage-6.2 with
sudo chown
Thanks for that - I compiled it as root, so that it could write to the
directory /opt/sage-6.2. There should have been no permission problems.
(In essence, I did what I've always done: opened up a login shell as root,
and installed sage in the directory /opt/sage-x.y.
However! I've just di
>From your logs it seems to be a permission problem. What user own
/opt/sage-6.2 ? and what are the permissions ?
2014-06-07 3:15 UTC+02:00, Alasdair :
> Here's the error as reported during the compilation process:
>
> checking for python... /opt/sage-6.2/local/bin/python
>> checking for a version
Here's the error as reported during the compilation process:
checking for python... /opt/sage-6.2/local/bin/python
> checking for a version of Python >= '2.1.0'... sys:1: RuntimeWarning: not
> adding directory '' to sys.path since it's writable by an untrusted group.
> Untrusted users could put f
Aha - thank you!! I hadn't spotted that.
On Friday, December 6, 2013 12:51:36 PM UTC, Jeroen Demeyer wrote:
>
> On 2013-12-06 12:50, Owen Campbell wrote:
> > This is on a Macbook running Mavericks.
> Mavericks is not yet supported, but it should be supported in the
> upcoming Sage 5.13 version.
On 2013-12-06 12:50, Owen Campbell wrote:
This is on a Macbook running Mavericks.
Mavericks is not yet supported, but it should be supported in the
upcoming Sage 5.13 version. If you're feeling adventurous, you can check
out http://trac.sagemath.org/sage_trac/ticket/15433
--
You received this
Hi,
I'm completely new to sage and attempting to build it from source for the first
time.
I've hit the following build error:
checking for uintptr_t... yes
checking for the GMP library version 4.1.3 or above... no
configure: error: Cannot find GMP version 4.1.3 or higher.
GMP is the GNU Multi-P
Hi Jeroen,
Sorry for the delay, here is the output you requested
>From shell:
linux-vdso.so.1 (0x7fffd39e8000)
libmpc.so.3 => not found
libmpfr.so.4 => /usr/lib64/libmpfr.so.4 (0x7fa61e11)
libgmp.so.11 => not found
libdl.so.2 => /lib64/libdl.so.2 (0x7fa61df0800
1) Please give the output of the following command, both from a normal
shell and from within the Sage shell (sage --sh):
$ ldd /data2/sage-5.11/local/lib/gcc/x86_64-unknown-linux-gnu/4.7.3/cc1
2) Is the error reproducible (does it happen again if you run "make")?
3) Did you use MAKE="make -jN"
I tried building in from source and this is the error I got. any help would be
greatly appreciated.
Thanks!
Shahab
C compiler: gcc
C compiler version:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/data2/sage-5.11/local/lib/gcc
This is likely a build error bug on all systems which do not support SSE2 but
where building is done using the current version of gcc. It may also manifest
as a runtime error on binary builds installed on systems which do not support
SSE2 (but I have not tested that).
I am submitting this here
On 12/26/2012 11:23 AM, kcrisman wrote:
>
>
> On Wednesday, December 26, 2012 6:51:42 AM UTC-5, Jeroen Demeyer wrote:
>
> On 2012-12-25 20:22, Stephen Montgomery-Smith wrote:
> > When I am building sage-5.5 inside of sage-5.5
> What does this mean? If it means building Sage inside a
On Wednesday, December 26, 2012 6:51:42 AM UTC-5, Jeroen Demeyer wrote:
>
> On 2012-12-25 20:22, Stephen Montgomery-Smith wrote:
> > When I am building sage-5.5 inside of sage-5.5
> What does this mean? If it means building Sage inside a Sage shell,
> that's not supported and might indeed brea
On 2012-12-25 20:22, Stephen Montgomery-Smith wrote:
> When I am building sage-5.5 inside of sage-5.5
What does this mean? If it means building Sage inside a Sage shell,
that's not supported and might indeed break.
--
You received this message because you are subscribed to the Google Groups
"sag
On 12/25/2012 01:22 PM, Stephen Montgomery-Smith wrote:
> When I am building sage-5.5 inside of sage-5.5, I get the following
> error in my build log. I was able to build sage-5.5.rc1 with no
> problem. Am I unique with this problem? I am building under FreeBSD-8.2.
>
>
> gcc -DNDEBUG -g -fwra
When I am building sage-5.5 inside of sage-5.5, I get the following
error in my build log. I was able to build sage-5.5.rc1 with no
problem. Am I unique with this problem? I am building under FreeBSD-8.2.
gcc -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -pipe
-Wl,-rpath=/usr/ports/math/sa
It actually doesn't appear to give an error then. Under both root and
sageserver users in the chroot, I get the
... stuff + gap version + stuff ... 62+@&67542+@ngap>
prompt.
> What if you do "sage -sh" and try to run "gap -r -b -p -T -o G
> /opt/sage/data//extcode/gap/sage.g" manually? What
On Fri, Aug 12, 2011 at 2:54 PM, Jason B Hill wrote:
> RuntimeError: Unable to start gap because the command 'gap -r -b -p -T
> -o G /opt/sage/data//extcode/gap/sage.g' failed.
What if you do "sage -sh" and try to run "gap -r -b -p -T -o G
/opt/sage/data//extcode/gap/sage.g" manually? Wh
I'm wondering if anyone has any pointers on an error I'm getting.
In a schroot+debootstrap environment using Ubuntu 10.04 x86_64, I can
extract and run the binary of Sage 4.7 as root. I can also extract,
build, and run sage from source as root. Both of these fail in the
same way when I chown a bui
Hello,
I am having trouble building sage 4.6.1 on an iMac8,1 (2.4 GHz Intel Core 2
Duo) running OS X 10.5.8. Below is the last relevant output from the
compilation. Any help would be appreciated.
Thanks,
Jon
gcc -std=gnu99 -dynamiclib -Wl,-headerpad_max_install_names -undefined
dynamic_lookup
On 2010-11-07 11:50, rafaelf wrote:
> I don't know if this can be considered a bug: it seems that source
> files are generated via 'grep', but if the variable $GREP_OPTIONS
> contains '--color=always', these sources won't compile because of the
> extra characters which code the colors.
My personal
On 2010-11-07 13:33, Dr. David Kirkby wrote:
> On 11/ 7/10 10:50 AM, rafaelf wrote:
>> I don't know if this can be considered a bug: it seems that source
>> files are generated via 'grep', but if the variable $GREP_OPTIONS
>> contains '--color=always', these sources won't compile because of the
>>
On 11/ 7/10 10:50 AM, rafaelf wrote:
I don't know if this can be considered a bug: it seems that source
files are generated via 'grep', but if the variable $GREP_OPTIONS
contains '--color=always', these sources won't compile because of the
extra characters which code the colors.
So 'grep' in the
I don't know if this can be considered a bug: it seems that source
files are generated via 'grep', but if the variable $GREP_OPTIONS
contains '--color=always', these sources won't compile because of the
extra characters which code the colors.
So 'grep' in the build process should always be used wit
Following my attempts to build Sage, whilst inserting random delays in front of
gcc/g++/gfortran, an error occured with sqlite-3.6.22.
This rather surprised me, as the sqlite team takes testing very seriously (more
so than Sage),
http://www.sqlite.org/testing.html
with 647 times as much test
I am trying to build Sage 4.2.1 on a 32-bit 2.4 Ghz P4 running Ubuntu
9.04. The following error message is shown at completion:
--
Collecting examples for package ‘utils’
Running examples in package ‘utils’
Error: testing 'uti
I'm on Ubuntu-8.04 on an i386 Macbook using KDE. Kernel is 2.6.24-21-
server.
The install log is 45 megs, so here's just the last stage where it
failed:
STAGE 2-4-5: GEMV TUNE
make -f Makefile INSTALL_LOG/cMVRES pre=c 2>&1 | ./xatlas_tee
INSTALL_LOG/cMVTUNE.LOG
make[3]: *** [build] Error 255
Hi,
I am trying to build SAGE on a SiCortex machine with MIPS processors
running Linux Gentoo Base System release 1.12.12.
The build/install for libpari-gmp failed (results below). I believe it
is because -lgmp gets built using -n32 while libpari-gmp is being
built with the default n64. Is there
Just got this build error that told me to post it here:
mpn_extras.o:mpn_extras.c:(.text+0x2630): first defined here
collect2: ld returned 1 exit status
make[2]: *** [libflint.so] Error 1
make[2]: Leaving directory `/home/zarathustra/Download/sage-3.0.alpha3/
spkg/build/flint-1.06.p2/src'
Error b
- build failed for libiml @ linking stage
replacing '/local/home/ldemo/software/sage-2.8.3.rc2/local/lib/libgmp.so' with
'-lgmp' would solve the problem.
i guess the libtool script is responsible for the error. solving this by hand
however is hard because make (in the root tree) does rebuild the
Getting the following error when building the latest version of SAGE:
robert-millers-powerbook-g4-12:/Volumes/DATA/sage-1.7 robert$ sage -br
--
sage: Building and installing modified SAGE library files.
pyrexc --embed-positions -I/Volumes/
72 matches
Mail list logo
