Hi Michael, Thanks for replying. I'm not sure I understand what you mean by merges as opposed to overwrites since I thought that Mercurial always merges the changesets it downloads from the main server when performing "upgrade()", and applies them to the current branch. I have several different projects I'm working on, not all of which are immediately merged back into the main Sage Development tree, so for that I thought cloning was the best thing. I'd also like to avoid building all of SAGE since it takes a long time compared to cloning (but even cloning takes about 45 minutes on my MacBook!).
I have installed a clean 2.8.14, and now it compiles properly. Thanks, -Jon =) On Nov 27, 1:51 pm, mabshoff <[EMAIL PROTECTED] dortmund.de> wrote: > On Nov 26, 11:03 pm, "Jonathan Hanke" <[EMAIL PROTECTED]> wrote: > > > Hi, > > Hello Jon, > > > > > I just cloned one of my sage 2.8.12 branches (which worked), but it failed > > to build the new branch. The old one builds fine. I have a Mac Book with > > OS 10.4, and the error message is below. I also tried a "sage -upgrade" on > > my main branch with similar results. I am afraid to rebuild anything else > > to avoid toasting another branch. Any suggestions? Thanks, > > You usually don't clone the main sage repo to do development, but you > work on it. If you upgrade to a recent version of sage it will merge > changes in the repos instead of overwriting them. I am not sure, but I > believe we started doing merges instead of overwrites with 2.8.12, but > somebody should confirm this. > > I would recommend separate installations if you work on different > projects. I do that mostly for porting purposes since many times the > first port is a "hack & slash" kind of making things compile. Once > those hacks are cleaned up in another install I merged them back into > my main repo. > > > > > -Jon > > =) > > > ------------------------------------------------------------------------------------------- > > ... > > Building sage/plot/plot3d/shapes.c because it depends on > > sage/plot/plot3d/shapes.pyx. > > cython --embed-positions --incref-local-binop > > -I/Users/jonhanke/Documents/sage- 2.8/devel/sage-290-devel -o > > sage/plot/plot3d/shapes.c sage/plot/plot3d/shapes.pyx > > running install > > running build > > running build_py > > running build_ext > > building 'sage.modules.free_module_element' extension > > gcc -fno-strict-aliasing -Wno-long-double -no-cpp-precomp -mno-fused-madd > > -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -I/Users/jonhanke/Documents/sage- > > 2.8/local//include -I/Users/jonhanke/Documents/sage-2.8/local//include/csage > > -I/Users/jonhanke/Documents/sage- 2.8/devel//sage/sage/ext > > -I/Users/jonhanke/Documents/sage-2.8/local/include/python2.5 -c > > sage/modules/free_module_element.c -o > > build/temp.macosx-10.3-i386-2.5/sage/modules/free_module_element.o > > -w > > gcc -bundle -undefined dynamic_lookup build/temp.macosx- > > 10.3-i386-2.5/sage/modules/free_module_element.o > > -L/Users/jonhanke/Documents/sage-2.8/local//lib -lcsage -lstdc++ -lntl -o > > build/lib.macosx-10.3-i386-2.5/sage/modules/free_module_element.so > > /usr/bin/ld: can't locate file for: -lcsage > > libcsage.dylib is $SAGE_ROOT/local/lib, so you might just copy it > over to the "right place" as a temporary work-around. > > > collect2: ld returned 1 exit status > > error: command 'gcc' failed with exit status 1 > > sage: There was an error installing modified sage library code. > > Cheers, > > Michael --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~----------~----~----~----~------~----~------~--~---
