[sage-release] Re: What to do to build 6.3.beta3?

2014-06-07 Thread Dima Pasechnik
On 2014-06-07, Simon King simon.k...@uni-jena.de wrote:
 Hi,

 I was creating a new trac ticket, thus I got sage-6.3.beta3 as starting
 point. However, ecl does not build. I found the recommendation to
 simply do sage -f maxima and sage -f ecl. While re-building maxima
 works, re-building ecl fails with this error:

 cp: cannot stat '/home/king/Sage/git/sage/config/config.*': No such file
 or directory
 Failed to copy up-to-date FSF config.* scripts from
 $SAGE_ROOT/config directory ... exiting

 Is there anything that I can do to successfully make sage that is less
 drastic than make dist-clean?

maybe, sage -sync-build  sage -ba ?
the 1st one is quick anyway; 
provided that you have ccache installed, the 2nd might be quite quick
too



 Best regards,
 Simon




-- 
You received this message because you are subscribed to the Google Groups 
sage-release group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.


Re: [sage-release] Re: What to do to build 6.3.beta3?

2014-06-07 Thread leif

Simon King wrote:

Hi Volker,

On 2014-06-07, Volker Braun vbraun.n...@gmail.com wrote:

--=_Part_803_7697580.1402142703003
Content-Type: text/plain; charset=UTF-8

Simon: Try running ./bootstrap in SAGE_ROOT


Even when running in a Sage shell, I get an error:

  (sage-sh) king@linux-etl7:sage$ ./bootstrap
  rm -rf config configure build/Makefile-auto.in
  ./bootstrap: Zeile 29: aclocal: Kommando nicht gefunden.
  Bootstrap failed. Either install autotools or run bootstrap with
  the -d option to download the auto-generated files instead.

Trying the -d option, as advised:

  (sage-sh) king@linux-etl7:sage$ ./bootstrap -d
  rm -rf config configure build/Makefile-auto.in
  ./bootstrap: Zeile 29: aclocal: Kommando nicht gefunden.
  Bootstrap failed, downloading required files instead.

  gzip: stdin: unexpected end of file
  tar: Unerwartetes Dateiende im Archiv.
  tar: Unerwartetes Dateiende im Archiv.
  tar: Error is not recoverable: exiting now

Then I tried installing autotools, but openSuse's yast does not know
autotools. So, how to install it, should it *really* be missing (which I
doubt, since so far building sage has worked)?


You can simply

wget http://sagemath.org/packages/upstream/configure/configure-33.tar.gz

and extract the tarball in $SAGE_ROOT (or just the two [to four] missing 
files in config/), then retry 'sage -i ecl'.



-leif

--
() The ASCII Ribbon Campaign
/\   Help Cure HTML E-Mail

--
You received this message because you are subscribed to the Google Groups 
sage-release group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.


[sage-release] Re: What to do to build 6.3.beta3?

2014-06-07 Thread Simon King
Hi Leif,

On 2014-06-07, leif not.rea...@online.de wrote:
 You can simply

 wget http://sagemath.org/packages/upstream/configure/configure-33.tar.gz

 and extract the tarball in $SAGE_ROOT (or just the two [to four] missing 
 files in config/), then retry 'sage -i ecl'.

I think I have already posted that I installed autotools via yast -i
libtool, and this seems to do the trikc.

Best regards,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
sage-release group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.