Yeah, I suspect it is something to do with the way all this happens pre-configure. I'm sure we are nearly at the bottom of it now.
Bill. 2009/4/16 Jeff Gilchrist <[email protected]>: > > On Thu, Apr 16, 2009 at 9:41 AM, Bill Hart <[email protected]> > wrote: > >> Looks to not be using gcc. It's using the Pathscale compiler and >> apparently it is a 32 bit assembler or maybe even an assembler for a >> non-x86 machine. >> >> Now the question is, why? > > gcc uses gcc on the system > cc uses pathscale, so is config.guess using cc instead of gcc? > > This is strange because on my other Xeon system which is detecting > core2 properly it is setup the same way, gcc = gcc and cc = pathcc > > And the strange PATH entries Jason noticed are also present on the > Xeon system that is working properly. > > Jeff. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "mpir-devel" group. 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/mpir-devel?hl=en -~----------~----~----~----~------~----~------~--~---
