On Sun, Apr 6, 2008 at 11:58 PM, Samuel Gaehwiler <[EMAIL PROTECTED]> wrote:
>
> > Instead do
> > ./sage -bdist some_name
>
> its available at http://people.ee.ethz.ch/~samuelg/sage/
>
>
> > 1. How much RAM?
>
> 2 GB (2x 1GB) DDR2 SDRAM 667 MHz
>
>
>
> > 2. What happens if you type
> >
> > ./sage -maxima
>
> *** - invalid byte #xCC in CHARSET:ASCII conversion
> The following restarts are available:
> ABORT :R1 ABORT
>
> ABORT :R2 ABORT
> ABORT :R3 ABORT
> Break 1 [4]>
>
>
>
> > 3. What happens if at the Sage prompt you type !maxima
> >
> > sage: !maxima
>
> *** - invalid byte #xCC in CHARSET:ASCII conversion
> The following restarts are available:
> ABORT :R1 ABORT
>
> ABORT :R2 ABORT
> ABORT :R3 ABORT
> Break 1 [4]>
>
>
>
> > 4. Do you have fink installed on your computer?
>
> no
>
>
>
> > 5. Are you using Macports?
>
> yes, MacPorts 1.600.
> The files in my /opt/local/bin are listed in
> http://people.ee.ethz.ch/~samuelg/sage/files_by_macports_in_opt_local_bin.txt
>
>
>
> > 6. Any weird language / internationalization issues?
>
> no. I have a Swiss German keyboard layout, but all previous
> posted errors also occur when I use the U.S. keyboard setting.
>
Do you have any files anywhere in your filesystem that might not
just use standard ascii characters in their names?
Could you try making a new clean user account and running
sage -maxima
from it?
I'm guessing a bug in Maxima is causing the problem. Maxima tries
to read various directories on startup and behaves very stupidly in
the presence of filenames that contain characters that confuse it.
-- William
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/sage-support
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
