Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] package/dropwatch: Try to fix autobuild error
Date: Thu, 30 Apr 2015 22:54:29 +0200	[thread overview]
Message-ID: <55429685.6030003@embedded.rocks> (raw)

Hi,

I need some help to fix autobuild error for dropwatch:
http://autobuild.buildroot.net/results/70f/70f019329fa5af6b573bc3ddd6c0bcdcb5ca8bec/

I fixed the musl build error by including a local queue.h header file 
from OpenBSD. This compiles fine, but leads to a linker error:

/home/joerg/Development/git/buildroot/output/host/usr/arm-buildroot-linux-musleabi/sysroot/usr/lib/libbfd.so: 
undefined reference to `libintl_dgettext'

I know that musl supports the gettext API natively. libintl.h is the 
header for the gettext API. There is no need for libintl. So why does 
libbfd.so does not link against libc? Any idea?

Best regards
J?rg Krause
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150430/a30713e7/attachment.html>

                 reply	other threads:[~2015-04-30 20:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=55429685.6030003@embedded.rocks \
    --to=joerg.krause@embedded.rocks \
    --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