From: Erik de Castro Lopo <erik@bcode.com>
To: video4linux-list@redhat.com
Subject: Re: Compling drivers from v4l-dvb hg tree
Date: Sat, 25 Apr 2009 08:29:06 +1000 [thread overview]
Message-ID: <20090425082906.a1a3b872.erik@bcode.com> (raw)
In-Reply-To: <412bdbff0904241522s4466fe3dh3fadd3b21113e60@mail.gmail.com>
On Fri, 24 Apr 2009 18:22:40 -0400
Devin Heitmueller <devin.heitmueller@gmail.com> wrote:
> Yeah, that's a bit harder. I did it a couple of months ago for ARM.
> I had to change the path to ensure the path to the cross-compiler's
> version of strip was ahead of the base operating system's version.
Well both my compile machine and my target are running x86 Ubuntu.
The only really relevant difference is that they have different
kernels, 2.6.26 on the compile machine and 2.6.29 on the target.
I've looked at the top level Makefile but there doesn't seem to be
a way os specifying compiling against another kernel.
Erik
--
=======================
erik de castro lopo
senior design engineer
bCODE
level 2, 2a glen street
milsons point
sydney nsw 2061
australia
tel +61 (0)2 9954 4411
fax +61 (0)2 9954 4422
www.bcode.com
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
next prev parent reply other threads:[~2009-04-24 22:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-24 7:03 Compling drivers from v4l-dvb hg tree Erik de Castro Lopo
2009-04-24 13:25 ` Devin Heitmueller
2009-04-24 22:03 ` Erik de Castro Lopo
2009-04-24 22:09 ` Devin Heitmueller
2009-04-24 22:16 ` Erik de Castro Lopo
2009-04-24 22:22 ` Devin Heitmueller
2009-04-24 22:29 ` Erik de Castro Lopo [this message]
2009-04-24 22:33 ` Devin Heitmueller
2009-04-24 22:39 ` Erik de Castro Lopo
2009-04-25 17:35 ` Trent Piepho
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=20090425082906.a1a3b872.erik@bcode.com \
--to=erik@bcode.com \
--cc=video4linux-list@redhat.com \
/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