Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] linux: why is vmlinux only available for mips?
Date: Fri, 15 Jul 2011 14:30:53 +0200	[thread overview]
Message-ID: <20110715143053.558a756a@skate> (raw)
In-Reply-To: <CAAXf6LUUFNFF+xCQJX2juonZTXh8V1HBVqDRjjSJ1VMJXUyQFg@mail.gmail.com>

Le Fri, 15 Jul 2011 08:34:34 +0200,
Thomas De Schampheleire <patrickdepinguin+buildroot@gmail.com> a ?crit :

> > The depend statement causes the vmlinux target only to be available
> > for mips processors.
> > For powerpc for example, only uImage and zImage are selectable.
> >
> > However, I'd like to have vmlinux in the output/images directory.
> > First of all because I am directly loading this on target, rather than
> > uImage or zImage.

If vmlinux is useful on powerpc platforms, then it should be added to
the list of architectures for which vmlinux is proposed.

> In fact I have more problems with this version encoding in the output
> build/linux-X directory:
> * I need to get to the vmlinux file (mentioned above)

Just need to add "|| BR2_powerpc" as you suggested.

> * I need to get to the dtc (device tree compiler) which resides in
> <linux>/scripts/dtc/dtc

This tool looks like a useful host tool built by the kernel. Maybe we
should install it in $(HOST_DIR)/usr/bin ?

> * I need to be able to compile external kernel modules, so in that
> Makefile I need to point to the right kernel directory.

Ok. Those could be integrated as Buildroot packages, in which case
getting access to the Linux source directory is easy.

> If you stick with one kernel version, then you can hardcode it in the
> relevant scripts and Makefiles. However, when switching to another
> version, you have to update all of these files.
> One approach to solve all of this would be to create a symbolic link
> output/build/linux, pointing to the output/build/linux-X directory
> corresponding to the actually configured version.

I think I'd prefer something like :

$ make <pkg>-show-srcdir

which would be implemented at the package infrastructure, and which
would return the source directory of a particular package. This way,
you can easily ask where a given package source code has been extracted
by Buildroot.

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  parent reply	other threads:[~2011-07-15 12:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-15  6:20 [Buildroot] linux: why is vmlinux only available for mips? Thomas De Schampheleire
2011-07-15  6:34 ` Thomas De Schampheleire
2011-07-15  9:22   ` Yann E. MORIN
2011-07-15  9:34     ` Thomas De Schampheleire
2011-07-15  9:38       ` Peter Korsgaard
2011-07-15 11:53         ` Thomas De Schampheleire
2011-07-15  9:46       ` Daniele Salvatore Albano
2011-07-15 11:55         ` Thomas De Schampheleire
2011-07-15 12:30   ` Thomas Petazzoni [this message]
2011-07-15 13:10     ` Yann E. MORIN
2011-07-20 13:38     ` Thomas De Schampheleire
2011-07-20 16:10       ` Quotient Remainder
2011-07-20 19:23         ` Thomas Petazzoni
2011-07-24 11:36         ` Thomas De Schampheleire
2011-07-26 10:38           ` Thomas De Schampheleire
2011-07-20 16:17       ` Thomas Petazzoni
2011-07-24 11:46         ` Thomas De Schampheleire
2011-07-25  7:05           ` Thomas Petazzoni
2011-07-25  8:34             ` Thomas De Schampheleire

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=20110715143053.558a756a@skate \
    --to=thomas.petazzoni@free-electrons.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