the top level config.log will tell you why ./configure did not accept
pre-installed readline.
probably you forgot to
source .homebrew...
before
./configure
(afk, so don't recall the exact file name, but it is the only one that
starts with '.' and has homebrew in)
On Thu, 17 Sep 2020, 13:24
On Thu, Sep 17, 2020 at 8:24 AM Dima Pasechnik wrote:
> try upgrading to the latest readline (8.0.4), e.g. install as much as
> possible from Homebrew,
> which has this version working.
>
>
Done
wdj@jeeves sage-9.2.beta12 % brew upgrade readline
Warning: You are using macOS 11.0.
We do not provi
try upgrading to the latest readline (8.0.4), e.g. install as much as
possible from Homebrew,
which has this version working.
On Thu, Sep 17, 2020 at 1:09 PM David Joyner wrote:
>
>
>
> On Thu, Sep 17, 2020 at 6:54 AM Dima Pasechnik wrote:
>>
>> in the log you attached the failure is in python3
in the log you attached the failure is in python3, and it's dated Aug 22
On Thu, Sep 17, 2020 at 11:12 AM David Joyner wrote:
>
> I downloaded sage 9.2.b12 then ran configure and make using newly upgraded
> Xcode 12.
> Instead of failing at python it fails at readline. The log is attached.
>
>
I also see build failures of at least some of these packages at
https://github.com/mkoeppe/sage/runs/1059961873 (using a new GH workflow
that runs Xcode 12 beta, added in https://trac.sagemath.org/ticket/30487)
I have opened https://trac.sagemath.org/ticket/30494 "Meta-ticket: Support
Xcode 12,
With a system Python and "make -k", the following packages fail:
gf2x
ecm
symmetrica
rubiks
ecl
scipy
On Tuesday, September 1, 2020 at 10:29:52 PM UTC-7 Matthias Koeppe wrote:
> These lines:
>
> configure:17396: checking build system compiler gcc
>
> etc.
> might indicate that the configure scri
These lines:
configure:17396: checking build system compiler gcc
etc.
might indicate that the configure script is confused about cross compiling
to a different architecture.
On Tuesday, September 1, 2020 at 9:59:59 PM UTC-7, John H Palmieri wrote:
>
>
>
> On Tuesday, September 1, 2020 at 9:52:
On Tuesday, September 1, 2020 at 9:52:37 PM UTC-7 Matthias Koeppe wrote:
> On Tuesday, September 1, 2020 at 8:59:14 PM UTC-7, John H Palmieri wrote:
>
>> If I do install Python 3.7, then gf2x and ecm both fail to build. The
>> gf2x log file says "configure: error: Cannot find a build system com
On Tuesday, September 1, 2020 at 8:59:14 PM UTC-7, John H Palmieri wrote:
>
> If I do install Python 3.7, then gf2x and ecm both fail to build. The gf2x
> log file says "configure: error: Cannot find a build system compiler
> ". The ecm log file says "checking if globals are prefixed by
> undersc
This fix was already merged in 3.8.4, so
after https://trac.sagemath.org/ticket/27754 we should be fine.
The PR for Python 3.7 is https://github.com/python/cpython/pull/21155, but
our Python 3.7.x is very old already.
On Tuesday, September 1, 2020 at 9:43:15 PM UTC-7, Matthias Koeppe wrote:
>
>
The issue with "posixmodule" is apparently
https://bugs.python.org/issue41100
On Tuesday, September 1, 2020 at 8:59:14 PM UTC-7, John H Palmieri wrote:
>
> If I do install Python 3.7, then gf2x and ecm both fail to build. The gf2x
> log file says "configure: error: Cannot find a build system c
If I do install Python 3.7, then gf2x and ecm both fail to build. The gf2x
log file says "configure: error: Cannot find a build system compiler
". The ecm log file says "checking if globals are prefixed by underscore...
configure: error: Test program links neither with nor without underscore."
O
I've been trying to build on Big Sur, too. I removed the
MACOSX_DEPLOYMENT_TARGET lines from sage-env, but the Python build still
fails. The log file is attached. Any suggestions (besides installing a
different system version of Python)?
John
On Saturday, August 22, 2020 at 3:44:01 PM UTC-7
On Sat, Aug 22, 2020 at 11:23 PM David Joyner wrote:
>
>
>
> On Sat, Aug 22, 2020 at 6:02 PM Dima Pasechnik wrote:
>>
>> On Sat, Aug 22, 2020 at 10:51 PM David Joyner wrote:
>> >
>> >
>> >
>> > On Sat, Aug 22, 2020 at 4:52 PM Dima Pasechnik wrote:
>> >>
>> >> On Sat, Aug 22, 2020 at 8:28 PM Dim
On Sat, Aug 22, 2020 at 6:02 PM Dima Pasechnik wrote:
> On Sat, Aug 22, 2020 at 10:51 PM David Joyner wrote:
> >
> >
> >
> > On Sat, Aug 22, 2020 at 4:52 PM Dima Pasechnik
> wrote:
> >>
> >> On Sat, Aug 22, 2020 at 8:28 PM Dima Pasechnik
> wrote:
> >> >
> >> > note: 'utimensat' has been marked
On Sat, Aug 22, 2020 at 10:51 PM David Joyner wrote:
>
>
>
> On Sat, Aug 22, 2020 at 4:52 PM Dima Pasechnik wrote:
>>
>> On Sat, Aug 22, 2020 at 8:28 PM Dima Pasechnik wrote:
>> >
>> > note: 'utimensat' has been marked as being introduced in macOS 10.13
>> > here, but the deployment target is ma
On Sat, Aug 22, 2020 at 4:52 PM Dima Pasechnik wrote:
> On Sat, Aug 22, 2020 at 8:28 PM Dima Pasechnik wrote:
> >
> > note: 'utimensat' has been marked as being introduced in macOS 10.13
> > here, but the deployment target is macOS 10.9.0
> >
> > seems to indicate that one has to properly set MA
On Sat, Aug 22, 2020 at 8:28 PM Dima Pasechnik wrote:
>
> note: 'utimensat' has been marked as being introduced in macOS 10.13
> here, but the deployment target is macOS 10.9.0
>
> seems to indicate that one has to properly set MACOS_DEPLOYMENT_TARGET
> (or a suchlike thing) to 10.13 or even bigge
note: 'utimensat' has been marked as being introduced in macOS 10.13
here, but the deployment target is macOS 10.9.0
seems to indicate that one has to properly set MACOS_DEPLOYMENT_TARGET
(or a suchlike thing) to 10.13 or even bigger.
On Sat, Aug 22, 2020 at 8:06 PM David Joyner wrote:
>
> Hi:
>
19 matches
Mail list logo
