linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "pjmaiya" <pjmaiya@signal-networks.com>
To: <bwarren@qstreams.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: CLI for embedded system
Date: Wed, 21 Feb 2007 17:18:32 +0530	[thread overview]
Message-ID: <000d01c755ae$364a7bf0$4601a8c0@signet> (raw)
In-Reply-To: 1171555658.7029.49.camel@saruman.qstreams.net

Dear Ben,
     I have tried following option, with host as ppc_8xx, since we are using
mpc860 processor and  also we are using montavista provided compiler
(ppc_8xx).
Our embedded target runs on montavista linux with mpc860 processor and
compiler given by monta vista(hard hat linux).

host$ ./configure --host=ppc_8xx --build=i686 CC=ppc_8xx-gcc

We are getting error ppc_8xx unkown host at some stage. When we further
investigated "clish" code we found that we need to add our new architecture
in aux_scripts/configure.sub file. We have successfully built that part. But
for some libarary we are getting error in /usr/lib/libbstd++, but we need to
change this path..only option left for us to change in "configure" file
which requires autoconf tool..Also we need to change some thing in
"configure.in". We are little bit stuck in this part..Can U help in this
regard.. Writing our make for clish is massive work!!!

thanx for help.
-pjmaiya

----- Original Message ----- 
From: "Ben Warren" <bwarren@qstreams.com>
To: "pjmaiya" <pjmaiya@signal-networks.com>
Cc: <linuxppc-embedded@ozlabs.org>
Sent: Thursday, February 15, 2007 9:37 PM
Subject: Re: CLI for embedded system


> On Thu, 2007-02-15 at 17:09 +0530, pjmaiya wrote:
> > hi,
> >     I have successfully complied and used 'clish' in host system (i686
> > machine)
> > But I need to port the same for PPC platform. Can anyone suggest me how
to
> > do the same.
> >
> > thanx in advace,
> > pjmaiya
> >
>
> Like many other projects, I believe this one uses autoconf (I think
> that's the term).  As a starting point, try:
>
> host$ ./configure --host=ppc-linux-gnu --build=i686 CC=
> ${CROSS_COMPILE}gcc
>
> /* Monitor the output of configure to make sure that everything looks
> kosher.  You'll probably want to add a "--prefix=" option that tells it
> where to place the end result, and there may be other options you want
> too.  Read and understand the Makefile that configure creates.  Then:
>
> host$ make
>
> I reiterate - this is only a starting point.  This may not compile
> cleanly and you will need to experiment a bit, I'm sure.  Hopefully it's
> not too bad, but these projects can sometimes be a pain to get exactly
> as you want.
>
> regards,
> Ben
>
>

  reply	other threads:[~2007-02-21 11:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-08 12:29 Target reset after linux reboot Frank Prepelica
2007-02-08 13:02 ` CLI for embedded system pjmaiya
2007-02-08 15:42   ` Ben Warren
2007-02-09 10:37     ` pjmaiya
2007-02-15 11:39       ` pjmaiya
2007-02-15 16:07         ` Ben Warren
2007-02-21 11:48           ` pjmaiya [this message]
2007-02-21 15:29             ` Ben Warren
2007-02-08 16:20   ` Grant Likely
2007-02-08 15:46 ` Target reset after linux reboot Ben Warren

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='000d01c755ae$364a7bf0$4601a8c0@signet' \
    --to=pjmaiya@signal-networks.com \
    --cc=bwarren@qstreams.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).