From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] transmission: version bump to 2.8.2
Date: Thu, 2 Jan 2014 10:15:51 +0100 [thread overview]
Message-ID: <20140102101551.2a562563@skate> (raw)
In-Reply-To: <BLU0-SMTP836DDC88AF848215E0249AD9CE0@phx.gbl>
Dear Bernd Kuhls,
On Mon, 30 Dec 2013 18:41:23 +0100, Bernd Kuhls wrote:
>
> Signed-off-by: Bernd Kuhls <berndkuhls@hotmail.com>
> ---
> package/transmission/transmission.mk | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/package/transmission/transmission.mk b/package/transmission/transmission.mk
> index 1e7ee48..3ced558 100644
> --- a/package/transmission/transmission.mk
> +++ b/package/transmission/transmission.mk
> @@ -4,7 +4,7 @@
> #
> ################################################################################
>
> -TRANSMISSION_VERSION = 2.33
> +TRANSMISSION_VERSION = 2.82
> TRANSMISSION_SITE = http://download.transmissionbt.com/files/
> TRANSMISSION_SOURCE = transmission-$(TRANSMISSION_VERSION).tar.xz
> TRANSMISSION_DEPENDENCIES = \
This patch is causing lots of build issues in our autobuilders. See
http://autobuild.buildroot.org/results/638/63884de929fb7339ebf44b08cb5d1ab30010666a/build-end.log
for an example. The build error is:
tr-utp.c:66:1: error: conflicting types for 'UTP_Write'
In file included from tr-utp.c:28:0:
../third-party/libutp/utp.h:116:6: note: previous declaration of 'UTP_Write' was here
make[2]: *** [tr-utp.o] Error 1
make[2]: *** Waiting for unfinished jobs....
Can you have a look into this?
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 9:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-30 17:41 [Buildroot] [PATCH 1/1] transmission: version bump to 2.8.2 Bernd Kuhls
2013-12-31 11:03 ` Thomas Petazzoni
2014-01-02 9:15 ` 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=20140102101551.2a562563@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.