linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Ira Weiny <iweiny@acm.org>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: PPC cross-compiling 1394 libraries
Date: Fri, 30 Nov 2001 17:31:05 -0800	[thread overview]
Message-ID: <20011130173105.21a0ec2b.iweiny@acm.org> (raw)
In-Reply-To: <3C082FD5.D1F6C997@carts.com>


On Fri, 30 Nov 2001 17:18:13 -0800
Kevin Fry <kevin@carts.com> wrote:

>
> I need to compile some 1394 libraries for my embedded 8260 board running
> HHL 2.0. These
> are the libraw1394 libraries needed for Firewire.  They have a
> ./configure script
> and everything, but if I tell the script --target=powerpc-linux I get
> 100's of
> make errors.  I'm using the HHL2.0 cross compiler, maybe that needs
> something
> extra to be done?
>
> Any advice on cross compiling libraries would be very appreciated?
>

Whenever I have cross compiled something I have always just edited the
makefiles by hand.  If you are using a std Linux box then all the data types
should be ok and configure will pick things up just fine.

I don't remember but I think I compiled libraw at some point.  What are the
errors you are getting?  Now that I think about it you may want to make sure
you have it pointing to the kernel source you will be using on the walnut.
This is one area you must make sure things are the same.

Ira Weiny
iweiny@acm.org


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

      reply	other threads:[~2001-12-01  1:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-01  1:18 PPC cross-compiling 1394 libraries Kevin Fry
2001-12-01  1:31 ` Ira Weiny [this message]

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=20011130173105.21a0ec2b.iweiny@acm.org \
    --to=iweiny@acm.org \
    --cc=linuxppc-embedded@lists.linuxppc.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).