All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas De Schampheleire <patrickdepinguin@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2013-11-12
Date: Wed, 13 Nov 2013 21:18:51 +0100	[thread overview]
Message-ID: <CAAXf6LWVm8bYNzScEA=iqE42QzbeSGP1-LTShCmAW4bNZJqFWg@mail.gmail.com> (raw)
In-Reply-To: <CAAXf6LWgt30AW1tNK=uNgvY=7gJqgT3QVxkPtuP4YDSmiSDKZA@mail.gmail.com>

On Wed, Nov 13, 2013 at 5:22 PM, Thomas De Schampheleire
<patrickdepinguin@gmail.com> wrote:
> Hi,
>
> On Wed, Nov 13, 2013 at 8:30 AM, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
>> Build statistics for 2013-11-12
>> ===============================
> [..]
>>        sh4 |               vim-699f8d8f096d | NOK | http://autobuild.buildroot.net/results/21b5a910e6a27fa1cb12d0002ffed7e6ed9d6c83/
>
> The problem here is:
> edit.c:(.text+0x1614): undefined reference to `libintl_gettext'
>
> So seems gettext related.
> I cannot yet reproduce this bug. I tried a limited build 'make
> toolchain vim' and also 'make toolchain gettext vim', but both work
> fine with that same defonfig.
>
> Interestingly, the autobuild configure output says:
> checking for NLS... gettext() works
> while in my reproduction it says:
> checking for NLS... gettext() works with -lintl
>
> This is a difference I cannot explain. I'm currently trying a full
> rebuild, but any input in the mean time is welcome...

FYI, I have seen the problem on a full rebuild, will analyze the
difference and get back...

  reply	other threads:[~2013-11-13 20:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-13  7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2013-11-12 Thomas Petazzoni
2013-11-13 16:22 ` Thomas De Schampheleire
2013-11-13 20:18   ` Thomas De Schampheleire [this message]
2013-11-14 12:51     ` Thomas De Schampheleire

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='CAAXf6LWVm8bYNzScEA=iqE42QzbeSGP1-LTShCmAW4bNZJqFWg@mail.gmail.com' \
    --to=patrickdepinguin@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.