This is because Python is running the following (its in python.log):
gcc -pthread -c -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall
-I. -IInclude -I./Include -f
PIC -DPy_BUILD_CORE \
-DSVNVERSION="\"`LC_ALL=C echo Unversioned directory`\"" \
-DHGVERSION="\"`LC_ALL=C hg id -i .`\"" \
-DHGTAG="\"`LC_ALL=C hg id -t .`\"" \
-DHGBRANCH="\"`LC_ALL=C hg id -b .`\"" \
-o Modules/getbuildinfo.o ./Modules/getbuildinfo.c
We used to ship hg, but not any more. And your system hg blocks for some
reason, probably looking for user input. There was a somewhat similar bug
in Maxima #15529. Somebody should open a ticket and see if its possible to
prevent the python build from calling hg.
On Friday, January 17, 2014 12:45:00 AM UTC-5, P Purkayastha wrote:
>
> On 01/16/2014 01:10 PM, Volker Braun wrote:
> > It is my pleasure to announce Sage-6.1.beta5. As usual, you can get it
> > either from our git server/github mirror as the "develop" branch, the
> > "6.1.beta5" tag, or by downloading the source tarball from
>
> It has happened to me a couple of times that the python compilation
> process remains stuck for hours and hours at the following three commands:
>
> /usr/bin/hg id -i
> /usr/bin/hg id -t
> /usr/bin/hg id -b
>
> If I kill the first one then the second one starts and stays like that.
> If I kill the second one then the third one starts. If I kill the third
> one then the rest of the build process just continues happily as if
> nothing happened.
>
> Attached screenshot shows that it is stuck at the second command. Can
> anyone fathom out a reason why this strange thing happens?
>
--
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/groups/opt_out.
