Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lionel Landwerlin <llandwerlin@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 13/14] target: added BR2_KARCH option
Date: Mon, 08 Feb 2010 00:55:55 +0100	[thread overview]
Message-ID: <1265586955.18332.1.camel@coalu.atr> (raw)
In-Reply-To: <20100207184636.GE5229@mx.loc>

Le dimanche 07 f?vrier 2010 ? 19:46 +0100, Bernhard Reutner-Fischer a
?crit :
> On Sun, Feb 07, 2010 at 07:07:55PM +0100, llandwerlin at gmail.com wrote:
> >From: Lionel Landwerlin <llandwerlin@gmail.com>
> >
> >For packages building kernel modules (ie linux-fusion), it is required
> >to give the ARCH=some_arch argument to make so the kernel's makefile
> >are aware of the target architecture. We didn't had the value to fill
> >the ARCH variable. BR2_KARCH variable is computed using the BR2_ARCH
> >variable.
> 
> There is/was KERNEL_ARCH in there since ages.

Thx for pointed this, and let's forget this patch...

linux-fusion bump patch updated.

-- 
Lionel Landwerlin

  parent reply	other threads:[~2010-02-07 23:55 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-07 18:07 [Buildroot] [PATCH 00/14] Pull-request: Bumps & new packages llandwerlin at gmail.com
2010-02-07 18:07 ` [Buildroot] [PATCH 01/14] package: added PKG_CONF_ENV variables to host packages llandwerlin at gmail.com
2010-02-09 11:31   ` Thomas Petazzoni
2010-02-07 18:07 ` [Buildroot] [PATCH 02/14] package: added pre-configure hooks llandwerlin at gmail.com
2010-02-09 11:32   ` Thomas Petazzoni
2010-02-07 18:07 ` [Buildroot] [PATCH 03/14] directfb: bump to 1.4.3 llandwerlin at gmail.com
2010-02-08 13:47   ` Paulius Zaleckas
2010-02-07 18:07 ` [Buildroot] [PATCH 04/14] package: added lirc llandwerlin at gmail.com
2010-02-09 11:37   ` Thomas Petazzoni
2010-02-09 11:54     ` Lionel Landwerlin
2010-02-09 12:37       ` Thomas Petazzoni
2010-02-09 12:53         ` Lionel Landwerlin
2010-02-07 18:07 ` [Buildroot] [PATCH 05/14] directfb: added support for lirc llandwerlin at gmail.com
2010-02-09 12:38   ` Thomas Petazzoni
2010-02-07 18:07 ` [Buildroot] [PATCH 06/14] pixman: bump to 0.16.4 llandwerlin at gmail.com
2010-02-07 18:07 ` [Buildroot] [PATCH 07/14] cairo: Bump to 1.8.8 llandwerlin at gmail.com
2010-02-07 18:07 ` [Buildroot] [PATCH 08/14] systat: bump to 9.0.6 llandwerlin at gmail.com
2010-02-07 18:07 ` [Buildroot] [PATCH 09/14] automake: bump to 1.11 llandwerlin at gmail.com
2010-02-07 18:07 ` [Buildroot] [PATCH 10/14] libtool: added LIBTOOLIZE variable to point on $(HOST_DIR)/usr/bin/libtoolize llandwerlin at gmail.com
2010-02-07 18:07 ` [Buildroot] [PATCH 11/14] target: Added ttyAS[0-3] devices llandwerlin at gmail.com
2010-02-07 18:07 ` [Buildroot] [PATCH 12/14] openssh: added empty login option llandwerlin at gmail.com
2010-02-07 18:07 ` [Buildroot] [PATCH 13/14] target: added BR2_KARCH option llandwerlin at gmail.com
2010-02-07 18:46   ` Bernhard Reutner-Fischer
2010-02-07 21:18     ` Lionel Landwerlin
2010-02-07 23:52     ` [Buildroot] [PATCH] linux-fusion: bump to 8.1.1 llandwerlin at gmail.com
2010-02-07 23:55     ` Lionel Landwerlin [this message]
2010-02-07 18:07 ` [Buildroot] [PATCH 14/14] " llandwerlin at gmail.com
2010-02-07 23:53   ` [Buildroot] [PATCH] " llandwerlin at gmail.com

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=1265586955.18332.1.camel@coalu.atr \
    --to=llandwerlin@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