This is data, not advice, it likely leads to dogs and cats living together, 
... mass hysteria.

I changed the R spkg-install to add 

CC=/usr/bin/gcc

and sage built and seems to work. 

Something strange seems to be happening with the builtin gcc and the OSX 
system frameworks.

On Wednesday, April 22, 2015 at 5:35:54 PM UTC-4, David Einstein wrote:
>
> I too am having this problem.  I recently upgraded Xcode to 6.3.1 and am 
> running OSX 10.10.3.   I have homebrew, but have removed it and all the 
> /usr/local stuff from my environment. Also I am using the sage built gcc (I 
> set SAGE_INSTALL_GCC=yes), which should (in theory) moot the homebrew issue.
>
> If I cd into the directory
>
> sage/local/var/tmp/sage/build/r-3.1.2.p0/src/src/library/grDevices
>
> and go into the sage shell, and do
>
> gcc -std=gnu99 -I../../../../include -DNDEBUG -I../../../include 
> -I../../../../src/include -DHAVE_CONFIG_H -I../../../../src/extra/zlib     
> -fPIC  -g -O2   -c devQuartz.c -o devQuartz.o
>
> I get the same result (not surprisingly, but somewhat reassuring)
>
> However, if I do
>
> /usr/bin/gcc -std=gnu99 -I../../../../include -DNDEBUG -I../../../include 
> -I../../../../src/include -DHAVE_CONFIG_H -I../../../../src/extra/zlib     
> -fPIC  -g -O2   -c devQuartz.c -o devQuartz.o
>
> (using the system compiler instead of the sage built compiler) it 
> compiles.  Unfortunately, this does not help the big picture, as I am loath 
> to compile R with a different compiler than everything else.
>
> On Thursday, April 16, 2015 at 9:35:21 PM UTC-4, Han Xiao wrote:
>>
>> I had the same problem while I was trying upgrading my Sage from 6.4.1 to 
>> 6.6. I'm using OS X 10.10.3 and I do have homebrew installed. I really hope 
>> this problem could be solved. 
>>
>> On Wednesday, April 15, 2015 at 10:46:31 PM UTC+8, Buck Evan wrote:
>>>
>>> I'm trying to build sage from source.
>>> I've installed lots of things, including gcc, but I've gotten stuck 
>>> while building R.
>>> It's erroring out in /usr/bin/cc (which it chose as the objective-c 
>>> compiler):
>>>
>>>
>>>
>>>    1. In file included from /usr/include/Availability.h:153:0, 
>>>    2. from /usr/include/stdlib.h:61, 
>>>    3. from ../../../../include/R.h:28, 
>>>    4. from qdBitmap.h:23, 
>>>    5. from qdBitmap.c:27: 
>>>    6. /System/Library/Frameworks/CoreServices.framework/Frameworks/
>>>    FSEvents.framework/Headers/FSEvents.h:486:41: error: expected ',' or 
>>>    '}' before '__attribute__' 
>>>    7. kFSEventStreamEventFlagItemIsHardlink __OSX_AVAILABLE_STARTING(
>>>    __MAC_10_10, __IPHONE_9_0) = 0x00100000, 
>>>    8. ^
>>>
>>>
>>>
>>> Full details are here:
>>> http://paste.pound-python.org/show/9mou1V2L8kJPOg3ztHcb/
>>>
>>

-- 
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Reply via email to