From: Ben Warren <bwarren@qstreams.com>
To: Keith Redfern <keith.redfern@uk.flextronics.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Problems dynamically linking busybox with ppc libs.
Date: Wed, 16 Aug 2006 10:13:21 -0400 [thread overview]
Message-ID: <1155737601.12539.34.camel@saruman.qstreams.net> (raw)
In-Reply-To: <367F3B3911959C4DA9991C00166F620C1DE208@EUDUCEX2.europe.ad.flextronics.com>
Keith,
On Wed, 2006-08-16 at 10:53 +0200, Keith Redfern wrote:
> I am trying to dynamically link busybox with the correct libraries but
> run into problems with directory paths and CC/LD flags.
>
> 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.
>
<snip>
>
> Is this the correct place to make modifications?
>
> Has anyone already figured the changes required to get this to work
> with ELDK toolchain?
>
> Any insight would be useful.
>
>
>
> ...…Keith
I have busybox 1.2 building under ELDK 4.0, and didn't mess at all with
the Make system, and am building for a ppc_6xx- target. I realize this
isn't quite your setup, but is pretty close.
As long as you have the tools listed in your PATH (in my
case /opt/tools/eldk4.0/usr/bin:/opt/tools/eldk4.0/bin), you should be
able to build fine using 'make menuconfig'. Just go to 'Busybox
Settings->Build Options' and select 'Do you want to build BusyBox with a
Cross Compiler?', in your case entering 'ppc_8xx-' or whatever the
prefix is for your CPU.
regards,
Ben
next prev parent reply other threads:[~2006-08-16 14:20 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 [this message]
2006-08-17 9:48 ` Wolfgang Denk
-- 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=1155737601.12539.34.camel@saruman.qstreams.net \
--to=bwarren@qstreams.com \
--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).