From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] linux-2.6.21.5-003-atmel.1-avr32-updates.patch failes
Date: Wed, 1 Aug 2007 12:36:19 +0200 [thread overview]
Message-ID: <20070801103619.GF11697@aon.at> (raw)
In-Reply-To: <0707312209460.11633@somehost>
On Tue, Jul 31, 2007 at 10:19:13PM +0200, Cristian Ionescu-Idbohrn wrote:
>On Tue, 31 Jul 2007, Cristian Ionescu-Idbohrn wrote:
>
>> Preceeded by this:
>>
>> Applying linux-2.6.21.5-002-lzma-vmlinuz.01.patch using plaintext:
>> patching file arch/i386/boot/compressed/Makefile
>> patching file scripts/gen_lzma_initramfs_list.sh
>> patching file arch/i386/boot/compressed/lzma_misc.c
>> patching file scripts/Makefile.lib
>>
>> Applying linux-2.6.21.5-003-atmel.1-avr32-updates.patch using plaintext:
>> patching file MAINTAINERS
>> patching file Makefile
>> Hunk #1 FAILED at 1.
>> 1 out of 1 hunk FAILED -- saving rejects to file Makefile.rej
>>
>> On Tue, 31 Jul 2007, Cristian Ionescu-Idbohrn wrote:
>>
>> > Patch failed! Please fix linux-2.6.21.5-003-atmel.1-avr32-updates.patch!
>> > make: *** [buildroot/build_i486/linux-2.6.21.5/.patched] Error 1
>>
>> Conflicts between linux-2.6.21.5-002-lzma-vmlinuz.01.patch and
>> linux-2.6.21.5-003-atmel.1-avr32-updates.patch?
>
>Questions:
>
>Is it really necessary to apply these patches? Even though .config shows?
>
># BR2_PACKAGE_LZMA_TARGET is not set
># BR2_PACKAGE_LZMA_HOST is not set
># BR2_TARGET_ROOTFS_EXT2_LZMA is not set
I do have lzma installed on my host so i do not need to build a separate
lzma for the host. Still i want to use a vmlinux that is lzma
compressed, so the linux-2.6.21.5-002-lzma-vmlinuz.01.patch is needed
(vmlinux-lzma is a kernel-config anyway, so even if it is applied you
don't have to use it).
I don't know what that atmel patch is supposed to do. For anything but
atmel "boards" it should not be downloaded nor applied anyway.
># BR2_avr32 is not set
># BR2_TOOLCHAIN_ATMEL_AVR32 is not set
next prev parent reply other threads:[~2007-08-01 10:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-31 19:51 [Buildroot] linux-2.6.21.5-003-atmel.1-avr32-updates.patch failes Cristian Ionescu-Idbohrn
2007-07-31 19:56 ` Cristian Ionescu-Idbohrn
2007-07-31 20:19 ` Cristian Ionescu-Idbohrn
2007-08-01 6:20 ` [Buildroot] linux-2.6.21.5-003-atmel.1-avr32-updates.patchfailes Ulf Samuelsson
2007-08-01 10:36 ` Bernhard Fischer [this message]
2007-08-01 11:50 ` [Buildroot] linux-2.6.21.5-003-atmel.1-avr32-updates.patch failes Ulf Samuelsson
2007-07-31 22:52 ` Ulf Samuelsson
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=20070801103619.GF11697@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