On 25 Aug., 15:28, kcrisman <kcris...@gmail.com> wrote:
> > > > 'make' is irrelevant here. Apparently your 'sed' -- used by the (poor)
> > > > spkg/standard/newest_version script -- is broken, as the first error
> > > > message suggests.
>
> > > > (The variables in 'deps' are then messed up with error output instead
> > > > of package names.)
>
> > > Right.
>
> > > I will check to see what is up with that.  The same computer has built
> > > Sage with no problems until this version, so I don't know exactly what
> > > is going on.
>
> > Just try
>
> > $ cd spkg/standard/
> > $ ./newest_version maxima # e.g.
>
> > If that fails, play with your 'sed', e.g. try (there)
>
> > $ ls -1rt maxima-*.spkg | tail -n 1 | sed -e 's/\.spkg//'
>
> $ sed
> is normal
>
> $ man sed
> gives an error, though - "cannot open configuration file man.conf".  I
> may not have installed this?
>
> $./newest_version maxima
> maxima-5.23.2.p0
>
> $ make # back in the correct directory
> Error determining package name using spkg/standard/newest_version
> script
>
> Something must have gotten corrupted.  Is there some file I can delete
> to start over?  There isn't even an spkg/installed directory yet...

Hmmm, take a look at (or re-extract) spkg/install (the main build
script), which sets up all package-related variables to be used in the
"Makefile" spkg/standard/deps, and then runs 'make'.

Or do you have different 'sed's in your PATH / perhaps in the current
$SAGE_ROOT/local/bin/?


If your Mercurial works, you could check what changed in / happened to
your root repo, which includes 'install', 'deps', 'newest_version'
etc.;

$ hg up

should restore the initial state of the files as released.


-leif

-- 
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/sage-devel
URL: http://www.sagemath.org

Reply via email to