You received this message because you are subscribed to a topic in the Google Groups "sage-support" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sage-support/GCasfFMwOOI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to sage-support...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sage-support/CAAWYfq0cWt22NZzKAqCZ5epN58vNVPUD3N%2B8F8bfEnHexdKVrA%40mail.gmail.com.
On Fri, Sep 4, 2020 at 12:55 PM Szabolcs Horvát <szho...@gmail.com> wrote:
> Thanks for the response. I do have boost installed in /opt/local/include, through MacPorts, but I remove MacPorts from the PATH before building Sage (otherwise Sage complains). Therefore, I assumed that this boost installation would not be detected. It appears that it might be sometimes detected and sometimes not? The contents of config.log are a bit unclear to me. I copy the relevant part below. Do you have any suggestion for what I might try, based on this?
various Sage packages have many ways to detect external software, and it's not uncommon to see loops over
/usr/include, /usr/local/include/, /opt/include, /opt/local/include in their configuration scripts.
Perhaps you are hit by one of these issues.
Or perhaps you left an environment variable set, pointing at /opt/local/include, e.g. CFLAGS or CXXFLAGS or CPPFLAGS...
At least it would explain why your log says
> configure:13392: g++ -std=gnu++11 -c -g -O2 -I/opt/local/include conftest.cpp >&5
which contains -I/opt/local/include
As a workaround, please rename your /opt/localwhile building Sage.
make distclean
./configure --with-system-boost_cropped=no
make
>> > To unsubscribe from this group and stop receiving emails from it, send an email to sage-s...@googlegroups.com.
>> > To view this discussion on the web visit https://groups.google.com/d/msgid/sage-support/53272397-0628-49ac-91d2-eeccb93fedb2n%40googlegroups.com.
>>
>> --
>> You received this message because you are subscribed to a topic in the Google Groups "sage-support" group.
>> To unsubscribe from this topic, visit https://groups.google.com/d/topic/sage-support/GCasfFMwOOI/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to sage-s...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-support/CAAWYfq0cWt22NZzKAqCZ5epN58vNVPUD3N%2B8F8bfEnHexdKVrA%40mail.gmail.com.
>
> --
> You received this message because you are subscribed to the Google Groups "sage-support" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-s...@googlegroups.com.
On Fri, Sep 4, 2020 at 4:31 PM John H Palmieri <jhpalm...@gmail.com> wrote:
>
>
>
> On Friday, September 4, 2020 at 7:14:24 AM UTC-7, Dima Pasechnik wrote:
>>
>>
>>
>> On Fri, Sep 4, 2020 at 12:55 PM Szabolcs Horvát <szho...@gmail.com> wrote:
>>
>> > Thanks for the response. I do have boost installed in /opt/local/include, through MacPorts, but I remove MacPorts from the PATH before building Sage (otherwise Sage complains). Therefore, I assumed that this boost installation would not be detected. It appears that it might be sometimes detected and sometimes not? The contents of config.log are a bit unclear to me. I copy the relevant part below. Do you have any suggestion for what I might try, based on this?
>>
>>
>> various Sage packages have many ways to detect external software, and it's not uncommon to see loops over
>> /usr/include, /usr/local/include/, /opt/include, /opt/local/include in their configuration scripts.
>> Perhaps you are hit by one of these issues.
>> Or perhaps you left an environment variable set, pointing at /opt/local/include, e.g. CFLAGS or CXXFLAGS or CPPFLAGS...
>> At least it would explain why your log says
>>
>> > configure:13392: g++ -std=gnu++11 -c -g -O2 -I/opt/local/include conftest.cpp >&5
>>
>> which contains -I/opt/local/include
>>
>> As a workaround, please rename your /opt/local
>> while building Sage.
>
>
> Or if you think that the system boost being broken is the only problem, you could do
>
> make distclean
> ./configure --with-system-boost_cropped=no
> make
>
>
> to force Sage to build its own boost.
Sage does build its own boost here - the problem is that a broken
(from Sage's point of view) systemwide
install of boost interferes with the build of brial.
> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-support/702943b4-a995-4569-aec2-37affe72d488o%40googlegroups.com.
On Friday, September 4, 2020 at 9:23:30 AM UTC-7, Dima Pasechnik wrote:On Fri, Sep 4, 2020 at 4:31 PM John H Palmieri <jhpalm...@gmail.com> wrote:
>
>
>
> On Friday, September 4, 2020 at 7:14:24 AM UTC-7, Dima Pasechnik wrote:
>>
>>
>>
>> On Fri, Sep 4, 2020 at 12:55 PM Szabolcs Horvát <szho...@gmail.com> wrote:
>>
>> > Thanks for the response. I do have boost installed in /opt/local/include, through MacPorts, but I remove MacPorts from the PATH before building Sage (otherwise Sage complains). Therefore, I assumed that this boost installation would not be detected. It appears that it might be sometimes detected and sometimes not? The contents of config.log are a bit unclear to me. I copy the relevant part below. Do you have any suggestion for what I might try, based on this?
>>
>>
>> various Sage packages have many ways to detect external software, and it's not uncommon to see loops over
>> /usr/include, /usr/local/include/, /opt/include, /opt/local/include in their configuration scripts.
>> Perhaps you are hit by one of these issues.
>> Or perhaps you left an environment variable set, pointing at /opt/local/include, e.g. CFLAGS or CXXFLAGS or CPPFLAGS...
>> At least it would explain why your log says
>>
>> > configure:13392: g++ -std=gnu++11 -c -g -O2 -I/opt/local/include conftest.cpp >&5
>>
>> which contains -I/opt/local/include
>>
>> As a workaround, please rename your /opt/local
>> while building Sage.
>
>
> Or if you think that the system boost being broken is the only problem, you could do
>
> make distclean
> ./configure --with-system-boost_cropped=no
> make
>
>
> to force Sage to build its own boost.
Sage does build its own boost here - the problem is that a broken
(from Sage's point of view) systemwide
install of boost interferes with the build of brial.Sage was using the system installation of the standard package "boost_cropped" ("configure:13558: will use system package and not install SPKG boost_cropped").
To unsubscribe from this group and stop receiving emails from it, send an email to sage-support...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sage-support/41ee60f8-e211-4bb0-88db-4483ec9e960co%40googlegroups.com.