From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/4] transmission: Fix build error "conflicting types for 'UTP_Write'" after version bump
Date: Thu, 2 Jan 2014 22:21:29 +0100 [thread overview]
Message-ID: <20140102222129.3f5eba3d@skate> (raw)
In-Reply-To: <BLU0-SMTP287B7593393BF8A5143ED5FD9CB0@phx.gbl>
Dear Bernd Kuhls,
On Thu, 2 Jan 2014 20:28:49 +0100, Bernd Kuhls wrote:
> fix taken from http://www.adminsehow.com/2012/10/how-to-install-transmission-2-71-on-debian-6-0-squeeze/
>
> compile tested on arch sh4, fixes
> http://autobuild.buildroot.org/results/638/63884de929fb7339ebf44b08cb5d1ab30010666a/
>
> should also fix powerpc
> http://autobuild.buildroot.org/results/eb4/eb486228a11a9602d4bf40e771744d2b2b40508f/
>
> Signed-off-by: Bernd Kuhls <berndkuhls@hotmail.com>
> ---
> package/transmission/transmission-fix-utypes.patch | 22 ++++++++++++++++++++
> 1 file changed, 22 insertions(+)
> create mode 100644 package/transmission/transmission-fix-utypes.patch
>
> diff --git a/package/transmission/transmission-fix-utypes.patch b/package/transmission/transmission-fix-utypes.patch
> new file mode 100644
> index 0000000..74f3d32
> --- /dev/null
> +++ b/package/transmission/transmission-fix-utypes.patch
Thanks, but please add a description + Signed-off-by inside the patch
itself. It should also point to where you found the patch.
See
http://buildroot.org/downloads/manual/manual.html#_format_and_licensing_of_the_package_patches
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-01-02 21:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-02 19:28 [Buildroot] [PATCH 4/4] transmission: Fix build error "conflicting types for 'UTP_Write'" after version bump Bernd Kuhls
2014-01-02 19:31 ` [Buildroot] [PATCH 1/1] " Bernd Kuhls
2014-01-02 21:21 ` Thomas Petazzoni [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=20140102222129.3f5eba3d@skate \
--to=thomas.petazzoni@free-electrons.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.