From: Bernhard Roth <broth@roth-itk.de>
To: buildroot@busybox.net
Subject: [Buildroot] Adding libev to buildroot
Date: Mon, 08 Aug 2011 15:19:16 +0200 [thread overview]
Message-ID: <4E3FE254.7030004@roth-itk.de> (raw)
In-Reply-To: <CAGm1_ktqDGmoRtbWuN8uDM3qiL00K+kS-VbyVcDV3p9sqav9Jg@mail.gmail.com>
Hello Yegor,
I did a patch according to Linus' description.
I hope this works and describes clearly the changes I did.
Just today I was recompiling a new root filesystem and libev works just
like a charm!
Keep your good work going, thank you!
Best regards,
Bernhard
On 08/08/2011 08:34 AM, Yegor Yefremov wrote:
> Hello Bernhard,
>
> you have following ways to get to the patch:
>
> 1. see kernel documentation on how to compare two src dirs:
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob_plain;f=Documentation/SubmittingPatches;hb=HEAD
> 2. using quilt: http://en.wikipedia.org/wiki/Quilt_%28software%29. It
> requires one clean src dir, your two files you sent to the list and
> changes to package/Config.in
> 3. git: clone buildroot repository, make your changes, git add, git
> commit, http://www.kernel.org/pub/software/scm/git/docs/git-format-patch.html.
> See http://progit.org/book/ for syntax and details
>
> Yegor
-------------- next part --------------
A non-text attachment was scrubbed...
Name: libev.patch
Type: text/x-patch
Size: 3325 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110808/40cdafee/attachment.bin>
next prev parent reply other threads:[~2011-08-08 13:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-07 11:10 [Buildroot] Adding libev to buildroot Bernhard Roth
2011-08-07 21:04 ` Yegor Yefremov
[not found] ` <4E3F79CF.40608@roth-itk.de>
[not found] ` <CAGm1_ktqDGmoRtbWuN8uDM3qiL00K+kS-VbyVcDV3p9sqav9Jg@mail.gmail.com>
2011-08-08 13:19 ` Bernhard Roth [this message]
2011-08-08 14:55 ` Yegor Yefremov
2011-09-10 15:13 ` Peter Korsgaard
2011-09-10 21:27 ` Yegor Yefremov
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=4E3FE254.7030004@roth-itk.de \
--to=broth@roth-itk.de \
--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.