Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] heimdal: explicitly set -lpthread
Date: Tue, 21 Apr 2015 09:35:09 +0200	[thread overview]
Message-ID: <20150421093509.0cdd1240@free-electrons.com> (raw)
In-Reply-To: <1429581853-24749-1-git-send-email-bluemrp9@gmail.com>

Dear Ryan Coe,

On Mon, 20 Apr 2015 19:04:13 -0700, Ryan Coe wrote:
> fixes the following build error:
> 
> output/build/host-heimdal-1.5.3/lib/sqlite/.libs/libheimsqlite.a(sqlite3.o): In function `pthreadMutexTry':
> sqlite3.c:(.text+0x5795): undefined reference to `pthread_mutex_trylock'
> output/build/host-heimdal-1.5.3/lib/sqlite/.libs/libheimsqlite.a(sqlite3.o): In function `pthreadMutexAlloc':
> sqlite3.c:(.text+0xbf84): undefined reference to `pthread_mutexattr_init'
> sqlite3.c:(.text+0xbf91): undefined reference to `pthread_mutexattr_settype'
> sqlite3.c:(.text+0xbfa4): undefined reference to `pthread_mutexattr_destroy'
> output/build/host-heimdal-1.5.3/base/.libs/libheimbase.a(heimbase.o): In function `init_ar_tls':
> heimbase.c:(.text+0x4f): undefined reference to `pthread_key_create'
> output/build/host-heimdal-1.5.3/base/.libs/libheimbase.a(heimbase.o): In function `autorel_tls':
> heimbase.c:(.text+0x263): undefined reference to `pthread_getspecific'
> heimbase.c:(.text+0x291): undefined reference to `pthread_setspecific'
> collect2: error: ld returned 1 exit status
> make[3]: *** [verify_krb5_conf] Error 1
> make[3]: Leaving directory `output/build/host-heimdal-1.5.3/lib/krb5'
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory `output/build/host-heimdal-1.5.3/lib'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `output/build/host-heimdal-1.5.3'
> make: *** [output/build/host-heimdal-1.5.3/.stamp_built] Error 2
> 
> Signed-off-by: Ryan Coe <bluemrp9@gmail.com>

Ok, now I understand better. It's because host-heimdal picks up
host-sqlite, which we most likely don't need. Can you try instead
something like this:

diff --git a/package/heimdal/heimdal.mk b/package/heimdal/heimdal.mk
index 972f15c..5d27f77 100644
--- a/package/heimdal/heimdal.mk
+++ b/package/heimdal/heimdal.mk
@@ -9,7 +9,19 @@ HEIMDAL_SITE = http://www.h5l.org/dist/src
 HEIMDAL_DEPENDENCIES = host-e2fsprogs host-pkgconf
 HEIMDAL_INSTALL_STAGING = YES
 # static because of -fPIC issues with e2fsprogs on x86_64 host
-HOST_HEIMDAL_CONF_OPTS = --with-x=no --disable-shared --enable-static
+HOST_HEIMDAL_CONF_OPTS = \
+       --disable-shared \
+       --enable-static \
+       --without-openldap \
+       --without-capng \
+       --without-sqlite3 \
+       --without-libintl \
+       --without-openssl \
+       --without-berkeley-db \
+       --without-readline \
+       --without-libedit \
+       --without-hesiod \
+       --without-x
 HOST_HEIMDAL_CONF_ENV = MAKEINFO=true
 HEIMDAL_MAKE = $(MAKE1)
 # For heimdal-0004-compile_et.patch

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-04-21  7:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-21  2:04 [Buildroot] [PATCH v2] heimdal: explicitly set -lpthread Ryan Coe
2015-04-21  7:35 ` Thomas Petazzoni [this message]
2015-04-22  4:32   ` Ryan Coe
2015-04-22  7:39     ` Thomas Petazzoni

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=20150421093509.0cdd1240@free-electrons.com \
    --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