cross compilation issue

Leisner, Martin Martin.Leisner at
Wed Oct 17 05:34:52 EST 2007


I disagree vehemently with "modifying" you session to suit the platform.
This becomes a problem when cross-platforms > 1.  When I "set the PATH and
environment variables" I have the same problem -- I go to a different 
platform, type make and get bad results.   

Why is modifying the makefile a "bad thing?"  hardhat did it, and afterwards
the cross-compile/arch becomes painless and transparent.  Building ways to 
construct software with fewer chances of human error is IMHO a "good thing".

I tend to lock down my source tree, and have a link tree for each platform.
So I'm not changing my build parameters, hard coding these things in the makefile
becomes a "set and forget" operation.

I agree with "problems" running from command lines...I often link in 
special tools into ~/bin so I can find them (instead of modifying my path).
But I can go weeks without having to run a tool from the command line, make's I run daily.

Having to "source" a script is another thing you can "forget" to do.
I often "forget" to run my 'make-line' script, and when I quickly hit <cntl>-C I don't
have problems (but sometimes I do).


To cross developers,  its VERY handy to build a copy of binutils which support multiple 
architectures -- so the
only thing which is really platform dependent is my host nm/objcopy/objdump/ld
supports all the platforms I'm working on...

-----Original Message-----
From: Wolfgang Denk [mailto:wd at]
Sent: Tue 10/16/2007 3:07 PM
To: Leisner, Martin
Cc: ravi.rao at; avenkatesh at; at; linuxppc-embedded at
Subject: Re: cross compilation issue
Dear Martin,

in message <556445368AFA1C438794ABDA8901891C0750DDF0 at> you wrote:
> #! /bin/bash
> exec make ARCH=powerpc CROSS_COMPILE=/opt/denx/eldk4.1/usr/bin/ppc_74xx- INSTALL_MOD_PATH=${PWD}/root $*

Note that this is *NOT* a suppoted value for CROSS_COMPILE. Please set
your PATH to include the /opt/denx/eldk4.1/usr/bin directory, and set

> I know hardhat linux had a strategy to make . files hiding the names of ARCH/CROSS_COMPILE -- so typing make
> would work once configured...
> IMHO it should be hardcoded in the Makefile after configuration -- it causes a lot of grief if you FORGET
> to specify one of these and just type "make".

I disagree. Such an approach will hit you as soon as you run a command
not from "make", but from the command line.

Instead, please set and export thse variables in your shell
environment, where each tool can pick it up.

If you have to switch environments frequently you can use some  shell
functions  to  do  so. For example, ELDK 4.1 which you use comes with
the  "eldk_init"  script   ("/opt/denx/eldk4.1/eldk_init"   in   your
installation) which can be "sourced" from the shell like this:

	$ source /opt/denx/eldk4.1/eldk_init 74xx
	PATH=/opt/denx/eldk4.1/usr/bin:/opt/denx/eldk4.1/bin: ...

ELDK 4.2 will use a much cleverer script "eldk-switch" which allows
to select versions and board like this:

	-> eldk-switch -r4.1 sequoia
	[ sequoia is using PPC440EPx ]
	Setup for ppc_4xxFP (using ELDK 4.1)
	-> eldk-switch -r4.2 TQM8540
	[ TQM8540 is using MPC8540 ]
	Setup for ppc_85xx (using ELDK 4.2)
	-> eldk-switch -r4.0 MPC860
	Setup for ppc_8xx (using ELDK 4.0)
	-> eldk-switch MPC7448
	Setup for ppc_74xx (using ELDK 4.2)

> One of the things I want to do is look at how the linux make system works now (I recall at times I edit the Makefile
> to hardcode these things).

Never edit the Makefile - this is always a Bad Thing (TM) to do.

Make sure to either set the ARCH and CROSS_COMPILE ariables  in  your
environment  (this  is  IMHO the more convenient way) or pass them on
the make command line.

Best regards,

Wolfgang Denk

DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at
Wenn Du ein' weise Antwort verlangst, Mußt Du vernünftig fragen.
                                                -- Goethe, Invektiven

More information about the Linuxppc-embedded mailing list