All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stefan Fröberg" <stefan.froberg@petroprogram.com>
To: buildroot@busybox.net
Subject: [Buildroot] Help needed with cross-compiling libotr
Date: Thu, 28 Feb 2013 17:04:23 +0200	[thread overview]
Message-ID: <512F71F7.20409@petroprogram.com> (raw)

Hello all

I have been trying to cross-compile libotr package that makes it possible,
with the help of pidgin-otr plugin, to send encrypted messages with
Pidgin IM software
(which I already have successfully cross-compiled for buildroot and plan
to submit soon).

Now, the problem is that no matter what I do that damn package picks
"-I/usr/include" somewhere
and the build will fail complaining about undefined reference to
__isoc99_sscanf (which it picks wrongly from
host system stdio.h).

Several remakes, autoreconf and configure switche changes and still no
closer to success.

Even grepped the source for -I/usr/include and the only place it shows
it is from
something called oldinclude from configure file...

Im totally lost here.

Could somebody more knowledgeable about autoconf/make please take a look
of this package ?
It's not big and the only dependencies it needs are libgcrypt and
libgpg-error

It can be downloaded from here:
http://www.cypherpunks.ca/otr/pidgin-otr-4.0.0.tar.gz

And here are my unworking Config.in and libotr.mk so far

config BR2_PACKAGE_LIBOTR
    bool "libotr"
    select BR2_PACKAGE_LIBGRCRYPT
    select BR2_PACKAGE_LIBGPG_ERROR
    help
      libotr

      http://www.cypherpunks.ca/otr

#############################################################
#
# libotr
#
#############################################################

LIBOTR_VERSION = 4.0.0
LIBOTR_SITE = http://www.cypherpunks.ca/otr
LIBOTR_AUTORECONF = YES
LIBOTR_AUTORECONF_OPTS = --install --force
LIBOTR_DEPENDENCIES = libgcrypt libgpg-error

LIBOTR_CONF_ENV = LIBGCRYPT_CONFIG=$(STAGING_DIR)/usr/bin/libgcrypt-config
LIBOTR_CONF_OPT += --disable-gcc-hardening --disable-linker-hardening 
--with-pic \
           --with-libgcrypt-prefix="$(STAGING_DIR)/usr" \
           --disable-dependency-tracking \
           --oldincludedir="$(STAGING_DIR)/usr/include"


# disable rpath stuff
define    LIBOTR_POST_CONFIGURE_FIXUP
    (cd $(@D); \
    sed -i
's|^hardcode_libdir_flag_spec=.*|hardcode_libdir_flag_spec=""|g' libtool ; \
    sed -i 's|^runpath_var=LD_RUN_PATH|runpath_var=DIE_RPATH_DIE|g'
libtool )
endef

LIBOTR_POST_CONFIGURE_HOOKS += LIBOTR_POST_CONFIGURE_FIXUP

$(eval $(autotools-package))



Thank you!

Regards
Stefan

             reply	other threads:[~2013-02-28 15:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-28 15:04 Stefan Fröberg [this message]
2013-02-28 15:06 ` [Buildroot] Help needed with cross-compiling libotr Stefan Fröberg
2013-02-28 15:21 ` Thomas Petazzoni
2013-02-28 15:36   ` Markos Chandras
2013-02-28 15:43     ` Jeremy Rosen
2013-02-28 15:48       ` Thomas Petazzoni
2013-02-28 16:01         ` Stefan Fröberg
2013-02-28 15:43     ` Gustavo Zacarias
2013-02-28 15:49       ` Markos Chandras
2013-02-28 15:50         ` Thomas Petazzoni
2013-02-28 15:51           ` Gustavo Zacarias
2013-02-28 15:53           ` Markos Chandras
     [not found]   ` <512F7E8D.5070200@petroprogram.com>
2013-02-28 16:04     ` Stefan Fröberg

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=512F71F7.20409@petroprogram.com \
    --to=stefan.froberg@petroprogram.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.