From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/target: device device/mips
Date: Fri, 22 Jun 2007 19:50:05 +0200 [thread overview]
Message-ID: <20070622175005.GA2799@aon.at> (raw)
In-Reply-To: <f0528b5b0706220940l5543936cw53cee028dfdc9012@mail.gmail.com>
On Fri, Jun 22, 2007 at 06:40:02PM +0200, Julien Letessier wrote:
>Bug: This breaks building the linux kernel for other devices, which
>use zImage or bzImage.
>
>Why: LINUX26_BINLOC is always defined in target/device/mips/Makefile.in
>Therefore it its definition in target/linux26.mk is never used
right, sorry. r18896 wraps this file in a mips/mipel check.
>
>Fix: For now, remove target/device/mips/Makefile.in, which is not
>protected by a board-support menuconfig option.
should be fixed.
Thanks!
prev parent reply other threads:[~2007-06-22 17:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-22 8:47 [Buildroot] svn commit: trunk/buildroot/target: device device/mips aldot at uclibc.org
2007-06-22 16:40 ` Julien Letessier
2007-06-22 17:24 ` [Buildroot] Help Building Buildroot A M
2007-06-22 18:20 ` Bernhard Fischer
2007-06-22 19:02 ` Bernhard Fischer
2007-06-22 19:15 ` A M
2007-06-22 20:55 ` A M
2007-06-22 21:07 ` Bernhard Fischer
2007-06-22 23:01 ` A M
2007-06-22 17:50 ` 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=20070622175005.GA2799@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