All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arthur LAMBERT <lambertarthur22@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] issue to build elfutils due to libintl
Date: Sun, 10 Mar 2019 16:14:26 +0100	[thread overview]
Message-ID: <20190310151426.GA11489@arthur-bzh> (raw)
In-Reply-To: <20190308234947.274e5d36@gmx.net>

Thanks to you I was able to know that the libintl include was comming from the uclibc.
The header was partially missing in my output directory. After checking my uclibc
defconfig, I get it.
In fact I have one custom modification on my buildroot. My uclibc defconfig does not have :
UCLIBC_HAS_LIBINTL=y

But I cannot explain why the compilation is working on my arch linux and was working before the
upgrading in my ubuntu.

This is not a real bug right ? Its more like a mistake in my uclibc defconfig which seems not
to break the build for dark reason on some linux configuration ?

      parent reply	other threads:[~2019-03-10 15:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-08 12:56 [Buildroot] issue to build elfutils due to libintl Arthur LAMBERT
2019-03-08 22:49 ` Peter Seiderer
2019-03-09 16:34   ` Arthur LAMBERT
2019-03-09 21:08     ` Peter Seiderer
2019-03-10 15:14   ` Arthur LAMBERT [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=20190310151426.GA11489@arthur-bzh \
    --to=lambertarthur22@gmail.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.