Re: x86_64 problems

On Wed, 07 Dec 2005 01:30:28 +0000, Paul F. Johnson wrote:

> Hi,
>
> I've just made the leap from being a 32 bit user to a 64 bit user. It's
> nice and warm here in FC5t1 land, but I've hit a couple of problems which
> I'm not sure how to fix.
>
> First off, the motherboard is a Gigabyte K8NS Pro and the processor is
> Sempron 3000+ (socket 764).
>
> When I first fire the machine up, the BIOS reports that it doesn't
> recognise the chip type, but it's correctly identified as an AMD. Fedora
> recognises it as AMD64/Optron chip (don't ask me why - it shouldn't
> really).
>
> I'm guessing that's a BIOS issue.

I;m pretty sure those issues are just cosmetic.

> Now, here's the problem. I'm trying to make wxDockit and am getting the
> following error
>
> checking build system type... Invalid
> configuration`x86_64-unknown-linux-gnu': machine `x86_64-unknown' not
> recognized
> configure: error: /bin/sh ./config.sub x86_64-unknown-linux-gnu failed
>
> Are the two problems related and if they are, is there any way to fix
> them? (if they're not, how do I fix the configure error)

Try running the following in the wxDockit source directory before running
configure:

libtoolize --force
aclocal --force
automake --add-missing
autoconf
autoheader

If there's an 'm4' directory somewhere in the wxDockit source tree, add
'-I path/to/m4' to the aclocal line.

No guarantees that'll help, particularly on FC5t1, which I haven't used
yet (I'm doing OK with CentOS 4.2, which is FC3-ish)

> I've read the Gigabyte manual and there is nothing in there to shed any
> light on this.

I wouldn't expect there to be. Might be worth looking on the Gigabyte
website for a new BIOS, though. Is the CPU you have listed as supported in
their CPU matrix for that board?

> Other than that, 64 bit seems quite a bit nippier.
>
> TTFN
>
> Paul

Best Regards,
Alex.
--
Alex Butcher Brainbench MVP for Internet Security: www.brainbench.com
Bristol, UK Need reliable and secure network systems?
PGP/GnuPG ID:0x271fd950 <http://www.assursys.com/>

.

Relevant Pages