Thank you for your answer, this was indeed the issue. I'll share my
config.log next time I have a build issue. Thanks again.
Le samedi 18 décembre 2021 à 17:43:50 UTC, Matthias Koeppe a écrit :
> Try if "./configure --without-system-givaro" fixes this problem for you.
>
> This is likely the issu
Try if "./configure --without-system-givaro" fixes this problem for you.
This is likely the issue described in https://trac.sagemath.org/ticket/33042
On Saturday, December 18, 2021 at 5:21:54 AM UTC-8 kilo...@gmail.com wrote:
> First, I am sorry for the duplicate with ask.sagemath.org but I fee
Post config.log please
On Saturday, December 18, 2021 at 5:21:54 AM UTC-8 kilo...@gmail.com wrote:
> First, I am sorry for the duplicate with ask.sagemath.org but I feel this
> website is better and easier to share a log (and it was indicated to post
> here in the log !).
>
> I tried to recompi
As it says, you don't have enough memory to compile cypari
On Monday, November 8, 2021 at 9:15:48 AM UTC+1 fj.m...@gmail.com wrote:
> I get this error:
> [cypari-2.1.2] virtual memory exhausted: Cannot allocate memory
> [cypari-2.1.2] error: command '/usr/bin/gcc' failed with exit code 1
> wh
On 2019-04-14 22:42, Mark wrote:
include "cysignals/signals.pxi"
That's no longer supported. The proper way to use cysignals is
from cysignals.signals cimport sig_check # or whatever you need from
cysignals
--
You received this message because you are subscribed to the Google Groups
"sag
On Sun, Apr 14, 2019 at 10:58 PM Mark wrote:
>
> Hello,
>
> I'm getting the same "InternalError: Internal compiler error:
> 'sage/ext/interrupt.pxi' not found" when trying to build sage 8.7 with the
> command ./sage -b on MacOS Mojave. This happens after I added a new folder in
> sage-8.7/src/s
Hello,
I'm getting the same "InternalError: Internal compiler error:
'sage/ext/interrupt.pxi' not found" when trying to build sage 8.7 with the
command ./sage -b on MacOS Mojave. This happens after I added a new folder
in sage-8.7/src/sage.
As I understand it's deprecated, I replace
include "s
Le mercredi 4 avril 2018 18:13:50 UTC+2, Dima Pasechnik a écrit :
>
> Could you post your patch here?
> It might be useful...
--
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
Could you post your patch here?
It might be useful...
--
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 grou
Thank you !
I made a patch that change the version_string to "7.2.0" (I had to modify
the patch generated by "diff" by hand to make it work).
And now it compiles.
Sage-8.1 is compiled without any other problem.
Paul
Le mercredi 4 avril 2018 13:16:33 UTC+2, Dima Pasechnik a écrit :
>
> the usual
the usual way to add patches would be to put them into build/pkgs/numpy/patches/
at the end of the installation log you see instructions on setting the
environment to try running numpy installation.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group
I think that you're right, the error comes from this error message that
break the configuration test of numpy.
This problem appears only in the numpy package. Every other package compile
without problem.
Do you know if it's possible to recompile the numpy package where it was
left, without re-
The error message
/etc/init.d/xprint: Command not found.
repeats many times and this appears to break the configuration tests numpy is
running.
In the end it fails as e.g. it is unable to confirm that OpenBLAS works.
And then it finishes with the error saying that it cannot find Fortran co
On Saturday, March 31, 2018 at 1:02:51 AM UTC+1, Samuel Lelievre wrote:
>
>
>
> Le jeudi 29 mars 2018 18:18:09 UTC+2, Paul Mercat a écrit :
> >
> > Hello,
> >
> > I've tried to compile sage-8.1 on a linux server, and I get
> > the following error:
> >
> > Error building Sage.
> >
> > How can I so
On Friday, March 30, 2018 at 8:12:12 PM UTC+1, Paul Mercat wrote:
>
> I tried to do "./make -i numpy", but I get the same error...
What compiler is being used? "same error" with gcc 7.2, or still with gcc
4.8.5?
The latter would be very odd.
--
You received this message because you are sub
Le jeudi 29 mars 2018 18:18:09 UTC+2, Paul Mercat a écrit :
>
> Hello,
>
> I've tried to compile sage-8.1 on a linux server, and I get
> the following error:
>
> Error building Sage.
>
> How can I solve this problem ?
What version of Linux is this server running?
Did other versions of Sage compi
I tried to do "./make -i numpy", but I get the same 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.com.
To post to th
This looks OK (there were download errors, but apparently it did work out
in the end
looking at the tail of this file shows
Successfully installed gcc-7.2.0
Deleting temporary build directory
/home/paul.mercat/sage-8.1/local/var/tmp/sage/build/gcc-7.2.0
Finished installing gcc-7.2.0.spkg
Now, wh
https://drive.google.com/open?id=1hHDMc9uEL9_SYrmq8Z6JPPFphL8uBzZ3
Le vendredi 30 mars 2018 17:10:24 UTC+2, Dima Pasechnik a écrit :
>
>
>
> On Friday, March 30, 2018 at 3:13:17 PM UTC+1, Paul Mercat wrote:
>>
>> Here is the file config.log
>>
>
> something does not match here, as this log tells t
On Friday, March 30, 2018 at 3:13:17 PM UTC+1, Paul Mercat wrote:
>
> Here is the file config.log
>
something does not match here, as this log tells that it's getting gcc 7.2
installed, but your numpy log still refers to gcc 4.8.5
Has the installation of gcc package been successful?
(look for
Here is the file config.log
Le vendredi 30 mars 2018 16:07:12 UTC+2, Paul Mercat a écrit :
>
> Hi,
>
>
> There is no such file logs/pkgs/config.log.
>
> I tried to recompile with the option SAGE_INSTALL_GCC='yes', but I get the
> same error:
>
>
> real43m24.500s
>
Hi,
There is no such file logs/pkgs/config.log.
I tried to recompile with the option SAGE_INSTALL_GCC='yes', but I get the
same error:
real43m24.500s
This looks like a gcc/gfortran problem.
Could you post also
logs/pkgs/config.log ?
You might consider forcing building gcc, see SAGE_INSTALL_GCC in
http://doc.sagemath.org/html/en/installation/source.html#environment-variables
On Thursday, March 29, 2018 at 5:18:09 PM UTC+1, Paul Mercat wrote:
You're right, I have found where I call sage/ext/interrupt.pxi and changed
it and now it works.
The compiler gave no information on where is the problem. It's a little bit
annoying...
Le dimanche 4 mars 2018 00:41:45 UTC+1, Dima Pasechnik a écrit :
>
>
> On Saturday, March 3, 2018 at 5:19:37 PM
On Saturday, March 3, 2018 at 5:19:37 PM UTC, Paul Mercat wrote:
>
>
> I'm trying to merge the ticket #21072 (that currently work with sage 7.3)
> with sage 8.1, but I get the following error, and I don't know why and what
> to do.
>
I believe that this functionality is now handled by cygsignal
this is now #21482
On Monday, September 12, 2016 at 5:50:11 PM UTC, leif wrote:
>
> Volker Braun wrote:
> > The error is in an optional part that isn't compiled by default; I guess
> > its the maple interface? The config contains
> >
> > checking for MAPLE >= 9.0... ./configure: line 18187:
>
I saw that you have already put useful part of the log on the ticket.
Thank you.
Le lundi 12 septembre 2016 19:22:42 UTC+2, leif a écrit :
>
>
>
> Presumably works if you temporarily hide your MAPLE.
>
> (I'll put a note onto the upgrade ticket [1]; you could *attach* ;-)
> your log there as wel
I also have problems with linbox since the update, I have attached the log
to #17635.
Le lundi 12 septembre 2016 19:50:11 UTC+2, leif a écrit :
>
> Volker Braun wrote:
> > The error is in an optional part that isn't compiled by default; I guess
> > its the maple interface? The config contains
Volker Braun wrote:
> The error is in an optional part that isn't compiled by default; I guess
> its the maple interface? The config contains
>
> checking for MAPLE >= 9.0... ./configure: line 18187:
> /bin/maple.system.type: No such file or directory
> found
>
> We should probably configure linb
David Coudert wrote:
> Hello,
>
> I have the following error with linbox during the compilation of sage
> 7.4.beta4.
>> ./lb-domain-type.h:31:33: fatal error: linbox/field/givaro.h: No such
> file or directory
>
> I was successfully able to compile 7.3, 7.4.beta1 and 7.4.beta2 on the
> same compu
The error is in an optional part that isn't compiled by default; I guess
its the maple interface? The config contains
checking for MAPLE >= 9.0... ./configure: line 18187:
/bin/maple.system.type: No such file or directory
found
We should probably configure linbox with --with-maple=no
On Mond
An opportunity to give back what I learned. YMMV.
On Sunday, March 16, 2014 7:32:28 PM UTC+1, Christian Stump wrote:
>
> Prequestion 2: What is the default way of checking on which Sage version a
> branch on trac is built on?
>
The date of the last commit is the simplest way (look at the resp.
> PEP 0263 says explicitly that the encoding magic can occur either on the
> first or on the second line, presumably for cases like this, so it looks
> like it is worth trying.
>
(If it already tries to decode the first line before looking at the second
line to see if it specifies an encoding
Op woensdag 18 september 2013 10:22:04 UTC+1 schreef Jeroen Demeyer:
>
> On 2013-09-18 07:20, Dima Pasechnik wrote:
> > accoring to http://www.python.org/dev/peps/pep-0263/
> > $SAGE_LOCAL/bin/hg might benefit from the 2nd line saying
> > # -*- coding: latin-1 -*-
> > (or # -*- coding: utf-8 -*
On 2013-09-18 07:20, Dima Pasechnik wrote:
accoring to http://www.python.org/dev/peps/pep-0263/
$SAGE_LOCAL/bin/hg might benefit from the 2nd line saying
# -*- coding: latin-1 -*-
(or # -*- coding: utf-8 -*-) ?
That wouldn't help since the offending character is on the *first* line,
before the
Hi,
I think I also had similar problems because of accented letters in my
building path.
I don't know if that would be easy to fix, but you can always build Sage
lesewhere and then move it back where you want to store it even if that
includes accented letters.
Best,
JP
On Wednesday, September
Hi,
Jan Groenewald wrote:
> It might be the é in your path, though \xc3 is something else:
> In [1]: print u'\xc3'
> Ã
0xC3 is the first byte of the UTF-8 encoding of 'é'.
--
Marc
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe
On 2013-09-17, ti tims wrote:
> Hi all @sage
>
>
> I do not succeed in compiling sage 5.11 on debian testing. here is the output
>
> copying build/scripts-2.7/hg ->
> /home/tm202135/Téléchargements/sage-5.11/local/bin
> changing mode of /home/tm202135/Téléchargements/sage-5.11/local/bin/hg to 75
Hi John,
On Tue, Aug 20, 2013 at 04:16:10PM -0700, John H Palmieri wrote:
>On Tuesday, August 20, 2013 6:18:29 AM UTC-7, mors...@gmail.com wrote:
>
> Hi, I'm trying to install SAGE and started with a version of XCode 3.21
> This failed, so I installed the newest from the ap
On Tuesday, August 20, 2013 6:18:29 AM UTC-7, mors...@gmail.com wrote:
>
>
> Hi, I'm trying to install SAGE and started with a version of XCode 3.21
> This failed, so I installed the newest from the apple store (without
> deleting
> the older version).
After you installed the newest versio
On 7 Mai, 19:09, "Nicolas M. Thiery" wrote:
> Hi!
>
> I have a user who installed Sage 4.4 (binary) on a MacBook Pro. She
> used sage -clone to create a new branch for creating a ticket. The
> compilation fails with the same error message about MulHIUL as in:
>
> http://trac.sagem
Here is mine :
gcc version 4.3.2 20081105 (Red Hat 4.3.2-7) (GCC)
Nathann
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.c
On Dec 29, 2009, at 5:07 AM, Nathann Cohen wrote:
> Well, after taking a look at file modules_list, would it be so bad if
> we were just adding at the end of the definition of this huge list :
>
> if ( the correct library is installed ):
>ext_modules.append( whatever you want)
>
> The problem
On Tue, Dec 29, 2009 at 5:01 PM, Georg S. Weber
wrote:
> +10 from my side for adding this feature to Sage (the "how" has yet
> to be discussed, why not use vanilla Python 2.7?)
Python 2.7 isn't out yet -- only 2.7 alpha1.
--Mike
--
To post to this group, send an email to sage-devel@googlegrou
On 29 Dez., 15:17, Mike Hansen wrote:
> Hello,
>
> On Tue, Dec 29, 2009 at 7:07 AM, Nathann Cohen
> wrote:
> > Well, after taking a look at file modules_list, would it be so bad if
> > we were just adding at the end of the definition of this huge list :
>
> > if ( the correct library is instal
Straightforward indeed O_o
Is there a special procedure for such things, or do we just create an
usual Sage ticket with the same patch (rewritten using hg) ?
Nathann
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-dev
Hello,
On Tue, Dec 29, 2009 at 7:07 AM, Nathann Cohen wrote:
> Well, after taking a look at file modules_list, would it be so bad if
> we were just adding at the end of the definition of this huge list :
>
> if ( the correct library is installed ):
> ext_modules.append( whatever you want)
>
>
Well, after taking a look at file modules_list, would it be so bad if
we were just adding at the end of the definition of this huge list :
if ( the correct library is installed ):
ext_modules.append( whatever you want)
The problem just comes from the fact that this file is a very long
list, a
On Tue, 29 Dec 2009 23:05:47 Nathann Cohen wrote:
> Why is is so troublesome for you ? Wouldn't it be easier to fix this
> Sage issue instead of dealing with CBC or GLPK as they are for the
> moment ? :-)
Fixing the sage issue would certainly be a good thing. From the point
of view of packaging sag
Why is is so troublesome for you ? Wouldn't it be easier to fix this
Sage issue instead of dealing with CBC or GLPK as they are for the
moment ? :-)
Nathann
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubsc
On Aug 30, 11:21 am, William Stein wrote:
/ ...
> Actually, there is little interaction between the compiled Sage and the
> linux install. Sage is almost self-contained.
Yes, but when compiling from source, the relationship with the
compiler can only be described as intimate.
> > Since my fi
On Sun, Aug 30, 2009 at 11:04 AM, arachnoid wrote:
>
>
>
> On Aug 30, 8:49 am, William Stein wrote:
> > On Sun, Aug 30, 2009 at 3:04 AM, arachnoid wrote:
> >
> > > On a Dell desktop with 2 GB RAM and plenty of free HDD space, Sage
> > > compilation fails. Here is the end of the installation log
On Aug 30, 8:49 am, William Stein wrote:
> On Sun, Aug 30, 2009 at 3:04 AM, arachnoid wrote:
>
> > On a Dell desktop with 2 GB RAM and plenty of free HDD space, Sage
> > compilation fails. Here is the end of the installation log:
>
> What exact compiler are you using (output of gcc -v)?
$ gcc
On Sun, Aug 30, 2009 at 3:04 AM, arachnoid wrote:
>
> On a Dell desktop with 2 GB RAM and plenty of free HDD space, Sage
> compilation fails. Here is the end of the installation log:
What exact compiler are you using (output of gcc -v)? Is there any
possibility to use a different compiler?
>
On 26 Mrz., 09:10, bourbabis wrote:
> Hi.
>
> memtest86+ reports some memory errors...
> I'm going to fix that.
> Thorough inspection of my SCSI hard drive (badblocks -w
> + the adaptec tool) doesn't report any problem.
>
> I've of course tried to install first a prebuild sage binary,
> but unf
Hi.
memtest86+ reports some memory errors...
I'm going to fix that.
Thorough inspection of my SCSI hard drive (badblocks -w
+ the adaptec tool) doesn't report any problem.
I've of course tried to install first a prebuild sage binary,
but unfortunately my processor doesn't support some
sse* instr
Hmmm,
looking at that log file (thanks for posting it!) there is another
possibility (than a "dying hard drive or bad memory") --- we have had
seen such "internal compiler errors" in case the CPU overheats. The
line "Target: i486-linux-gnu" posted above supports this assumption
--- I fear it woul
2009/3/25 bourbabis :
>
> Hi SAGE teamT.
>
> So I've tried to rebuild from scratch.
> I've encountered several times this error message :
>
> python: can't open file '/opt/sage-3.4/devel/sage/doc/common/
> builder.py'
> (See lines number 31833 and 68522 from the log file).
>
> Notice I've been abl
Hi SAGE teamT.
So I've tried to rebuild from scratch.
I've encountered several times this error message :
python: can't open file '/opt/sage-3.4/devel/sage/doc/common/
builder.py'
(See lines number 31833 and 68522 from the log file).
Notice I've been able to build "atlas" and "freetype" in prev
Hi.
1) Sorry, I've forgotten to switch to LANG=en
before.
2) I'm going to rebuild from scratch and
post the whole log. I use an old computer,
so it will take some time.
3)
"ls /opt/sage-3.4/spkg/installed" returns :
atlas-3.8.3.p0
blas-20070724
bzip2-1.0.5
conway_polynomials-0.2
cython-0.10.3
Well,
"Aucun fichier ou répertoire de ce type" is french for "No file or
directory of this type". So some headers cannot be found, and this
strongly suggests that something went wrong before the Sage library
(sage-3.4.spkg) was processed.
Is the install log overwritten by subsequent make "runs"?
2009/3/24 William Stein :
>
> On Tue, Mar 24, 2009 at 8:02 AM, bourbabis wrote:
>>
>> Hello SAGE people.
>>
>> Everything is in the title. Several attempts with "make" leading to
>> the exact same point of failure.
>>
>> The install log file :
>> http://download206.mediafire.com/nzjxxh0x9jmg/4lj
On Tue, Mar 24, 2009 at 8:02 AM, bourbabis wrote:
>
> Hello SAGE people.
>
> Everything is in the title. Several attempts with "make" leading to
> the exact same point of failure.
>
> The install log file :
> http://download206.mediafire.com/nzjxxh0x9jmg/4ljzjnh2mdd/install.log
That log only sh
On Jan 17, 12:48 pm, luis wrote:
> Mabshoff, William,
Hi,
> Yes, enforcing the use of the original compiler (/usr/bin/gcc)
> the "flint" compilation problem disappears.
Ok, but I am still curious why this fails for you with the other
compiler. Having compiled Sage with self compiled gcc 4.
Mabshoff, William,
Yes, enforcing the use of the original compiler (/usr/bin/gcc)
the "flint" compilation problem disappears.
Thanks,
Luis
On Jan 17, 9:41 pm, William Stein wrote:
> On Sat, Jan 17, 2009 at 11:42 AM, mabshoff wrote:
>
> > On Jan 17, 11:34 am, luis wrote:
> >> Hi,
>
> >>
On Sat, Jan 17, 2009 at 11:42 AM, mabshoff wrote:
>
>
>
> On Jan 17, 11:34 am, luis wrote:
>> Hi,
>>
>> In compiling sage on a linux debian (stable) I have a problem
>> with "flint-1.0.13.p0".
>>
>> Some lines of the install.log file are included hereafter.
>>
>> Thanks,
>>
>> Luis
>
>
>
>> Fin
On Jan 17, 11:34 am, luis wrote:
> Hi,
>
> In compiling sage on a linux debian (stable) I have a problem
> with "flint-1.0.13.p0".
>
> Some lines of the install.log file are included hereafter.
>
> Thanks,
>
> Luis
> Finished extraction
>
On Mon, Dec 8, 2008 at 12:53 PM, William Stein <[EMAIL PROTECTED]> wrote:
> On Mon, Dec 8, 2008 at 12:51 PM, Clint Whaley <[EMAIL PROTECTED]> wrote:
>> William,
>>
>>>Is there an easy way to build an ATLAS but without it using any sse
>>>(or other "modern") optimizations?
>>>
>>>See the little dis
On Mon, Dec 8, 2008 at 12:51 PM, Clint Whaley <[EMAIL PROTECTED]> wrote:
> William,
>
>>Is there an easy way to build an ATLAS but without it using any sse
>>(or other "modern") optimizations?
>>
>>See the little discussion below. The main issue is that I want to be
>>able to build a binary on a
>
> It would be interesting to figure out how to build binaries on
> sage.math that don't require SSE. I have no clue how to do this?
> Does anybody have any ideas?
>
> After searching around for a while, my best idea is to ask Clint
> Whaley how to build Atlas in such a way that it doesn't u
On Mon, Dec 8, 2008 at 4:35 AM, bourbabis <[EMAIL PROTECTED]> wrote:
>
> Hello.
>
> OK, you're probably right, it's a hardware problem. It's the
> most credible explanation, even if the exact circumstances
> triggering it will remain obscure. I will follow your suggestions
> and try a step by step
On Dec 8, 4:35 am, bourbabis <[EMAIL PROTECTED]> wrote:
> Hello.
Hi bourbabis,
> OK, you're probably right, it's a hardware problem.
To elaborate on the remarks by William: compiling ATLAS is some of the
most demanding things you can do to a CPU since most of it has next to
no IO and it attem
Hello.
OK, you're probably right, it's a hardware problem. It's the
most credible explanation, even if the exact circumstances
triggering it will remain obscure. I will follow your suggestions
and try a step by step compilation, following the script.
Just a precision, this is not I absolutely *w
On Sat, Dec 6, 2008 at 3:10 AM, bourbabis <[EMAIL PROTECTED]> wrote:
>
> Hello.
> Sorry, I should have exposed my case more thoroughly.
>
> You said : "Why are you trying to building
> again after compilation of a given package fails? Won't it just fail
> again?"
>
> No. For example, I've tried t
Hello.
Sorry, I should have exposed my case more thoroughly.
You said : "Why are you trying to building
again after compilation of a given package fails? Won't it just fail
again?"
No. For example, I've tried to compile Atlas (the process takes
about 5 hours), may be 4 or 5 times and the last a
On Fri, Dec 5, 2008 at 4:26 PM, bourbabis <[EMAIL PROTECTED]> wrote:
>
> Hello folks.
>
> I'm afraid this is may be not possible, but however
> here is a suggestion. I strive to compile Sage
> on a somewhat weak/outdated hardware.
> Actually, the problem is not at all that
> compilation as a whole
On Jun 23, 5:01 pm, I wrote:
> Hi,
>
> I'm getting a compilation error for R when trying to compile 3.0.3.
> What I hope is the relevant piece of the installation log is below.
> Any help is greatly appreciated.
>
> Thanks.--Rob
>
> Configuring R for OSX
> checking build system type... i
On Jun 23, 10:24 pm, Rob <[EMAIL PROTECTED]> wrote:
> On Jun 23, 5:08 pm, mabshoff <[EMAIL PROTECTED]> wrote:
>
> > any chance you have Fink or MacPorts installed?
>
> I had fink installed years ago, but it's not in my path any longer.
> Did it leave something around that's causing this problem?
On Jun 23, 5:08 pm, mabshoff <[EMAIL PROTECTED]> wrote:
> any chance you have Fink or MacPorts installed?
I had fink installed years ago, but it's not in my path any longer.
Did it leave something around that's causing this problem? I'll try
deleting anything that you can suggest.
Thanks.--R
On Jun 23, 2:01 pm, Rob <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I'm getting a compilation error for R when trying to compile 3.0.3.
> What I hope is the relevant piece of the installation log is below.
> Any help is greatly appreciated.
>
> Thanks.--Rob
hi Rob,
any chance you have Fink or MacP
Hi Michael,
Thanks for the update, I will keep an eye on the next release. I
started to use (and enjoy working with) the binary SAGE package ;)
Cheers
Amir
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from t
On Jun 22, 2:30 am, Amir Saffari <[EMAIL PROTECTED]> wrote:
> Hi,
Hi Amir,
> First of all, thanks for developing this great package. I am trying to
> build the sage from source on my machine at work and it seems that
> there is some problem with "gmp" installation. I'm installing it on my
> ho
On Tue, Jun 10, 2008 at 7:41 AM, IzI <[EMAIL PROTECTED]> wrote:
Hi Iztok,
> I humbly apologize for bothering you with such a trivial problem, the
> libc6-dev package was missing on my installation.
>
No problem and don't worry about it since everybody around here has had
something very similar
I humbly apologize for bothering you with such a trivial problem, the
libc6-dev package was missing on my installation.
Iztok
On Jun 9, 6:58 pm, mabshoff <[EMAIL PROTECTED]> wrote:
> On Jun 9, 2:43 am, IzI <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> > I would prefer to submit the bug as a Trac issue,
I will post the log tomorrow (I used a borrowed PC with P4 and Ubuntu
8.04 for a trial installation), so I will try to write some other
details today.
The bug is not related to the PIL package, it was used only as an
example for repeating the bug.
I got the same error (limits.h line 122) while in
On Jun 9, 2:43 am, IzI <[EMAIL PROTECTED]> wrote:
Hi,
> I would prefer to submit the bug as a Trac issue, but was not able to
> subscribe.
>
> Steps to reproduce the problem:
> 1.) download and install SAGE to a 32bit (P4) Ubuntu 8.04
> 2.) wgethttp://www.sagemath.org/packages/experimental/PIL-1
On 4/22/08, William Stein <[EMAIL PROTECTED]> wrote:
> > > > export CC=gcc-4.3
> > > > export CXX=g++-4.3
>
>
> Gonzalo -- just out of curiosity are you willing to do all the work to fix
> the issues with CC not being honored? Or are you just saying "I think
> it should be this way; you g
Hi there,
I've added patch suggestions for PolyBoRi to the Tracs:
http://trac.sagemath.org/sage_trac/ticket/2999
http://trac.sagemath.org/sage_trac/ticket/3000
BTW, I would have preferred to have tickets per package not per
variable. This way, the names for the patch files will be very long,
as
On 4/22/08, mabshoff <[EMAIL PROTECTED]> wrote:
> > > Ideally, it would be nice to (e.g)
> >
> > > export CC=gcc-4.3
> > > export CXX=g++-4.3
>
>
> I don't like this and I don't think it is worth fixing in the first
> place since this introduces potentially subtle bugs since we might end
>
On Apr 22, 7:05 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> On Tue, Apr 22, 2008 at 9:47 AM, mabshoff
>
>
>
> <[EMAIL PROTECTED]> wrote:
>
> > On Apr 22, 6:23 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> > > On Tue, Apr 22, 2008 at 9:19 AM, Gonzalo Tornaria
>
> > Hi,
>
> > > <[EMAIL
On Tue, Apr 22, 2008 at 9:47 AM, mabshoff
<[EMAIL PROTECTED]> wrote:
>
>
>
> On Apr 22, 6:23 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> > On Tue, Apr 22, 2008 at 9:19 AM, Gonzalo Tornaria
>
> Hi,
>
>
> > <[EMAIL PROTECTED]> wrote:
> >
> > > Ideally, it would be nice to (e.g)
> >
> >
On Apr 22, 6:23 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> On Tue, Apr 22, 2008 at 9:19 AM, Gonzalo Tornaria
Hi,
> <[EMAIL PROTECTED]> wrote:
>
> > Ideally, it would be nice to (e.g)
>
> > export CC=gcc-4.3
> > export CXX=g++-4.3
I don't like this and I don't think it is worth fixing
On Tue, Apr 22, 2008 at 9:19 AM, Gonzalo Tornaria
<[EMAIL PROTECTED]> wrote:
>
> Ideally, it would be nice to (e.g)
>
> export CC=gcc-4.3
> export CXX=g++-4.3
> export F77=gfortran-4.3
I agree. That was always the intention. I'm glad you've gone
through and tested what does and doesn't obey
William Stein wrote:
>
> On 9/28/07, Eliz <[EMAIL PROTECTED]> wrote:
>>
>> I still can't build flint-0.2.p3.spkg.
>
> Looking at your first message, I just realized that
> you are building using
>
> "gcc version 4.3.0 20070531 (experimental)"
>
> This is the unstable active development version of
I relinked my gcc to gcc-4.1 and the compilation works !!!
Thanks !!
Elizabeth
On Sep 28, 12:00 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> On 9/28/07, Eliz <[EMAIL PROTECTED]> wrote:
>
>
>
> > I still can't build flint-0.2.p3.spkg.
>
> Looking at your first message, I just realized that
>
On 9/28/07, Eliz <[EMAIL PROTECTED]> wrote:
>
> I still can't build flint-0.2.p3.spkg.
Looking at your first message, I just realized that
you are building using
"gcc version 4.3.0 20070531 (experimental)"
This is the unstable active development version of GCC. It's
highly unlikely to actually
I still can't build flint-0.2.p3.spkg.
Here is the start of the error messages relating to building
flint-0.2.p3:
g++ -fPIC -shared -fPIC -o libflint.so mpn_extras.o Z.o memory-
manager.o Z_mpn.o ZmodF.o ZmodF_mul.o ZmodF_mul-tuning.o fmpz.o
fmpz_poly.o mpz_poly-tuning.o mpz_poly.o ZmodF_poly.o
Hello,
I've posted a new spkg for flint here:
http://sagemath.org/packages/standard/flint-0.2.p3.spkg
which takes into account all Bill's
remarks below. Please try it out (by putting it in SAGE_ROOT/spkg/standard/
and typing "make") on your system, and let us know if it fixes the problem for
Well my FLINT makefile *still* seems to have INCS = -I"/usr/include",
so if that directory contains gmp.h on her machine, then it could well
be picking up the wrong version of GMP.
FLINT builds on sage.math without adding this directory to the INCS,
so I'd say try removing that directory from the
>> test-support.o: In function `__gmpz_fits_uint_p':
>> test-support.c:(.text+0x0): multiple definition of
>> `__gmpz_fits_uint_p'
>> Z_mpn-test.o:Z_mpn-test.c:(.text+0x0): first defined here
>> test-support.o: In function `__gmpz_fits_ulong_p':
>>
>> Here is the end of the install.log
>>
>> ZmodF
1 - 100 of 103 matches
Mail list logo
