Re: [sage-devel] Re: openssl gone?

Am Mittwoch, 6. April 2016 00:40:51 UTC+2 schrieb François: > > One day we'll have to version or crush those build logs instead of > appending to them incrementally. The correct section says > > configure: CHECKS for libraries > checking for SHA1_Init in -lcrypto... yes > checking for curl_glob

Re: [sage-devel] Re: openssl gone?

One day we'll have to version or crush those build logs instead of appending to them incrementally. The correct section says configure: CHECKS for libraries checking for SHA1_Init in -lcrypto... yes checking for curl_global_init in -lcurl... no checking for XML_ParserCreate in -lexpat... no check

Re: [sage-devel] Re: openssl gone?

Hum... configure: CHECKS for libraries checking for SHA1_Init in -lcrypto... no checking for SHA1_Init in -lssl... no checking for curl_global_init in -lcurl... no checking for XML_ParserCreate in -lexpat... no checking for iconv in -lc... yes Would you be able to get the config.log file (either

Re: [sage-devel] Re: openssl gone?

On 04/06/16 09:54, Simon King wrote: Am Dienstag, 5. April 2016 23:47:20 UTC+2 schrieb François: On 04/06/16 09:27, Simon King wrote: > Interesting. There really is no such thing as git-remote-http. Why could > that be? Do you have curl+curl-dev installed? That what it u

Re: [sage-devel] Re: openssl gone?

Am Dienstag, 5. April 2016 23:47:20 UTC+2 schrieb François: > > On 04/06/16 09:27, Simon King wrote: > > Interesting. There really is no such thing as git-remote-http. Why could > > that be? > > Do you have curl+curl-dev installed? That what it uses for those. > After sudo apt-get install

Re: [sage-devel] Re: openssl gone?

On 04/06/16 09:27, Simon King wrote: Interesting. There really is no such thing as git-remote-http. Why could that be? Do you have curl+curl-dev installed? That what it uses for those. Francois -- You received this message because you are subscribed to the Google Groups "sage-devel" group. T

Re: [sage-devel] Re: openssl gone?

Hi François, Am Dienstag, 5. April 2016 23:19:26 UTC+2 schrieb François: > > What do you have in local/libexec/git-core? > I suppose you talk about SAGE_LOCL/libexec/git-core, since the problems only arise with the git installation of Sage, not with my system-wide installation. It contains ne

Re: [sage-devel] Re: openssl gone?

What do you have in local/libexec/git-core? You should have something like /usr/libexec/git-core/git-remote /usr/libexec/git-core/git-remote-ext /usr/libexec/git-core/git-remote-fd /usr/libexec/git-core/git-remote-ftp /usr/libexec/git-core/git-remote-ftps /usr/libexec/git-core/git-remote-http /usr

[sage-devel] Re: openssl gone?

Am Dienstag, 5. April 2016 23:09:15 UTC+2 schrieb Simon King: > > > > Am Dienstag, 5. April 2016 22:21:50 UTC+2 schrieb Volker Braun: >> >> Those are 4 concatenated git build logs. I don't know which one is >> relevant. >> > > Since it still doesn't work, I suppose the last one is relevant. >

[sage-devel] Re: openssl gone?

Am Dienstag, 5. April 2016 22:21:50 UTC+2 schrieb Volker Braun: > > Those are 4 concatenated git build logs. I don't know which one is > relevant. > Since it still doesn't work, I suppose the last one is relevant. -- You received this message because you are subscribed to the Google Groups

[sage-devel] Re: openssl gone?

Those are 4 concatenated git build logs. I don't know which one is relevant. On Tuesday, April 5, 2016 at 8:23:53 PM UTC+2, Simon King wrote: > > Hi Volker, > > Am Dienstag, 5. April 2016 17:30:15 UTC+2 schrieb Volker Braun: >> >> Should work, whats the git build log and what does the git binary

[sage-devel] Re: how we develop sage

>From Drew: "+1. At the LMFDB workshop in Bristol last week we ended up giving a lot of people accounts on the main LMFDB machine in Warwick simply so they wouldn't have to go through the time-consuming (and somewhat error prone) process of building Sage 7.1 on their laptops and installing the add

[sage-devel] how we develop sage

Hi, This was a comment I just put on trac #965: "I would make a completely separate python package, maybe called pysmalljac, which builds smalljac and makes it usable from Python. It would be on github and pypi. That's how most Sage development should be done. What a monster I've created by fol

[sage-devel] Re: openssl gone?

Hi Volker, Am Dienstag, 5. April 2016 17:30:15 UTC+2 schrieb Volker Braun: > > Should work, whats the git build log and what does the git binary link to? > The git log is attached. I don't know how to find out what the git binary links to. - Why is it not installed with http(s) support? >> >

[sage-devel] Re: openssl gone?

Should work, whats the git build log and what does the git binary link to? On Tuesday, April 5, 2016 at 5:03:08 PM UTC+2, Simon King wrote: > > - Is the git spkg installed by default (I don't recall to have installed > it manually)? If so, why? > $ cat build/pkgs/git/type standard > - Wh

[sage-devel] Re: Git message while pushing a patch

Thank you ! I'll look that up in git's doc. -- Emmanuel Charpentier Le mardi 5 avril 2016 09:39:20 UTC+2, Volker Braun a écrit : > > Pruning is about unreachable objects (commits not referenced by a branch, > e.g. because you deleted the branch). It is safe to do unless you > accidentally dele

[sage-devel] Re: openssl gone?

Hi Volker, On 2016-04-05, Volker Braun wrote: > Fixed, the tarball had the wrong name Thank you, it worked! Unfortunately it didn't solve the problem that I wanted to get solved: When I am in a normal shell, the command git clone https://github.com/momtx/meataxe.git works. But in a Sage shel

[sage-devel] Re: openssl gone?

Fixed, the tarball had the wrong name On Tuesday, April 5, 2016 at 4:35:07 PM UTC+2, Simon King wrote: > > Hi! > > I just tried to install openssl. "sage -i openssl" did not work, as it > couldn't download openssl-1.0.2g.tar.gz from any mirror. What went wrong > here? > > Best regards, > Si

[sage-devel] openssl gone?

Hi! I just tried to install openssl. "sage -i openssl" did not work, as it couldn't download openssl-1.0.2g.tar.gz from any mirror. What went wrong here? Best regards, Simon -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from thi

Re: [sage-devel] Re: Sage 7.1 Windows 8.1 Cygwin make error

On 5 April 2016 at 10:59, Dima Pasechnik wrote: > > MSYS2 has a mingw toolchain and a Cygwin toolchain. > > http://stackoverflow.com/questions/25019057/how-are-msys-msys2-and-msysgit-related-to-each-other > I did not know that msys2 also had a cygwin toolchain. But then, I don't want to touch cy

Re: [sage-devel] Re: Sage 7.1 Windows 8.1 Cygwin make error

No, start-up fails with a related(?) seg fault. Am Dienstag, 5. April 2016 11:50:01 UTC+2 schrieb Dima Pasechnik: > > Does Sage start for you? > > On Tuesday, April 5, 2016 at 10:39:24 AM UTC+1, > alexander.s...@googlemail.com wrote: >> >> My home directory is in C:\cygwin64. Permission were mixe

Re: [sage-devel] Re: Sage 7.1 Windows 8.1 Cygwin make error

Does Sage start for you? On Tuesday, April 5, 2016 at 10:39:24 AM UTC+1, alexander.s...@googlemail.com wrote: > > My home directory is in C:\cygwin64. Permission were mixed up, but after > restoring them the error persists. > Although sage is no longer complaining about DOT_SAGE permissions. >

Re: [sage-devel] Re: Sage 7.1 Windows 8.1 Cygwin make error

My home directory is in C:\cygwin64. Permission were mixed up, but after restoring them the error persists. Although sage is no longer complaining about DOT_SAGE permissions. Am Dienstag, 5. April 2016 10:32:06 UTC+2 schrieb Dima Pasechnik: > > > > On Tuesday, April 5, 2016 at 7:56:01 AM UTC+1,

Re: [sage-devel] Re: Sage 7.1 Windows 8.1 Cygwin make error

On Tuesday, April 5, 2016 at 9:38:24 AM UTC+1, bluescarni wrote: > > On 29 March 2016 at 20:41, Dima Pasechnik > > wrote: > >> (this is perhaps not quite the same as the "proper" cygwin patch - MSYS2 >> is a fork of Cygwin, >> which is sort of more developer-friendly --- perhaps we should cons

Re: [sage-devel] Re: Sage 7.1 Windows 8.1 Cygwin make error

On 29 March 2016 at 20:41, Dima Pasechnik wrote: > (this is perhaps not quite the same as the "proper" cygwin patch - MSYS2 > is a fork of Cygwin, > which is sort of more developer-friendly --- perhaps we should consider > switching to it) > As far as I know MSYS2 is not a fork of cygwin, it is

Re: [sage-devel] Re: Sage 7.1 Windows 8.1 Cygwin make error

On Tuesday, April 5, 2016 at 7:56:01 AM UTC+1, alexander.s...@googlemail.com wrote: > > I faced the same error, which appears to be caused by gcc-5.3.0. After > downgrading to gcc-4.9.3, brial compiled successfully. > I am now stuck with a segmentation fault related to doc-html. > It seems to c

Re: [sage-devel] Request to extend the binomial function by the reflection formula

Overall, I think the proposed change makes sense in the long run, and Peter presents a good case. But there are some dangers. Foremost, Clemens argues that a change will potentially brake user code: while this is true, I think it should be overruled for the long benefits, if another behaviour is m

[sage-devel] Re: Git message while pushing a patch

Pruning is about unreachable objects (commits not referenced by a branch, e.g. because you deleted the branch). It is safe to do unless you accidentally deleted a branch and want it back ;-) A better command to clean up temporary files is "git gc" which includes pruning On Tuesday, April 5,

[sage-devel] Git message while pushing a patch

Pushing to Trac#20190 , I got : charpent@asus16-ec:/usr/local/sage-exp$ git trac push Pushing to Trac #20190... Guessed remote branch: u/charpent/upgrade_r_to_3_2_4 remote: Trac #20190: Commit changed to feb037. Auto packing the repository for optim