Is your build script doing a recursive chmod go+x by any chance? I don't 
understand how you could end up with these permissions otherwise. I'm 
pretty sure they aren't in the tarball.



On Thursday, December 26, 2019 at 3:04:42 PM UTC+1, Harald Schilly wrote:
>
> I got a build failure (running in an ubuntu 18.04 docker container for 
> cocalc). This is the whole log it says to report:
>
> ~:$ cat /ext/sage/sage-dev/logs/pkgs/python3-3.7.3.p1.log
> Found local metadata for python3-3.7.3.p1
> Using cached file /ext/sage/sage-dev/upstream/Python-3.7.3.tar.xz
> python3-3.7.3.p1
> ====================================================
> Setting up build directory for python3-3.7.3.p1
> Finished extraction
> Applying patches from ../patches...
> Applying ../patches/2.6.5-FD_SETSIZE.patch
> patching file Modules/selectmodule.c
> Applying ../patches/2.7.3-dylib.patch
> patching file Lib/distutils/unixccompiler.py
> Applying ../patches/3.2.6-no-enable-new-dtags.patch
> patching file Lib/distutils/unixccompiler.py
> Hunk #1 succeeded at 249 (offset 6 lines).
> Applying ../patches/cygwin-ctypes.patch
> patching file Lib/ctypes/__init__.py
> Hunk #1 succeeded at 439 (offset 8 lines).
> Applying ../patches/cygwin-readline.patch
> patching file setup.py
> Hunk #1 succeeded at 788 (offset 69 lines).
> Hunk #2 succeeded at 1369 (offset -3 lines).
> Applying ../patches/linux_linking_issue_25229.patch
> patching file Lib/distutils/unixccompiler.py
> Hunk #1 succeeded at 243 (offset 9 lines).
> Applying ../patches/macos_no_include.patch
> patching file configure
> patching file configure.ac
> patching file pyconfig.h.in
> patching file setup.py
> Applying ../patches/permissions_issue_34245.patch
> patching file Makefile.pre.in
> Applying ../patches/trashcan.patch
> patching file Include/object.h
> patching file Lib/test/test_capi.py
> patching file Lib/test/test_ordered_dict.py
> patching file 'Misc/NEWS.d/next/Core and 
> Builtins/2019-02-13-16-47-19.bpo-35983.bNxsXv.rst'
> patching file Modules/_elementtree.c
> patching file Modules/_testcapimodule.c
> Hunk #1 succeeded at 5203 (offset -4 lines).
> Hunk #2 succeeded at 5386 (offset -4 lines).
> patching file Objects/descrobject.c
> Hunk #1 succeeded at 1023 (offset 2 lines).
> patching file Objects/dictobject.c
> patching file Objects/listobject.c
> patching file Objects/odictobject.c
> patching file Objects/setobject.c
> patching file Objects/tupleobject.c
> patching file Objects/typeobject.c
> patching file Python/hamt.c
> patching file Python/traceback.c
> ************************************************************************
> spkg-build should not be marked executable in the build/pkgs directory
> ************************************************************************
> Please email sage-devel (http://groups.google.com/group/sage-devel)
> explaining the problem and including the log file
>   /ext/sage/sage-dev/logs/pkgs/python3-3.7.3.p1.log
> Describe your computer, operating system, etc.
> ************************************************************************
>
>
>
> Investigating a little bit:
>
> ~$ ls -l ./local/var/tmp/sage/build/python3-3.7.3.p1/spkg-*
> -rwxr-xr-x 1 salvus salvus 4342 Sep  2  2018 ./local/var/tmp/sage/build/
> python3-3.7.3.p1/spkg-build
> -rwxr-xr-x 1 salvus salvus  106 Nov 10  2017 ./local/var/tmp/sage/build/
> python3-3.7.3.p1/spkg-check
> -rwxr-xr-x 1 salvus salvus 2269 Aug 18  2018 ./local/var/tmp/sage/build/
> python3-3.7.3.p1/spkg-install
>
> ~$ ls -l ./build/pkgs/python3/spkg-*
> -rwxr-xr-x 1 salvus salvus 4342 Sep  2  2018 
> ./build/pkgs/python3/spkg-build
> -rwxr-xr-x 1 salvus salvus  106 Nov 10  2017 
> ./build/pkgs/python3/spkg-check
> -rwxr-xr-x 1 salvus salvus 2269 Aug 18  2018 
> ./build/pkgs/python3/spkg-install
>
>
> ~$ dev$ umask
> 0022
>
>
>
>
>

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/3b6858a1-511f-464a-98fd-377ce6ac4048%40googlegroups.com.

Reply via email to