From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] netatalk : Fix BerkeleyDB library path
Date: Mon, 17 Dec 2012 23:18:11 +0100 [thread overview]
Message-ID: <50CF9A23.4090409@mind.be> (raw)
In-Reply-To: <CAGduivzm4RUMxoUWtsQshupg5Q=OFU3BYaXAOpp8CRVxghQYtA@mail.gmail.com>
On 17/12/12 23:13, Maxime Hadjinlian wrote:
> On Mon, Dec 17, 2012 at 11:05 PM, Arnout Vandecappelle<arnout@mind.be> wrote:
[snip]
>> Yes, but the configure script already does that: if it fails to find it in
>> $atalk_libname and $atalk_libname != lib then it tries again in lib.
> Okay, I see what I missed and I'm looking at your patch, I'll go to
> bed less stupid.
The only reason I'm less stupid is that I spent three hours looking at
that configure script...
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
prev parent reply other threads:[~2012-12-17 22:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1352057123-7137-2-git-send-email-maxime.hadjinlian>
2012-11-08 21:34 ` [Buildroot] [PATCH 2/2] netatalk: Make BerkeleyDB optional for Netatalk Maxime Hadjinlian
2012-12-05 9:05 ` Peter Korsgaard
2012-12-05 9:38 ` Maxime Hadjinlian
2012-12-08 15:53 ` [Buildroot] [PATCH] netatalk : Fix BerkeleyDB library path Maxime Hadjinlian
2012-12-16 10:54 ` Peter Korsgaard
2012-12-16 22:17 ` Peter Korsgaard
2012-12-16 23:15 ` Maxime Hadjinlian
2012-12-17 20:35 ` Arnout Vandecappelle
2012-12-17 22:00 ` Maxime Hadjinlian
2012-12-17 22:05 ` Arnout Vandecappelle
2012-12-17 22:13 ` Maxime Hadjinlian
2012-12-17 22:18 ` Arnout Vandecappelle [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=50CF9A23.4090409@mind.be \
--to=arnout@mind.be \
--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.