Mouse's profile - activity

overview network karma followed questions activity

2021-03-26 16:10:10 +0200	received badge	● Popular Question (source)
2020-12-22 13:57:46 +0200	commented answer	How to make Sage use OpenSSL installed in /opt/local/{bin, lib,include} Those lists seem to require joining the group...?
2020-12-22 04:17:46 +0200	commented answer	How to make Sage use OpenSSL installed in /opt/local/{bin, lib,include} What version of Sage are you building? Latest stable, 9.2. What version of pplpy is giving trouble? Whatever's coming with that Sage version. The report says pplpy-0.8.4. Do you have Apple's command-line tools only or the full Xcode with its command-line tools? Xcode with it's command-line tools, and CLT installed separately. Both v12.3. `CC=clang` and `CXX=clang++` is already set - that's my env default. can you locate where the bug lies that makes it use clang instead of clang++? I wish. :-( I have log files that might be useful for somebody who understands Sage and pplpy, bot don't know where to send them.
2020-12-21 16:58:00 +0200	commented answer	How to make Sage use OpenSSL installed in /opt/local/{bin, lib,include} Great reply, thank you! Unfortunately, I do not run Homebrew, for convenience and security reasons. On the other hand, the difference between finding Homebrew- and Macports-installed packages should be only in where to look for them. Thus, "re-targeting" to Macports (or enabling Macports in addition to Homebrew) should be just the matter of adding more locations to the search functions that look for stuff. Trying `sage -f python3` - it figures that Macports is installed, and asks to make it "invisible" for the build to proceed?! Then, building `pplpy`, the stupid thing tries to compile `.cpp` files with `clang` instead of `clang++`, and then complains about C flags that aren't valid for C++.
2020-12-21 15:44:06 +0200	received badge	● Supporter (source)
2020-12-21 05:40:20 +0200	received badge	● Student (source)
2020-12-21 03:04:33 +0200	asked a question	How to make Sage use OpenSSL installed in /opt/local/{bin, lib,include} MacOS Catalina 10.15.7. Seemingly no way to get Sage binary to recognize installed OpenSSL (I'm not taking about the screwed-up version of LibreSSL that MacOS is coming with now). I have Python3{7,8,9} installed in /opt/local via Macports. OpenSSL-1.1.1i installed the same way (/opt/local). Everything works fine. How do I get Sage to use the packages already installed, instead of, e.g., downloading its own copy of Python? Barring that, what do I need to download to build Sage.app from sources, so it can link with a normal OpenSSL, and maybe use a normal Python?
2020-12-21 02:59:29 +0200	commented question	How get openssl with python 3 for macOS Sage 9.2? Why cannot Sage (e.g., on MacOS) use Macports-installed Python (I have Python37, Python38, Python39 installed, not counting Python27), and Macports-installed OpenSSL 1.1.1i? What do I need to do to force Sage to use apps and packages already installed on my box?