From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12031] Build of cups-filters fails while linking, apparently due to missing libiconv
Date: Fri, 19 Jul 2019 17:11:40 +0000 [thread overview]
Message-ID: <bug-12031-163-2GL9iKvbtN@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-12031-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=12031
jakobcornell at gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #8161|requested config |incorrect config - do not
description| |use
Attachment #8161|0 |1
is obsolete| |
--- Comment #4 from jakobcornell at gmail.com ---
Comment on attachment 8161
--> https://bugs.busybox.net/attachment.cgi?id=8161
incorrect config - do not use
I'd changed some config parameters since getting the issue, so this config
doesn't cause the error. Stay tuned for the proper config.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-07-19 17:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-11 6:23 [Buildroot] [Bug 12031] New: Build of cups-filters fails while linking, apparently due to missing libiconv bugzilla at busybox.net
2019-07-12 18:52 ` [Buildroot] [Bug 12031] " bugzilla at busybox.net
2019-07-18 20:34 ` bugzilla at busybox.net
2019-07-19 4:25 ` bugzilla at busybox.net
2019-07-19 17:11 ` bugzilla at busybox.net [this message]
2019-07-19 18:56 ` bugzilla at busybox.net
2019-07-22 6:52 ` bugzilla at busybox.net
2019-07-22 7:16 ` bugzilla at busybox.net
2019-07-22 7:35 ` bugzilla at busybox.net
2019-07-22 11:05 ` bugzilla at busybox.net
2019-07-22 20:59 ` bugzilla at busybox.net
2019-09-21 17:09 ` bugzilla at busybox.net
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-12031-163-2GL9iKvbtN@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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