Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Location of Cross-Compiled Kernel Tree
Date: Tue, 20 Mar 2007 16:34:43 +0100	[thread overview]
Message-ID: <20070320153443.GA22863@aon.at> (raw)
In-Reply-To: <61c0054e0703200754j7c355f6dqa0831f9458e68e78@mail.gmail.com>

On Tue, Mar 20, 2007 at 09:54:57AM -0500, Paul Kavan wrote:
>Hello all:
>
>Sorry if this seems like a basic question. I am trying to port a usb
>wifi driver to the AT91SAM9260 and for the make file I need to specify
>the kernel directory. For that I need the top level of the
>cross-compiled kernel tree that buildroot makes. I am using a very
>recent version of buildroot....literally days old. Does anyone know
>what directory that is exactly?

depends..

echo *build_*/linux-*

and pick the correct one (there may only be one).

      reply	other threads:[~2007-03-20 15:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-20 14:54 [Buildroot] Location of Cross-Compiled Kernel Tree Paul Kavan
2007-03-20 15:34 ` Bernhard Fischer [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=20070320153443.GA22863@aon.at \
    --to=rep.dot.nop@gmail.com \
    --cc=buildroot@busybox.net \
    /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