Basics -- what tools for Walnut?

I think I'm missing a basic concept here -- I'm about to do some work on
a Walnut system, so  I started by loading up the HardHat Linux that came
with the Walnut onto my intel desktop, then grabbing the
linuxppc_2_4_devel kernel via rsync.  When I try to compile, gas startes
to complain about "unknown option '-m405'".

I tried running /opt/hardhat/devkit/ppc/4xx/bin/ppc_4xx-as -m405, and
sure enough, it doesn't know the 405.  Nor does the gas that I built
from binutils 2.10.1 with --target-powerpc.

So, is there a patch I should be applying before building the
cross-compile environment, or a specific set of tools somewhere, or what
am I missing?

thanks,
dave.


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

The version of HardHat Linux that came with your walnut was created to match the
requirements of the kernel also shipped with Hard Hat Linux.

The current _devel kernel requires a newer version of binutils that understands
the -m405 architecture.  Either use the kernel shipped w/ Hard Hat Linux, or you
will need to get a newer tool chain.  (Either build it yourself or purchase it
from MontaVista...)

--Mark
(Speaking for myself, not MontaVista whom I work for.)

Dave Strout wrote:

I think I'm missing a basic concept here -- I'm about to do some work on
a Walnut system, so  I started by loading up the HardHat Linux that came
with the Walnut onto my intel desktop, then grabbing the
linuxppc_2_4_devel kernel via rsync.  When I try to compile, gas startes
to complain about "unknown option '-m405'".

I tried running /opt/hardhat/devkit/ppc/4xx/bin/ppc_4xx-as -m405, and
sure enough, it doesn't know the 405.  Nor does the gas that I built
from binutils 2.10.1 with --target-powerpc.

So, is there a patch I should be applying before building the
cross-compile environment, or a specific set of tools somewhere, or what
am I missing?

thanks,
dave.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Dave Strout wrote:

I think I'm missing a basic concept here -- I'm about to do some work on
a Walnut system, so  I started by loading up the HardHat Linux that came
with the Walnut onto my intel desktop, then grabbing the
linuxppc_2_4_devel kernel via rsync.  When I try to compile, gas startes
to complain about "unknown option '-m405'".

I tried running /opt/hardhat/devkit/ppc/4xx/bin/ppc_4xx-as -m405, and
sure enough, it doesn't know the 405.  Nor does the gas that I built
from binutils 2.10.1 with --target-powerpc.

So, is there a patch I should be applying before building the
cross-compile environment, or a specific set of tools somewhere, or what
am I missing?

I suspect that is a fairly old tool chain that you are using.
Try modifying arch/ppc/Makefile to use

  -mcpu=403

instead of

  -mcpu=405

If you subscribe to the MontaVista product, the current compiler will
work properly with linuxppc_2_4_devel.

-Frank
--
Frank Rowand [off-list ref]
MontaVista Software, Inc

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Frank Rowand wrote:

I suspect that is a fairly old tool chain that you are using.

In the past, the practice was to inform people when changes were made
that required a minimum revision of tools to operate properly.
Simply telling people "your toolchain is too old" isn't helpful.....
What version of tools is required to build this properly?  Why
doesn't the check in comment indicate this information when the
change was made?

Try modifying arch/ppc/Makefile to use

  -mcpu=403

Or, just remove it since it doesn't perform any useful function.  On
the newer tools, it's required to allow the assembler to not bitch about
4xx unique instructions, another non-useful function, IMHO.

Thanks.

	-- Dan


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

It's all good -- I didn't realize there was a newer binutils.  2.12
seems to do the trick

thanks,
dave.

Dan Malek wrote:

Frank Rowand wrote:

quoted

I suspect that is a fairly old tool chain that you are using.

In the past, the practice was to inform people when changes were made
that required a minimum revision of tools to operate properly.
Simply telling people "your toolchain is too old" isn't helpful.....
What version of tools is required to build this properly?  Why
doesn't the check in comment indicate this information when the
change was made?

quoted

Try modifying arch/ppc/Makefile to use

  -mcpu=403

Or, just remove it since it doesn't perform any useful function.  On
the newer tools, it's required to allow the assembler to not bitch about
4xx unique instructions, another non-useful function, IMHO.

Thanks.

    -- Dan

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/