From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] netatalk: bump version
Date: Thu, 25 Oct 2012 08:53:55 +0200 [thread overview]
Message-ID: <20121025085355.379e9cb3@skate> (raw)
In-Reply-To: <1349108616-5814-1-git-send-email-maxime.hadjinlian@gmail.com>
Dear Maxime Hadjinlian,
On Mon, 1 Oct 2012 18:23:36 +0200, Maxime Hadjinlian wrote:
> Netatalk goes to version 3.0.
> The startup script has changed too, there is now only one binary called
> netatalk. No more afpd, cnid, ... at startup ! They are executed by netatalk.
>
> All the config is done within /etc/afp.conf, look at :
> http://netatalk.sourceforge.net/3.0/htmldocs/upgrade.html
> for more info about the upgrade process.
> ---
> package/netatalk/S50netatalk | 32 +++++++++++---------------------
> package/netatalk/netatalk.mk | 4 ++--
> 2 files changed, 13 insertions(+), 23 deletions(-)
This update is apparently breaking the build in certain configurations:
http://autobuild.buildroot.net/results/4fada48332abc7f9bcd49a70debbc7950bc2263a/build-end.log
I see that your package as a dependency on berkeyleydb, but somehow,
the configure script fails to find it.
Can you look into it?
See
http://autobuild.buildroot.net/results/4fada48332abc7f9bcd49a70debbc7950bc2263a/
for the full configuration files.
Thanks,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-10-25 6:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-01 16:23 [Buildroot] [PATCH] netatalk: bump version Maxime Hadjinlian
2012-10-08 13:47 ` Peter Korsgaard
2012-10-25 6:53 ` Thomas Petazzoni [this message]
2012-10-25 8:57 ` Maxime Hadjinlian
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=20121025085355.379e9cb3@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox