Re: [sage-devel] Re: OSX Yosemite
William Stein wrote: This pattern has happened with literally every single OS X release: So true! Searching sage lists for '_scproxy' reveals that the failure to build the _scproxy module happened before on new releases of OS X. See the search results for sage-release [0] and sage-devel [1], with especially thread [2], where Volker [3] suggested a workaround: The following workaround should help to get around Apple's broken headers: CFLAGS=-DOS_OBJECT_USE_OBJC=0 export CFLAGS make Maybe this workaround could also help in the present situation? In the meanwhile, I sent a problem report to Apple via the 'Feedback assistant'. [0] https://groups.google.com/forum/#!searchin/sage-release/_scproxy [1] https://groups.google.com/forum/#!searchin/sage-devel/_scproxy [2] https://groups.google.com/d/topic/sage-devel/9B1GyPe6MAM/discussion [3] https://groups.google.com/d/msg/sage-devel/9B1GyPe6MAM/lQTo4ZrbjlAJ -- 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 sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: OSX Yosemite
If you look in the header the problem this time is precisely that the offending line is not guarded by #if OS_OBJECT_USE_OBJC On Tuesday, October 21, 2014 7:50:56 AM UTC+1, Samuel Lelievre wrote: William Stein wrote: This pattern has happened with literally every single OS X release: So true! Searching sage lists for '_scproxy' reveals that the failure to build the _scproxy module happened before on new releases of OS X. See the search results for sage-release [0] and sage-devel [1], with especially thread [2], where Volker [3] suggested a workaround: The following workaround should help to get around Apple's broken headers: CFLAGS=-DOS_OBJECT_USE_OBJC=0 export CFLAGS make Maybe this workaround could also help in the present situation? In the meanwhile, I sent a problem report to Apple via the 'Feedback assistant'. [0] https://groups.google.com/forum/#!searchin/sage-release/_scproxy [1] https://groups.google.com/forum/#!searchin/sage-devel/_scproxy [2] https://groups.google.com/d/topic/sage-devel/9B1GyPe6MAM/discussion [3] https://groups.google.com/d/msg/sage-devel/9B1GyPe6MAM/lQTo4ZrbjlAJ -- 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 sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: OSX Yosemite
On Mon, Oct 20, 2014 at 10:05 AM, Samuel Lelievre samuel.lelie...@gmail.com wrote: Hi all, I am using OS X 10.10 Yosemite. I was beta-testing it since July, and failing to build Sage. (Strangely I never thought about using the OSX-10.9 version. I just tried and it works! Thanks Stefan for asking the question, and Volker for answering it works!) idle rambling... This pattern has happened with literally every single OS X release: - Sage builds on version A - Version A+1 is coming soon and Sage doesn't build on it, but binaries built for A *mostly* work. Watch out, since usually the mostly work, but there will be some misc failures. Do run doctests to see how bad the situation is. - Version A+1 gets released. Somebody -- e.g., Craig Citro a few years ago, and most recently Andrew Ohana -- makes a *truly heroic effort* to get Sage to fully build on version A+1. It's never easy. I remember being completely stumped after a day of trying before Craig Citro finally got one of the ports to work. With Andrew Ohana's porting, I got him a MBP retina laptop in exchange for porting Sage to run on 10.9 :-). Maybe you're the hero this time :-) /idle rambling... About building Sage on Yosemite, here is my experience. - While beta-testing Yosemite, I tried to build Sage 6.3. My report on sage-release [1] has links to a few log files. - Incidentally I asked on sage-devel [2] about the Sage project getting developer previews of future versions of OS X. - Having understood that the bug was with gcc, I then installed homebrew, and used it to install gcc 4.9.1, hoping this would help building Sage, but that failed at a further step, which I reported on sage-release [3] where Volker helped to point the failure to a specific header: That header is Objective-C, which should never have been included when compiling C sources. Most likely an OSX bug. You can send them a bug report if you like talking at walls... - I don't mind talking at walls and I wanted to report to Apple with some details, but I thought I should first make sure this was not a homebrew thing, so I emailed the homebrew list [4] and someone answered [5] suggesting an experiment (not done). - I have now installed the finalized version of Yosemite, and I still have Apple's Feedback Assistant from beta-testing. (Plus, Apple tells me I will get betas of the next releases.) So I would love to send feedback to Apple about this issue, but I'm unsure how to formulate the issue, could someone help here? One option would be to point to this thread, but maybe a concise description of the issue would have more chances of being dealt with? [1] Discussion on sage-release after Sage 6.3 was released (Aug 2014). https://groups.google.com/d/msg/sage-release/Ilt8TZdy3H8/YxXy6mDyFEsJ [2] Post on sage-devel asking if the Sage project has or could have an Apple developer account, so as to test developer previews of future releases of OS X. https://groups.google.com/d/topic/sage-devel/-sm2ejzcjY8/discussion [3] Discussion on sage-release after Sage 6.4.beta3 was released (Sep 2014). https://groups.google.com/d/msg/sage-release/d7wrbZBZvrI/QtUT295ycVMJ [4] My question on the homebrew mailing list: http://librelist.com/browser//homebrew/2014/10/11/homebrew-bug-or-osx-bug/#4f32863d45a19e4f340e1f1efd08e897 [5] An answer to my question on the homebrew mailing list http://librelist.com/browser//homebrew/2014/10/11/homebrew-bug-or-osx-bug/#d2586d0f8ca2f240ee3eb51498a9fbcf More related links for reference. [6] Sage trac #17169: Upgrade to GCC 4.9.1 http://trac.sagemath.org/ticket/17169 [7] Sage trac #17174: Python _scproxy build fails on Yosemite http://trac.sagemath.org/ticket/17174 [8] Sage trac: non-closed tickets with keyword Yosemite http://trac.sagemath.org/query?status=!closedkeywords=~yosemite -- 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 sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout. -- William Stein Professor of Mathematics University of Washington http://wstein.org -- 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 sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: OSX Yosemite
idle rambling... This pattern has happened with literally every single OS X release: Agreed, this is really annoying, and +A to the person who is the hero each time! -- 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 sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: OSX Yosemite
Oh that's fun. I usually get that message when xvcc cannot find its own
libraries
in stage 1. Something that is usually solved by setting LD_LIBRARY_PATH (or here
its mac equivalent) or using static libraries for gmp/mpfr/mpc. But this is new,
someone hasn't been thinking forward about new version of OS X.
So the link of the next email is very relevant indeed.
François
On 18/10/2014, at 6:00, Volker Braun vbraun.n...@gmail.com wrote:
Relevant bit from config.log:
xgcc (GCC) 4.7.3
Copyright (C) 2012 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
configure:3355: $? = 0
configure:3344:
/Users/vbraun/Sage/local/var/tmp/sage/build/gcc-4.7.3.p1/gcc-build/./gcc/xgcc
-B/Users/vbraun/Sage/local/var/tmp/sage/build/gcc-4.7.3.p1/gcc-build/./gcc/
-B/Users/vbraun/Sage/local/x86_64-apple-darwin14.0.0/bin/
-B/Users/vbraun/Sage/local/x86_64-apple-darwin14.0.0/lib/ -isystem
/Users/vbraun/Sage/local/x86_64-apple-darwin14.0.0/include -isystem
/Users/vbraun/Sage/local/x86_64-apple-darwin14.0.0/sys-include-v 5
Reading specs from
/Users/vbraun/Sage/local/var/tmp/sage/build/gcc-4.7.3.p1/gcc-build/./gcc/specs
COLLECT_GCC=/Users/vbraun/Sage/local/var/tmp/sage/build/gcc-4.7.3.p1/gcc-build/./gcc/xgcc
COLLECT_LTO_WRAPPER=/Users/vbraun/Sage/local/var/tmp/sage/build/gcc-4.7.3.p1/gcc-build/./gcc/lto-wrapper
Target: x86_64-apple-darwin14.0.0
Configured with: ../src/configure --prefix=/Users/vbraun/Sage/local
--with-local-prefix=/Users/vbraun/Sage/local
--with-gmp=/Users/vbraun/Sage/local --with-mpfr=/Users/vbraun/Sage/local
--with-mpc=/Users/vbraun/Sage/local --with-system-zlib --disable-multilib
--disable-nls
Thread model: posix
gcc version 4.7.3 (GCC)
configure:3355: $? = 0
configure:3344:
/Users/vbraun/Sage/local/var/tmp/sage/build/gcc-4.7.3.p1/gcc-build/./gcc/xgcc
-B/Users/vbraun/Sage/local/var/tmp/sage/build/gcc-4.7.3.p1/gcc-build/./gcc/
-B/Users/vbraun/Sage/local/x86_64-apple-darwin14.0.0/bin/
-B/Users/vbraun/Sage/local/x86_64-apple-darwin14.0.0/lib/ -isystem
/Users/vbraun/Sage/local/x86_64-apple-darwin14.0.0/include -isystem
/Users/vbraun/Sage/local/x86_64-apple-darwin14.0.0/sys-include-V 5
xgcc: error: unrecognized command line option '-V'
xgcc: fatal error: no input files
compilation terminated.
configure:3355: $? = 1
configure:3344:
/Users/vbraun/Sage/local/var/tmp/sage/build/gcc-4.7.3.p1/gcc-build/./gcc/xgcc
-B/Users/vbraun/Sage/local/var/tmp/sage/build/gcc-4.7.3.p1/gcc-build/./gcc/
-B/Users/vbraun/Sage/local/x86_64-apple-darwin14.0.0/bin/
-B/Users/vbraun/Sage/local/x86_64-apple-darwin14.0.0/lib/ -isystem
/Users/vbraun/Sage/local/x86_64-apple-darwin14.0.0/include -isystem
/Users/vbraun/Sage/local/x86_64-apple-darwin14.0.0/sys-include-qversion
5
xgcc: error: unrecognized command line option '-qversion'
xgcc: fatal error: no input files
compilation terminated.
configure:3355: $? = 1
configure:3371:
/Users/vbraun/Sage/local/var/tmp/sage/build/gcc-4.7.3.p1/gcc-build/./gcc/xgcc
-B/Users/vbraun/Sage/local/var/tmp/sage/build/gcc-4.7.3.p1/gcc-build/./gcc/
-B/Users/vbraun/Sage/local/x86_64-apple-darwin14.0.0/bin/
-B/Users/vbraun/Sage/local/x86_64-apple-darwin14.0.0/lib/ -isystem
/Users/vbraun/Sage/local/x86_64-apple-darwin14.0.0/include -isystem
/Users/vbraun/Sage/local/x86_64-apple-darwin14.0.0/sys-include-o conftest
-g -O2 conftest.c 5
conftest.c:1:0: error: unknown value '10.10' of -mmacosx-version-min
configure:3374: $? = 1
configure:3562: checking for suffix of object files
configure:3584:
/Users/vbraun/Sage/local/var/tmp/sage/build/gcc-4.7.3.p1/gcc-build/./gcc/xgcc
-B/Users/vbraun/Sage/local/var/tmp/sage/build/gcc-4.7.3.p1/gcc-build/./gcc/
-B/Users/vbraun/Sage/local/x86_64-apple-darwin14.0.0/bin/
-B/Users/vbraun/Sage/local/x86_64-apple-darwin14.0.0/lib/ -isystem
/Users/vbraun/Sage/local/x86_64-apple-darwin14.0.0/include -isystem
/Users/vbraun/Sage/local/x86_64-apple-darwin14.0.0/sys-include-c -g -O2
conftest.c 5
conftest.c:1:0: error: unknown value '10.10' of -mmacosx-version-min
configure:3588: $? = 1
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME GNU C Runtime Library
| #define PACKAGE_TARNAME libgcc
| #define PACKAGE_VERSION 1.0
| #define PACKAGE_STRING GNU C Runtime Library 1.0
| #define PACKAGE_BUGREPORT
| #define PACKAGE_URL http://www.gnu.org/software/libgcc/;
| /* end confdefs.h. */
|
| int
| main ()
| {
|
| ;
| return 0;
| }
configure:3602: error: in
`/Users/vbraun/Sage/local/var/tmp/sage/build/gcc-4.7.3.p1/gcc-build/x86_64-apple-darwin14.0.0/libgcc':
configure:3605: error: cannot compute suffix of object files: cannot compile
See `config.log' for more details.
--
You received this message because you are subscribed to the Google Groups
sage-devel group.
To unsubscribe from this group
