On 25 Aug., 14:19, kcrisman <kcris...@gmail.com> wrote:
> > > Did something change in prereq in the last couple alphas?  Through
> > > 4.7.1 I really had no trouble on Cygwin other than known problems.
> > > But now I get weird things like what is below 
> > > (seehttp://sage.math.washington.edu/home/kcrisman/cygwin-1.7.9-winxp-sage...
> > > for all details).
>
> > > Usually typing "make" again keeps it going, but with this latest alpha
> > > I can't even get to the first spkg, I guess.  Note that suspicious
> > > order of words appearing each time:
>
> > > installed/Error running sed to extract package name
>
> > > I also find "installed/Error dependency dropped." amusing.  Maybe we
> > > need an Error dependency :)
>
> > > Thanks for any help - my guess is that something weird is going on
> > > with a line ending or the arguments to some command, but I don't
> > > understand how makefiles or spkg/standard/deps *really* work (I mean,
> > > I can follow the implications in deps, but don't really know what
> > > "happens" so that it follows these implications, nor in what order),
> > > so I could use the help tracking this down.
>
> > '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//'


-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