On Nov 23, 2007, at 18:04 , William Stein wrote:

>
> On Nov 23, 2007 3:58 PM, Justin C. Walker <[EMAIL PROTECTED]> wrote:
>>> Hello folks,
>>>
>>> Sage 2.8.13 has been released. Sources are and binaries should  
>>> soon be
>>> available at
>>>
>>>               http://sagemath.org/download.html
>>
>> I did a full build of 2.8.13 on two systems:
>>
>> Mac OS X/10.4.11: Dual Quad-Core Xeon
>> Mac OS X/10.5.1:  Core Duo
>>
>> Problems on both:
>> 10.5.1: blow-up in Flint
>>    ld: duplicate symbol ___gmpz_abs in test-support.o and fmpz_poly-
>> test.o
>>
>> 10.4.11: blow-up in cddlib ("/usr/local" contamination)
>>    /usr/libexec/gcc/i686-apple-darwin8/4.0.1/ld: Undefined symbols:
>>    ___gmpq_init
>>    ...
>
> This is all really weird since I fully tested building Sage-2.8.13 on
> OSX 10.4 intel and OSX 10.5 intel (both core duo and Xeon),
> and didn't have any problems at all.   So the problem could
> be with
>   (1) 10.5.1 versus 10.5 -- unlikely, since this wouldn't
> even touch the compilers (but I'll try upgrading right now and
> see if I can replicate the problem there),
>  (2) Us having different versions of Xcode: I'm using
>    gcc version 4.0.1 (Apple Inc. build 5465)
> on my machines, or

Same Xcode/gcc versions.  I don't think it's 10.5.1 vs. 10.5; more  
than likely something in the way I have my system set up (or perhaps  
in your setup :-}).  My 10.5 install is pretty much plain vanilla.  I  
have Xcode 2.5 and 3.0 installed, but my gcc version matches yours.

>  (3) you having something funny in your /usr/local/.

> Also maybe you have all kinds
> of stuff in /usr/local?  Could you try temporarily renaming it,
> redoing the build, just to see if that's the problem?

I reported this during one of the "alpha/rc" cycles (2.8.10.alpha?, I  
think), and tried the "move /usr/local out of the way" trick.  That  
let the build complete, and 'sage' seemed to work (modulo some "make  
test" glitches I may be forgetting).

> Something I've wondered about for a while -- is there a bulletproof
> way to ignore /usr/local/ during build of Sage?

I think 'gcc' has flags that let you force the lookup paths for  
"system-supplied" includes and libs.  I'll see if I can track that down.

Justin

--
Justin C. Walker, Curmudgeon-at-Large
() The ASCII Ribbon Campaign
/\ Help Cure HTML Email




--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~----------~----~----~----~------~----~------~--~---

Reply via email to