From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] RFC Building Linux under Buildroot.
Date: Wed, 18 Apr 2007 15:39:06 +0200 [thread overview]
Message-ID: <20070418133906.GA11554@aon.at> (raw)
In-Reply-To: <01ba01c781b2$63d89a90$01c4af0a@Glamdring>
On Wed, Apr 18, 2007 at 02:07:46PM +0200, Ulf Samuelsson wrote:
>----- Original Message -----
>From: "Bernhard Fischer" <rep.dot.nop@gmail.com>
>To: "Ulf Samuelsson" <ulf@atmel.com>
>Cc: <buildroot@uclibc.org>
>Sent: Wednesday, April 18, 2007 1:40 PM
>Subject: Re: [Buildroot] RFC Building Linux under Buildroot.
>
>
>>On Wed, Apr 18, 2007 at 10:45:02AM +0200, Ulf Samuelsson wrote:
>>>I enclose the Makefile.in and Config.in I use to Build Linux.
>>>I have them in my targets/linux directory.
>>>
>>>Would like to have comments on that before I generate a real patch.
>>>Think it makes for easier reading than the patch.
>>>
>>>Basically I would like to bbe able to select the most
>>>common choices using checkboxes, but also allow full flexiubility
>>>by providing a text version as well.
>>
>>From a cursory look that seems fine.
>>Does this handle multiple patch-files ?
>>
>
>Yes, but the patchfiles are in a linux patch directory.
So, IIUC, it doesn't handle downloading multiple patchfiles yet?
$(patsubst %,$(PATCHFILE_DIR)/%,$(foo_CUSTOM_PATCHES)): same_for_http
wget ... -O $@
may work.
next prev parent reply other threads:[~2007-04-18 13:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-18 8:45 [Buildroot] RFC Building Linux under Buildroot Ulf Samuelsson
2007-04-18 11:40 ` Bernhard Fischer
2007-04-18 12:07 ` Ulf Samuelsson
2007-04-18 13:39 ` Bernhard Fischer [this message]
2007-04-18 14:42 ` 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=20070418133906.GA11554@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.