On 2011-12-12 00:15, Simon King wrote:
> Eventually, it was a one-line change in 29 packages. See #12131, which
> is now needing review. I made it a blocker for sage-5.0, but if people
> think that openSUSE 12.1 could already be supported by sage-4.8, I
> wouldn't object...
If it gets reviewed soon
Hi!
On 10 Dez., 11:17, Simon King wrote:
> Hi Volker,
>
> On 10 Dez., 11:10, Volker Braun wrote:
>
> > I would be in favor of making it a blocker. Its really only a one-line
> > change
>
> A one-line change that needs to be done in at least 12 packages,
> though.
Eventually, it was a one-line
On Sat, Dec 10, 2011 at 2:38 AM, Jeroen Demeyer wrote:
> On 2011-12-10 11:10, Volker Braun wrote:
>> I would be in favor of making it a blocker. Its really only a one-line
>> change and if you can make it work then we should bump all spkgs as soon
>> as possible. Jeroen, are you going to do anothe
On Saturday, December 10, 2011 10:38:34 AM UTC, Jeroen Demeyer wrote:
> What is the ticket number?
> Also, please explain the issue on the ticket, because I haven't been
> following the whole discussion here.
>
http://trac.sagemath.org/sage_trac/ticket/12131
--
To post to this group, send an e
On 2011-12-10 11:10, Volker Braun wrote:
> I would be in favor of making it a blocker. Its really only a one-line
> change and if you can make it work then we should bump all spkgs as soon
> as possible. Jeroen, are you going to do another alpha to try that out?
I could, yes. I have some other thi
Hi Volker,
On 10 Dez., 11:10, Volker Braun wrote:
> I would be in favor of making it a blocker. Its really only a one-line change
A one-line change that needs to be done in at least 12 packages,
though.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from
On Saturday, December 10, 2011 9:17:53 AM UTC, Simon King wrote:
>
> One question: If I remember correctly, openSUSE is one of the most
> common Linux distributions, at least in Germany.
>
Probably only in Germany ;-)
I would be in favor of making it a blocker. Its really only a one-line
change
Hi all!
I made some progress. I modified the following spkgs to use --
libdir="$SAGE_LOCAL/lib":
* readline (I used Volker's version)
* python
* mpir
* boehm_gc
* givaro
* mpfr
* mpfi
* r
Now, building the Sage library code fails, more precisely: M4RI.
I suppose that I'l
Yes, this would be gmp/mpir's fault.
On Friday, December 9, 2011 10:26:56 PM UTC, Simon King wrote:
>
> This time, libgmp.so.8 can't be found (although it is in SAGE_LOCAL/
> lib64. I assume this means that I have to modify gmp, not ecl
>
>
--
To post to this group, send an email to sage-devel@
Hi!
Things went quite far, actually the next error has only been in the
ecl-11.1.2.cvs2020.p0 spkg
The new install log is at
http://sage.math.washington.edu/home/SimonKing/SAGE/install_logs/4.8.alpha3/install.log.3
This time, libgmp.so.8 can't be found (although it is in SAGE_LOCAL/
lib64.
Hi Volker,
On 9 Dez., 22:12, Volker Braun wrote:
> Python's configure script would again need --libdir="$SAGE_LOCAL/lib"
> added.
I have done that, and now Sage came past Python and past Fortran. Now
I am looking forward for Atlas to build.
> We should probably fix all ocurences, even if it is
If you symlink $SAGE_LOCAL/lib64 -> $SAGE_LOCAL/lib then it should work.
Python's configure script would again need --libdir="$SAGE_LOCAL/lib"
added. We should probably fix all ocurences, even if it is painful. But for
now why not do the symlink kludge.
--
To post to this group, send an email
Hi!
On 9 Dez., 21:19, Simon King wrote:
> Things only broke in the python spkg.
And the problem is that libpython2.6.so.1.0 can't be found. But there
*is* libpython2.6.so.1.0, namely at $SAGE_ROOT/local/lib64/ !!
So, why is Sage not looking there?
Cheers,
Simon
--
To post to this group, send
Hi Volker,
On 9 Dez., 20:55, Volker Braun wrote:
> Just as a proof of concept, here is a readline spkg that does ./configure
> --libdir="$SAGE_LOCAL/lib" to fix the lib64 built-in:
>
> http://www.stp.dias.ie/~vbraun/Sage/spkg/readline-6.2.p2.spkg
>
> This will get you across the first hurdle but
Hi Volker,
On 9 Dez., 20:55, Volker Braun wrote:
> Just as a proof of concept, here is a readline spkg that does ./configure
> --libdir="$SAGE_LOCAL/lib" to fix the lib64 built-in:
>
> http://www.stp.dias.ie/~vbraun/Sage/spkg/readline-6.2.p2.spkg
>
> This will get you across the first hurdle but
On 9 Dez., 20:41, Simon King wrote:
> To my surprise, the second attempt to build sage-4.8.alpha3 now fails
> in the same way as sage-4.7.2. Strange. It is a pity that I didn't
> save the old install log!
If I understand correctly, libreadline.a is attempted to be created,
by
ar cr libreadline
Just as a proof of concept, here is a readline spkg that does ./configure
--libdir="$SAGE_LOCAL/lib" to fix the lib64 built-in:
http://www.stp.dias.ie/~vbraun/Sage/spkg/readline-6.2.p2.spkg
This will get you across the first hurdle but I highly doubt that the
remaining spkgs will build...
--
Hi!
To my surprise, the second attempt to build sage-4.8.alpha3 now fails
in the same way as sage-4.7.2. Strange. It is a pity that I didn't
save the old install log!
The new one is at
http://sage.math.washington.edu/home/SimonKing/SAGE/install_logs/4.8.alpha3/install.log
Cheers,
Simon
--
To
On 9 Dez., 09:13, "Georg S. Weber" wrote:
> On 8 Dez., 23:54, Volker Braun wrote:
>
> > I think I'll be able to say more if you show me the install.log ;-)
>
> I agree.
The install log for my failing attempt on sage-4.7.2 is here:
http://sage.math.washington.edu/home/SimonKing/SAGE/install_log
On Friday, 9 December 2011 18:52:49 UTC+8, Volker Braun wrote:
>
> On Friday, December 9, 2011 5:43:41 AM UTC, Dima Pasechnik wrote:
>>
>> well, can't we just use the system's readline instead?
>
>
> I think the reason is because OSX doesn't ship with readline since its
> GPL. Apple hacked in a r
On Dec 9, 2011 8:00 AM, "Georg S. Weber" wrote:
>
>
>
> On 9 Dez., 15:24, Julien Puydt wrote:
> > Le 09/12/2011 09:28, Georg S. Weber a crit :
>
> >
> > What about making sage use the system readline by default instead?
> >
> > Snark on #sagemath
>
> Hi Julien,
>
> unfortunately, there are some
On 9 Dez., 15:24, Julien Puydt wrote:
> Le 09/12/2011 09:28, Georg S. Weber a crit :
>
> What about making sage use the system readline by default instead?
>
> Snark on #sagemath
Hi Julien,
unfortunately, there are some OSes (I think Solaris was one of
them?!), where the default readline lib
Le 09/12/2011 09:28, Georg S. Weber a écrit :
after reading the discussion at http://trac.sagemath.org/sage_trac/ticket/10572
it occured to me that as a rule, rules comes with exceptions.
More precisely, renaming the readline library that is bundled with
sage as "sage-readline" and adapting the
> Can you look into your lib64 directory and tell us which spkgs got
> installed there?
I had a look at install.log:
grep "local/lib64/" install.log | grep "^/usr/bin/install" | cut -d
4 -f 2 | cut -d / -f 2 | cut -d . -f 1 | sort | uniq
gives:
ecl-11
libcord
libfplll
libfreetype
libgc
libgc
On 9 Dez., 12:05, Volker Braun wrote:
> Good observation. I made a trac ticket with the two possible fixes
> athttp://trac.sagemath.org/sage_trac/ticket/12131
>
Thank you.
> Can you look into your lib64 directory and tell us which spkgs got
> installed there?
I'm sorry, I can't. The unsuccessfu
Good observation. I made a trac ticket with the two possible fixes at
http://trac.sagemath.org/sage_trac/ticket/12131
Can you look into your lib64 directory and tell us which spkgs got
installed there?
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from t
On Friday, December 9, 2011 5:43:41 AM UTC, Dima Pasechnik wrote:
>
> well, can't we just use the system's readline instead?
I think the reason is because OSX doesn't ship with readline since its GPL.
Apple hacked in a readline replacement by ripping off some BSD code but its
not 100% compatibl
On Friday, December 9, 2011 8:28:26 AM UTC, Georg S. Weber wrote:
>
> I don't think there is any other spkg needing the readline
> library that comes with Sage, or is there?
>
Isn't pretty much every program with a stand-alone command line going to
use readline? A quick grep in $SAGE_LOCAL/bin fi
Dear Thomas.
On 9 Dez., 09:29, Thomas Hupfer
wrote:
> My workaround was to make one of the aforementioned directories a
> symlink to the other, after unpacking the sage sources but before
> building.
Thank you for your hint!
I forgot to bring my laptop to university, so, I can't test it now,
an
Hi,
I don't think that there still is a problem with readline on Suse.
after a lot of struggling, I managed to build sage 4.7.2 on openSuSE
12.1 (64bit) on my desktop computer and my laptop a few weeks ago.
Also see the thread
https://groups.google.com/group/sage-devel/browse_thread/thread/02e435
Hi,
after reading the discussion at http://trac.sagemath.org/sage_trac/ticket/10572
it occured to me that as a rule, rules comes with exceptions.
More precisely, renaming the readline library that is bundled with
sage as "sage-readline" and adapting the R spkg to look for "sage-
readline" (I don
On 8 Dez., 23:54, Volker Braun wrote:
> I think I'll be able to say more if you show me the install.log ;-)
I agree. Possibly, some lightly tweaked new readline spkg solves this
problem. But to have chance, a bit more information seems to be
needed.
Cheers,
Georg
--
To post to this group, s
well, can't we just use the system's readline instead?
I cannot imagine a recent Linux distribution for which such readline
doesn't work with Sage.
--
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...@goog
I think I'll be able to say more if you show me the install.log ;-)
--
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.com/group
Hi Volker,
On 8 Dez., 15:31, Volker Braun wrote:
> Well for once its not Suse's fault but our own for abusing LD_LIBRARY_PATH.
That may be to blame for the error that I find for sage-4.8.alpha3
(namely maxima not starting because it can't find mgnuplot).
But can the problem with sage-4.7.2 real
Hi Volker,
On 8 Dez., 15:31, Volker Braun wrote:
> Well for once its not Suse's fault but our own for abusing LD_LIBRARY_PATH.
> But having said that, if you want to install linux specifically for the
> purpose of running Sage then I would recommend Ubuntu or Fedora
I was explicitly deciding aga
Well for once its not Suse's fault but our own for abusing LD_LIBRARY_PATH.
But having said that, if you want to install linux specifically for the
purpose of running Sage then I would recommend Ubuntu or Fedora (depending
on whether your are less or more technically inclined). They just get mor
Hi Volker,
On 8 Dez., 15:02, Volker Braun wrote:
> No, its not a plug-in solution. After we adapt the compilerwrapper we need
> to remove the workarounds from the readline spkg, for example.
That sounds like my choice of a Linux distribution was a severe
mistake. I was much looking forward to fi
No, its not a plug-in solution. After we adapt the compilerwrapper we need
to remove the workarounds from the readline spkg, for example.
--
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.c
Hi Volker,
On 8 Dez., 14:06, Volker Braun wrote:
> Really, this is why LD_LIBRARY_PATH is considered a bad solution for
> forcing libraries that doesn't scale to big projects. This is not a new
> conclusion, many others have been burned there before. The known solution
> to this is to use rpaths.
The general problem with libreadline is that a lot of programs outside of
Sage use it. So many distributions break if we just LD_LIBRARY_PATH a
different version of libreadline, suddenly your shell doesn't work any more
etc. There are then hacks for Suse and Arch linux in the readline spkg to
p
41 matches
Mail list logo
