All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] transmission 1.74 fails to build
Date: Sat, 17 Apr 2010 02:35:12 +0200	[thread overview]
Message-ID: <20100417023512.460d215c@surf> (raw)
In-Reply-To: <p2je7c6a05e1004160937mfce6921bu36df256e24c019b5@mail.gmail.com>

Hello Marek,

Thanks for working on this package!

On Fri, 16 Apr 2010 18:37:21 +0200
Belisko Marek <marek.belisko@gmail.com> wrote:

> --- /dev/null
> +++ b/package/transmission/Config.in
> @@ -0,0 +1,23 @@
> +config BR2_PACKAGE_TRANSMISSION
> +	bool "transmission"
> +	select BR2_PACKAGE_ZLIB
> +	select BR2_PACKAGE_OPENSSL
> +	select BR2_PACKAGE_LIBCURL
> +	select BR2_PACKAGE_LIBEVENT
> +	default n

default n is not needed, this is the default.

> diff --git a/package/transmission/settings.json.template
> b/package/transmission/settings.json.template

What is this ? Why isn't it part of the Transmission package itself ?

> diff --git a/package/transmission/transmission-init
> b/package/transmission/transmission-init

It should probably be named Sxxtransmission, just like all the other
init scripts.

> diff --git a/package/transmission/transmission.mk
> b/package/transmission/transmission.mk

Since transmission is using the autotools as its build system, you must
use the autotools infrastructure for the .mk file. See
http://buildroot.org/downloads/buildroot.html#autotools-tutorial for
details.

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

      reply	other threads:[~2010-04-17  0:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-16  7:14 [Buildroot] transmission 1.74 fails to build Belisko Marek
2010-04-16 14:42 ` Thomas Petazzoni
2010-04-16 16:37   ` Belisko Marek
2010-04-17  0:35     ` 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=20100417023512.460d215c@surf \
    --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.