On Nov 11, 12:23 pm, Tim Joseph Dumol wrote:
> The GCC error can be fixed by copying libgcc from the system libraries as
> so:
>
> $ cp /usr/lib/libgcc_s.so /opt/sage-4.2/local/lib/gcc-lib//4.0.3/
Thank you a lot, now I compiled sage-4.2 and indeed all the humble
plot behaviour is gone :) :) :)
Henryk Trappmann wrote:
> Yes, I used 4.1.1.
> Unfortunately I can not use neither the precompiled 32bit 4.2 - it is
> compiled with some SSE or so instructions which my AMD does not
> support - nor with the source, it gets me some error that some GCC
> symbol can not be found when building R - no
The GCC error can be fixed by copying libgcc from the system libraries as
so:
$ cp /usr/lib/libgcc_s.so /opt/sage-4.2/local/lib/gcc-lib//4.0.3/
- Tim Joseph Dumol
http://timdumol.com
On Wed, Nov 11, 2009 at 4:04 PM, Henryk Trappmann
wrote:
>
> Yes, I used 4.1.1.
> Unfortunately I can not use
Yes, I used 4.1.1.
Unfortunately I can not use neither the precompiled 32bit 4.2 - it is
compiled with some SSE or so instructions which my AMD does not
support - nor with the source, it gets me some error that some GCC
symbol can not be found when building R - nor can I try my original
example wi
kcrisman wrote:
> This must be a matplotlib issue. Jason, have you noticed this? With
> the non-intersecting axes this is pretty important to have out fixed.
> Also, Henryk, can you give a reproducible example so we can track down
> what a best fix might be? Thanks.
>
> - kcrisman
>
> On Nov 8
This must be a matplotlib issue. Jason, have you noticed this? With
the non-intersecting axes this is pretty important to have out fixed.
Also, Henryk, can you give a reproducible example so we can track down
what a best fix might be? Thanks.
- kcrisman
On Nov 8, 3:02 pm, Henryk Trappmann wro
