From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] netatalk : Fix BerkeleyDB library path
Date: Mon, 17 Dec 2012 23:05:28 +0100 [thread overview]
Message-ID: <50CF9728.7050806@mind.be> (raw)
In-Reply-To: <CAGduivzGSNwizLx8WbC+BN6J=dbmcDRjNyB7zc0stccS3X1BoQ@mail.gmail.com>
On 17/12/12 23:00, Maxime Hadjinlian wrote:
> On Mon, Dec 17, 2012 at 9:35 PM, Arnout Vandecappelle<arnout@mind.be> wrote:
>> On 17/12/12 00:15, Maxime Hadjinlian wrote:
[snip]
>> BDB_LIB isn't even used by configure, so I don't think does patch does
>> much :-)
> You're right, it should be BDB_LIBS at least.
But BDB_LIBS is unconditionally set by configure.
>> The problem I encounter in my build is that configure uses `ls ...` to
>> find the library, and my /bin/ls is linked against libacl.so.1. It seems
>> LD_LIBRARY_PATH is overridden because ls fails with:
>>
>> /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by /home/arnout/src/buildroot/output-ext-toolchain-x86_64/host/usr/x86_64-buildroot-linux-gnu/sysroot/usr/lib/libacl.so.1
>>
>> And indeed, configure sets:
>> eval export $shlibpath_var=$bdblibdir
>>
>> This is OK for native builds, but not for cross-builds...
> If I'm reading this correctly (and I'm not sure I am), there is one
> bug with ls if you native hosts is 32bits but also, if you look the
> value of atalk_libname, it will value lib64 and since the lib are not
> put there by BerkeleyDB, it will also fail. And so we must look for
> them in lib, right ? (That was I tried to fixed in my numerous
> attempt).
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.
Regards,
Arnout
[snip]
--
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
next prev parent reply other threads:[~2012-12-17 22:05 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 [this message]
2012-12-17 22:13 ` Maxime Hadjinlian
2012-12-17 22:18 ` Arnout Vandecappelle
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=50CF9728.7050806@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox