Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15376] Libiconv config
Date: Sun, 12 Mar 2023 17:47:35 +0000	[thread overview]
Message-ID: <bug-15376-163-q3RFp9Lm3M@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-15376-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=15376

Yann E. MORIN <yann.morin.1998@free.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |yann.morin.1998@free.fr

--- Comment #1 from Yann E. MORIN <yann.morin.1998@free.fr> ---
Igor, All,

Thanks for your report.

However, you did not provide enough information. Can you provide:
  * the version of Buildroot you are using
  * the defconfig file your are using

I was also not able to reproduce with current master; the following ran
for quite some time, but trigerred not (related) issue:

    $ while ! ( grep -q -E '^BR2_PACKAGE_LIBICONV=y' .config \
             && grep -q -E '^BR2_ENABLE_LOCALE=y' .config)
    do
        make randconfig
    done

Regards,
Yann E. MORIN.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2023-03-12 17:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-06 22:06 [Buildroot] [Bug 15376] New: Libiconv config bugzilla
2023-03-06 22:08 ` [Buildroot] [Bug 15376] " bugzilla
2023-03-12 17:47 ` bugzilla [this message]
2023-03-14 21:37 ` bugzilla

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=bug-15376-163-q3RFp9Lm3M@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@uclibc.org \
    /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