On Dec 10, 2007 6:35 PM, David Joyner <[EMAIL PROTECTED]> wrote:
>
> On Dec 10, 2007 9:25 PM, William Stein <[EMAIL PROTECTED]> wrote:
> >
> > On Dec 10, 2007 5:44 PM, David Joyner <[EMAIL PROTECTED]> wrote:
> > >
> > > Hi:
> > > It seems like I saw this reported already but can't find it now.
> > > I'm thinking I'm doing something stupid, but can't figure it out
> > > and was wondering if someone on this list can see the problem.
> > >
> > > My usual procedure for creating a patch is as follows:
> > >
> > > 1. Take a file I want to edit, say linear_code.py in sage/coding,
> > > copy it to a directory sagestuff, say.
> > > 2. Create a clone, say codes1.
> > > 3. Edit the file, modifying/adding the functions I want.
> > > 4. Copy the file sagestuff/linear_code.py to
> > > sage/coding/linear_code.py, over-writing the existing file.
> > > 5. Rebuild the clone sage -br
> > > 6. Test the file sage -t sagestuff/linear_code.py
> > > 7. If there are errors, go to step 3. Other wise,
> > > create a patch using hg_sage.commit() and
> > > hg_sage.bundle('mybundle')
> > >
> > > This process is no longer working for me. Now, it seems I have
> > > to type sage -sh before step 6.
> >
> > What happens if you don't?
>
>
> It does not read the changes I made. For example, if I added a
> function 'chinen_polynomial'
> and add examples in the docstring for that function, all the examples
> will fail with
> AttributeError: 'LinearCode' object has no attribute 'chinen_polynomial'.
>
>
> >
> > > Then I have to type
> > > export EDITOR=vi (export EDITOR=emacs seems not to work)
> > > before step 7.
> >
> > What happens if you dont type export EDITOR=vi?
>
>
> sage: hg_sage.commit()
> cd "/home/wdj/wdj/sagefiles/sage-2.8.13.alpha1/devel/sage" && hg diff | less
> cd "/home/wdj/wdj/sagefiles/sage-2.8.13.alpha1/devel/sage" && hg commit
> emacs: symbol lookup error: /usr/lib/libcairo.so.2: undefined symbol:
> FT_Library_SetLcdFilter
> transaction abort!
> rollback completed
> abort: edit failed: emacs exited with status 127
>
This is a library conflict. I know how to fix it, by unsetting some
environment
variables before calling emacs. This is trac #975:
http://trac.sagemath.org/sage_trac/ticket/975
For now, if you put this in your SAGE_ROOT/local/bin/ it will be a work-around:
(1) Make a file SAGE_ROOT/local/bin/emacs
(2) Put this in it:
#!/bin/sh
unset LD_LIBRARY_PATH
unset DYLD_LIBRARY_PATH
/usr/bin/emacs $@
(3) make it executable:
chmod +x SAGE_ROOT/local/bin/emacs
William
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-support@googlegroups.com
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://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/
-~----------~----~----~----~------~----~------~--~---
