> > [Or didn't get the tarball fully extracted, such that some spkgs are
> > missing, perhaps due to insufficient disk space left?]
>
> Hmm, THAT is a possibility, I suppose... although those spkgs were
> still there, since newest_version appeared to work...
No, there are at least 65 GB free on th
>
> > But newest_version seems to be working fine.
>
> Apparently not for all packages / package base names. Which fail?
Sorry, I think I didn't make it clear that I tested newest_version on
some of the spkgs that it had failed for earlier (observed by looking
at install.log and where the env var
On 25 Aug., 18:13, kcrisman wrote:
> On Aug 25, 11:43 am, kcrisman wrote:
> > > > 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
> > > > 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
On Aug 25, 11:43 am, kcrisman wrote:
> > > 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 packa
> > 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
> "Makefi
On 25 Aug., 15:28, kcrisman 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
>
> > > '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.
>
> >
On 25 Aug., 14:19, kcrisman 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
> > 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).
>
On 25 Aug., 11:20, leif wrote:
> On 25 Aug., 04:17, kcrisman 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.
On 25 Aug., 04:17, kcrisman 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.
12 matches
Mail list logo
