You don't happen to set CFLAGS or CPPFLAGS by any chance?
The problem in the failing compile command from your log is that
"-I/Users/zscherr/sage/develop/local/include" appears after
"-I/usr/local/include". It should appear before.
gcc -Wno-unused-result -Wsign-compare -Wunreachable-code
Hi Matthias,
Running ./sage -sh -c 'pkg-config --cflags singular' with home-brew's
singular installed gives:
-DSING_NDEBUG -DOM_NDEBUG -DSING_NDEBUG -DOM_NDEBUG -DSING_NDEBUG
-DOM_NDEBUG -DSING_NDEBUG -DOM_NDEBUG
-I/Users/zscherr/sage/develop/local/include/singular
my env is a mess, but I
On Wednesday, September 9, 2020 at 7:57:18 PM UTC-7, Matthias Koeppe wrote:
>
> On Wednesday, September 9, 2020 at 6:49:36 PM UTC-7, Zachary Scherr wrote:
>>
>>I tried to build the most recent beta version of sage and it would
>> appear that it's taking issue with the fact that I have
On Wednesday, September 9, 2020 at 6:49:36 PM UTC-7, Zachary Scherr wrote:
>
>I tried to build the most recent beta version of sage and it would
> appear that it's taking issue with the fact that I have singular installed
> on my Mac 10.15.6 through homebrew. Homebrew's version is singular
On Wednesday, September 9, 2020 at 2:44:00 PM UTC-7, Dima Pasechnik wrote:
>
>
> On Wed, Sep 9, 2020 at 10:40 PM John H Palmieri > wrote:
>
>> I have a Sage policy proposal:
>>
>> - For any new standard Sage package PKG, we strongly recommend, require
>> if at all possible, that the package
On Wed, Sep 9, 2020 at 10:40 PM John H Palmieri
wrote:
> I have a Sage policy proposal:
>
> - For any new standard Sage package PKG, we strongly recommend, require if
> at all possible, that the package comes with an spkg-configure.m4 script in
> build/pkgs/PKG. There should also be a directory
I have a Sage policy proposal:
- For any new standard Sage package PKG, we strongly recommend, require if
at all possible, that the package comes with an spkg-configure.m4 script in
build/pkgs/PKG. There should also be a directory build/pkgs/PKG/distros.
Neither the spkg-configure.m4 file nor
On Monday, September 7, 2020 at 2:18:34 PM UTC-7, Matthias Koeppe wrote:
>
> tox (https://tox.readthedocs.io/en/latest/) is a popular package that is
> used by a large number of Python projects as the standard entry point for
> testing and linting.
> [...]
>
I propose to make "tox" a standard
