I get the same error with MAcOS Mojave and Xcode 10.0. The release notes
for Xcode 10 state that /usr/include is being relocated to
/Library/Developer//CommandLineTools/SDKs/MacOSX.sdk/usr/include/.
See the Xcode 10 release notes:
I did a make in ~/sage-8.1. When that completes I cd to src/Mac-app and
run make again.
My version of Mac OS is 10.13.2.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send
It appears that diskimage still has the tmp-sage-8.1-OSX_10.13.2_x86_64.app.dmg
file open. You can find this with "sudo lsof |fgrep tmp-sage-8.1".
Killing disk image allows the "hdiutil convert -format UDBZ -o
sage-8.1-OSX_10.13.2_x86_64.app.dmg
tmp-sage-8.1-OSX_10.13.2_x86_64.app.dmg"
I double checked and the Xcode IDE and Xcode Command Line Tools version is
9.2 ( 9C40b).
When I started the Xcode IED it wanted to install some files, after that
the script to build the man app runs further, see below. I think it fails
in trying to move the dmg.
I will look at the Makefile
I am trying to build the sage 8.1 mac-app on macOS 10.13.2 with Xcode V9.2
and Command Line Tools for Xcode V9.1. I have been able to compile sage
and run make ptests (all tests passed).
When I try to build the Mac-app in sage-8.1/src/mac-app it crashes with a
failure to build MainMenu.nib,
I upgraded to Command Line Tools for Xcode V9.1 and Sage 8.1 now compiles.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
On Sunday, November 19, 2017 at 11:27:43 AM UTC-5, M Mills wrote:
>
> Thanks.
>
> On Sunday, November 19, 2017 at 4:34:30 AM UTC-6, Dima Pasechnik wrote:
>>
>> 8.0 will not work with the current Xcode.
>> You would need 8.1.rc2 (or wait for 8.1 to be done, probably very soon).
>>
>
This is still
This is still broken ins Sage 8.1.rc2 with the same error. Should I post a
new thread?
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
What is the best way to do this? The file is extracted from the
mpir-3.0.0.tar.bz2 every time make is run.
On Wednesday, August 2, 2017 at 5:41:01 PM UTC-4, Bill Hart wrote:
>
> The only workaround I'm currently aware of is to remove the offending
> addmul_1.asm file. It is to do with our use
I tried AS_INTEGRATED_ASSEMBLER=1 make without success, I also tried adding
it to my environment and also from the debugging shell.
I also tried: export CFLAGS="-Wa,-q $CFLAGS" without success.
The make ends with:
vscanf.o scanf/.libs/vsscanf.o -L/Users/michael/sage-8.0/local/lib -m64
-O2
I found this thread on the MPIR issues list:
https://github.com/wbhart/mpir/issues/217
It appears that the MacOS assembler is old. Is there to configure the
sage build as they suggest?
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To
age
My system does not have a ~/.sage/init.sage file.
Mike
On Thursday, January 19, 2017 at 11:12:22 PM UTC-5, Michael Frey wrote:
>
> I found that when trying to access LATeX (MacTeX) calls in a Sage notebook
> via MatPlotLib or directly Sage would report that it could not find some
I found that when trying to access LATeX (MacTeX) calls in a Sage notebook
via MatPlotLib or directly Sage would report that it could not find some
TeX function. It appears that the PATH variable being used by the Sage app
is pointing to /usr/texbin, not /Library/TeX/texbin. As a workaround I
I am trying to attach a code file to a sage notebook. The call is : attach
("~/.sage/MHF_Bloch_n_Plot.sage"). The error I get is "NameError: name
'cython' is not defined". The code in the attach file is:
...
cython("""
#Parallel Cython, Numpy calls -- 3 part3
#Part 1
#Cython version for
14 matches
Mail list logo
