On Sunday 15 March 2009 04:55:39 Gonzalo Tornaria wrote:
> As I mentioned, in current tr...@1739, my nocona is detected as a
> "core2" by config.guess, since it does include lahf.
>
> However, I tried hacking config.guess so that my cpu returns "nocona"
> instead --- just because I wanted to benchmark it that way (and also
> would be a test of what happens when compiling in nocona w/o lahf).
> But now, the configure step fails.

shouldn't need to hack config.guess ,if everything working as it should :) 
then a
./configure --build=your_guess-unknown-linux-gnu
should do it
where the -unknown-linux-gnu is the last part of what config.guess returns


>
> The variables are:
>
> using ABI="64"
>       CC="gcc -std=gnu99"
>       CFLAGS="-O2 -m64 -march=nocona -mtune=nocona"
>       CPPFLAGS=""
>       MPN_PATH=" x86_64/core2 x86_64 generic"
>
> (so, it seems to be using core2 code, after all...)
>
> The first errors that show up in configure output are:
>
> checking for struct pst_processor.psp_iticksperclktick... no
> =yes: command not found: HAVE_NATIVE_%3
> =yes: command not found: HAVE_NATIVE_%2
> =yes: command not found: HAVE_NATIVE_%3
> =yes: command not found: HAVE_NATIVE_%2
>
> And later:
>
> checking size of unsigned short... 0
> checking size of unsigned... 0
> checking size of unsigned long... 0
> checking size of mp_limb_t... 0
> configure: error: Oops, mp_limb_t doesn't seem to work
>
> Here it stops...
>
> Gonzalo
>
> On Sat, Mar 14, 2009 at 10:49 PM, Gonzalo Tornaria <torna...@gmail.com> 
wrote:
> > My nocona with lahf is now a "core2-unknown-linux-gnu". Thanks for
> > upgrading it for me... I hope it still keeps my office warm in winter
> >
> > :-)
>
> 


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"mpir-devel" group.
To post to this group, send email to mpir-devel@googlegroups.com
To unsubscribe from this group, send email to 
mpir-devel+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/mpir-devel?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to