linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: "Keith Redfern" <keith.redfern@uk.flextronics.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Problems dynamically linking busybox with ppc libs.
Date: Thu, 17 Aug 2006 11:48:12 +0200	[thread overview]
Message-ID: <20060817094812.EAC42353A31@atlas.denx.de> (raw)
In-Reply-To: Your message of "Wed, 16 Aug 2006 10:53:04 +0200." <367F3B3911959C4DA9991C00166F620C1DE208@EUDUCEX2.europe.ad.flextronics.com>

In message <367F3B3911959C4DA9991C00166F620C1DE208@EUDUCEX2.europe.ad.flextronics.com> you wrote:
> 
> I am trying to dynamically link busybox with the correct libraries but> 
> run into problems with directory paths and CC/LD flags.

Maybe you do too much?

> I am using the toolchain supplied with ELDK and my target board is
> ppc_8xx based. The busybox version that I am using is 1.1.3.

> I see the following in Rules.mak and have been trying different variable> 
> options but with no success.

You are not supposed to meddle with Rules.mk. Also, this is not
necessary at all.

> Is this the correct place to make modifications?

No. No modifications are necessary.

Just run a standard configuration  and  make  sure  to  select  cross
compilation with "ppc_8xx-" as Cross Compiler prefix, i. e.:

-> cd /tmp
-> wget http://busybox.net/downloads/busybox-1.1.3.tar.bz2
-> tar jxf busybox-1.1.3.tar.bz2
-> cd busybox-1.1.3
-> export CROSS_COMPILE=ppc_8xx-
-> make config
...
*
* Build Options
*
...
Do you want to build BusyBox with a Cross Compiler?
(USING_CROSS_COMPILER) [N/y/?] (NEW) y
  Cross Compiler prefix (CROSS_COMPILER_PREFIX) [/usr/i386-linux-uclibc/bin/i386-uclibc-] (NEW) ppc_8xx-
Any extra CFLAGS options for the compiler? (EXTRA_CFLAGS_OPTIONS) [] (NEW)
...
-> make
...
  LINK busybox_unstripped
  STRIP busybox
...

This is so straightforward that I wonder what you moight have done to
run into problems...


> Has anyone already figured the changes required to get this to work with
> ELDK toolchain?

Yes. And if had bothered to check how the busybox RPM was build which
comes included with the ELDK (for example by  looking  at  it's  spec
file), then you should have known, too.

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Our business is run on trust.  We trust you will pay in advance.

  parent reply	other threads:[~2006-08-17  9:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-16  8:53 Problems dynamically linking busybox with ppc libs Keith Redfern
2006-08-16 14:13 ` Ben Warren
2006-08-17  9:48 ` Wolfgang Denk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-08-17 11:29 Keith Redfern

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060817094812.EAC42353A31@atlas.denx.de \
    --to=wd@denx.de \
    --cc=keith.redfern@uk.flextronics.com \
    --cc=linuxppc-embedded@ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).