On Wednesday, April 1, 2020 at 11:05:31 AM UTC-7, John H Palmieri wrote:
>
>
>
> On Tuesday, March 31, 2020 at 7:15:10 PM UTC-7, John H Palmieri wrote:
>>
>>
>>
>> On Tuesday, March 31, 2020 at 6:21:42 PM UTC-7, Matthias Köppe wrote:
>>>
>>> On Tuesday, March 31, 2020 at 8:02:48 PM UTC-4, John H Palmieri wrote:
>>>>
>>>> Here's the strange part: if I add the package libpng, then Sage doesn't 
>>>> build. With these packages, it builds and passes tests (output from "brew 
>>>> list --versions"):
>>>>
>>>> autoconf 2.69
>>>> automake 1.16.2
>>>> boost 1.72.0_1
>>>> cabextract 1.9.1
>>>> emacs-mac emacs-26.3-z-mac-7.9
>>>> gcc 9.2.0_1 9.3.0
>>>> gdbm 1.18.1
>>>> gettext 0.20.1
>>>> gmp 6.2.0 6.1.2_2
>>>> gnutls 3.6.12
>>>> icu4c 64.2
>>>> isl 0.22.1 0.21 0.18
>>>> jpeg 9d
>>>> libdvdcss 1.4.2
>>>> libevent 2.1.11_1
>>>> libffi 3.2.1
>>>> libidn2 2.3.0
>>>> libmpc 1.1.0
>>>> libtasn1 4.14 4.16.0
>>>> libtiff 4.1.0
>>>> libunistring 0.9.10
>>>> mpfr 4.0.2
>>>> nettle 3.4.1
>>>> [email protected] 1.1.1d
>>>> p11-kit 0.23.20 0.23.18.1
>>>> pkg-config 0.29.2
>>>> readline 8.0.4
>>>> sqlite 3.31.1
>>>> unbound 1.9.4 1.10.0
>>>> xz 5.2.5
>>>>
>>>
>>> python3's spkg-configure refuses to use system python if we install any 
>>> of the following from spkg:
>>>
>>> sqlite libpng bzip2 xz libffi
>>>
>>> bzip2 comes from /usr/bin
>>> The others from homebrew.
>>> When you install libpng in addition to the list of packages, the set of 
>>> prerequisites for accepting system python3 is complete, and then the 
>>> unresolved problems with the build (kiwisolver, ...) appear when system 
>>> python 3 is /usr/bin/python3 (XCode's python3).
>>>
>>> It does not happen if you have homebrew python3 in PATH. 
>>>
>>
>> Right, I realized that, too. However, I initially had even more homebrew 
>> packages installed, Sage built using the system Python, and the build 
>> succeeded. That's when I ran into the doctest failures, which I am now 
>> trying to reproduce: trying to see which homebrew packages trigger them.
>>
>>
> To summarize:
>
> - if I don't install libpng (for example), then Sage builds its own Python 
> and everything works, all tests pass.
> - if I don't install Homebrew's python but enough other packages, then the 
> OS X Python is used, and kiwisolver fails to build. Trac 29408 appears to 
> help with that; I'm trying a full build now.
>

With trac 29404 + 29408, the build succeeds with the system python, but I 
get many of the doctest failures that arise with Homebrew's python.
 

> - if I install Homebrew's python but not pkg-config, then matplotlib fails 
> to build because it can't find libpng. (The top-level configure script 
> finds it and so decides not to build it.)
> - if I also install pkg-config, the build succeeds but I get all of the 
> doctest failures I reported before. In this last case, here's what I've 
> installed — I tried to keep the list as small as possible:
>
> gcc 9.2.0_1 9.3.0
> gdbm 1.18.1
> gmp 6.2.0 6.1.2_2
> isl 0.22.1 0.21 0.18
> libmpc 1.1.0
> libpng 1.6.37
> libunistring 0.9.10
> mpfr 4.0.2
> [email protected] 1.1.1d
> pkg-config 0.29.2
> python 3.7.7
> readline 8.0.4
> sqlite 3.31.1
> xz 5.2.5 
>
> Overall, this is a precarious situation.
>
> By the way, this is with OS X 10.15.4 and the latest Xcode,
>
> % gcc --version
> Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr 
> --with-gxx-include-dir=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/c++/4.2.1
> Apple clang version 11.0.3 (clang-1103.0.32.29)
> Target: x86_64-apple-darwin19.4.0
> Thread model: posix
> InstalledDir: 
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
>
>

-- 
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/0b4cf47f-dcb1-44b0-af2d-295da9f37ed8%40googlegroups.com.

Reply via email to