I have no idea why you don't even have libcblas in the readelf output.
Are you trying to use your distro atlas or building Sage's own?
Is local/lib/libcblas.so broken (ldd -r output)?
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe
I am stumped. I will have to think it over for a bit. Output of "ld -v" please.
From: sage-devel@googlegroups.com [sage-devel@googlegroups.com] on behalf of
shol...@ualberta.ca [shol...@ualberta.ca]
Sent: Friday, 7 February 2014 15:51
To: sage-devel@googleg
OK I need a bigger gun. Try the same compilation again but add -Wl,-M,
then another time but with -Wl,--verbose
send me the output.
--
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, s
yes do both.
On Thu, 06 Feb 2014 18:36:58 shol...@ualberta.ca wrote:
> Hmmm it must have worked - no complaints, just another line. Run ldd or
> readelf on it? (complex_double.so)
>
> On Thursday, February 6, 2014 7:24:06 PM UTC-7, François wrote:
> > On Thu, 06 Feb 2014 18:13:37 sho...@ualberta.
Here it is:
(sage-sh) sbh@sbh-MacBookPro:sage-6.1.1$ ./sage -sh
Starting subshell with Sage environment variables set. Don't forget
to exit when you are done. Beware:
* Do not do anything with other copies of Sage on your system.
* Do not use this for installing Sage packages using "sage -i"
Hi, the only thing I built before this, as a prerequisite, was ppl (parma
polyhedra from bugseng) and which I included in the ld.so... path, etc.
However, I am doing absolutely nothing special to build sage: untar the
source, make. That's it. (I wish I knew more about what was going on)
He
I'm pretty sure I got the path outputed by the last compile right -
unfortunately,
(sage-sh) sbh@sbh-MacBookPro:src$ readelf -d
/home/sbh/SW/Sage6.1.1/sage-6.1.1/src/build/lib.linux-x86_64-2.7/sage/rings/complex_double.so
Dynamic section at offset 0x2bc68 contains 28 entries:
TagTy
Hmmm it must have worked - no complaints, just another line. Run ldd or
readelf on it? (complex_double.so)
On Thursday, February 6, 2014 7:24:06 PM UTC-7, François wrote:
>
> On Thu, 06 Feb 2014 18:13:37 sho...@ualberta.ca wrote:
> > Hi, the only thing I built before this, as a prerequisite, w
On Thu, 06 Feb 2014 18:13:37 shol...@ualberta.ca wrote:
> Hi, the only thing I built before this, as a prerequisite, was ppl (parma
> polyhedra from bugseng) and which I included in the ld.so... path, etc.
> However, I am doing absolutely nothing special to build sage: untar the
> source, make.
On Thu, 06 Feb 2014 17:34:48 shol...@ualberta.ca wrote:
> Thanks for all the effort - appreciate it.
>
> Here it is.
Thanks, nothing obviously suspicious. What does
readelf -d src/build/lib.linux-x86_64-2.7/sage/rings/complex_double.so
says?
--
You received this message because you are subscrib
Hi again,
So it didn't seem to complain about "./sage -ba" but still underlinked
library...
sbh@sbh-MacBookPro:~/SW/Sage6.1.1/sage-6.1.1$ ./sage -sh
Starting subshell with Sage environment variables set. Don't forget
to exit when you are done. Beware:
* Do not do anything with other copies o
Send over logs/pkgs/sage-6.1.1.log (compressed) for forensic.
On Thu, 06 Feb 2014 17:21:17 shol...@ualberta.ca wrote:
> Hi again,
>
> So it didn't seem to complain about "./sage -ba" but still underlinked
> library...
>
> sbh@sbh-MacBookPro:~/SW/Sage6.1.1/sage-6.1.1$ ./sage -sh
>
> Starting sub
Hi Jean-Pierre,
On Wed, Feb 05, 2014 at 06:00:58AM -0800, Jean-Pierre Flori wrote:
> > See also
> https://groups.google.com/d/msg/sage-devel/zlyuxWIcERQ/cLPRt2nufr4J
>
> You surely spotted that, but every compiled cython file is present twice in
> the sage tree.
Actually, when running "make l
Ah, that explains it. We just recently added a "configure" script, which is
why you didn't trip over that before.
--
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
For the record, I would like to confess that I've now figured the problem
out, and it was indeed a wonky environment variable: $PATH! Years ago when
I started using sage, I just added the sage root directory to my path, and
I've been doing it ever since. I now realize that is a bad idea.
The
Not healthy at all. Sage itself has not been properly linked.
Try "./sage -ba" and then see if complex_double.so is still
underlinked.
Francois
On Thu, 06 Feb 2014 13:09:10 shol...@ualberta.ca wrote:
> Well I've attached the config.log from
>
> ./local/var/tmp/sage/build/gsl-1.15.p1/src/config.l
Actually after a closer exam of a standard sage install,
the underdefinition of libraries (libgsl in particular)
is built in. Which means that some other part may be
broken. From the sage shell what does
ldd -r local/lib/python2.7/site-packages/sage/rings/complex_double.so
says?
Francois
--
Yo
On Thu, 06 Feb 2014 11:26:40 shol...@ualberta.ca wrote:
> Hi, it didn't seem like too big a file (otherwise I can use UbuntuOne) so I
> tar'd the log files up and they are attached.
Just the log gsl-1.15.p1.log would have been enough. OK so there is a
configuration and linking problem with your g
I had the same problem, which was solved by running
xcode-select --install
as Volker (and John Palmieri) suggested.
David
On Thu, Feb 6, 2014 at 9:09 AM, Volker Braun wrote:
> Do you have the xcode command line tools installed? Also, look into
> config.log as explained in the error message for
Still busted. Compress the build log of gsl found under logs/pkgs/ and put it
somewhere we can download it.
It may be too big for the list.
From: sage-devel@googlegroups.com [sage-devel@googlegroups.com] on behalf of
shol...@ualberta.ca [shol...@ualberta.c
Before you proceed with "make" to finish the install check that libgsl is
properly built this time.
ldd -r shouldn't find any undefined symbols and readelf should show libcblas or
libptcblas as one
of its output.
Francois
From: sage-devel@googlegroups.com
On Feb 6, 2014 10:16 AM, "Nils Bruin" wrote:
>
> On Thursday, February 6, 2014 8:56:09 AM UTC-8, William wrote:
>>
>> When we do eventually switch to Python 3, I want to modify the preparse
to allow
>> use of print as statement still
>
> That may be challenging. How should the following be parsed
+1 for gradually switching to py3 syntax
Its easy to get used to a print function. Old code can be auto-fixed with
2to3.
On Thursday, February 6, 2014 4:48:51 PM UTC, Nathann Cohen wrote:
>
> Hello everybody !
>
> My brain having shown its uselessness agsinst the problem I work on, I was
> fi
On Thursday, February 6, 2014 8:56:09 AM UTC-8, William wrote:
>
> When we do eventually switch to Python 3, I want to modify the preparse to
> allow
> use of print as statement still
That may be challenging. How should the following be parsed (and which are
syntax errors)?
print (1,2,3)
>
>
> Yep.I think in library code we should just do it though -- use
> print as a function.
>
> When we do eventually switch to Python 3, I want to modify the preparse to
> allow
> use of print as statement still, since for interactive use it is very
> natural (and not allowing
> it will
Boost compiles rather quickly, it is mostly just headers. Only a few
support libraries need to be compiled. It is somewhat large (currently 58MB
tar.bz2).
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop
On Thursday, February 6, 2014 8:38:28 AM UTC-8, Jeroen Demeyer wrote:
>
> On 2014-02-06 03:41, anne1.s...@gmail.com wrote:
> > On Tuesday, February 4, 2014 12:49:15 AM UTC-8, Jeroen Demeyer wrote:
> >
> > On 2014-02-04 09:20, Anne Schilling wrote:
> > > but it keeps reappearing.
>
On Thu, Feb 6, 2014 at 7:22 AM, Jean-Pierre Flori wrote:
>
>
> On Thursday, February 6, 2014 12:52:16 PM UTC+1, Volker Braun wrote:
>>
>> We only ship a partial boost library, afaik boost-python is not included.
>> Installing boost system-wide might work, but I've also had issues with
>> conflicti
On Thu, Feb 6, 2014 at 8:48 AM, Nathann Cohen wrote:
> Hello everybody !
>
> My brain having shown its uselessness agsinst the problem I work on, I was
> fishing for patches needing review.
>
> http://trac.sagemath.org/ticket/15784
>
> What do we do with this ?
>
> 1) Do we care if something is no
Hello everybody !
My brain having shown its uselessness agsinst the problem I work on, I was
fishing for patches needing review.
http://trac.sagemath.org/ticket/15784
What do we do with this ?
1) Do we care if something is not Python 3 compatible ?
2) Do we care if a patch touches everything ?
On 2014-02-06 03:41, anne1.schill...@gmail.com wrote:
On Tuesday, February 4, 2014 12:49:15 AM UTC-8, Jeroen Demeyer wrote:
On 2014-02-04 09:20, Anne Schilling wrote:
> but it keeps reappearing.
What you mean with this?
How can I tell make not to install semigroupe any longer then
Do you have the xcode command line tools installed? Also, look into
config.log as explained in the error message for details.
On Thursday, February 6, 2014 3:24:21 PM UTC, Ben Salisbury wrote:
>
> Hi!
>
> I am also having an issue building the latest version of Sage. An oddity
> is that whil
Hi!
I am also having an issue building the latest version of Sage. An oddity
is that while is does not build on my laptop, is does build on my desktop
(both of which are running OS X 10.9.1). Here is my output:
Bens-MacBook-Pro-3:sage-git Ben$ git checkout develop
Switched to branch 'devel
On Thursday, February 6, 2014 12:52:16 PM UTC+1, Volker Braun wrote:
>
> We only ship a partial boost library, afaik boost-python is not included.
> Installing boost system-wide might work, but I've also had issues with
> conflicting versions. But its worth a shot, for starters.
>
> Really, we
Boost python also has a shared library component that should be under
local/lib/libboost_python.so or so. But we don't install it correctly.
Probably because that would be harder with the cropped boost, you can
easily just copy some of the headers but to build a subset you need to deal
with the
On Thursday, February 6, 2014 12:52:16 PM UTC+1, Volker Braun wrote:
>
> We only ship a partial boost library, afaik boost-python is not included.
>
But there is a python folder in the src of the partial boost library. So I
thought boost-python was included...
sage-5.12/spkg/standard/boost_cro
We only ship a partial boost library, afaik boost-python is not included.
Installing boost system-wide might work, but I've also had issues with
conflicting versions. But its worth a shot, for starters.
Really, we should just ship all of boost. See also Martin Raum's recent
post...
On Thurs
Hi sage-devel,
Since the presentation of Vaucanson 2.0 at a Sage meeting in Paris, I am
trying to install it and use it from sage.
[1] http://wiki.sagemath.org/GroupeUtilisateursParis
[2] https://www.lrde.epita.fr/wiki/Vaucanson/Vaucanson2b3
I installed the experimental package gcc-4.8.1.spkg b
OK your gsl install is completely broken but atlas is there.
Can you try to re-install gsl? "./sage -f gsl" should do
the trick. If it still doesn't work post the build log from gsl (found under
logs/pkgs).
Francois
From: sage-devel@googlegroups.com [sage-
Hi,
I'd like to advertise these 3 job offers that should interest the sage
developper community.
In particular, some of the code development in these jobs concerns
parallelization of libraries
either used in sage (LinBox; fpLLL) or of potential interest for sage (FGb).
Part of the job include
i
40 matches
Mail list logo
