From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8606] New: Problem compiling on Arch Linux
Date: Thu, 14 Jan 2016 21:57:57 +0000 [thread overview]
Message-ID: <bug-8606-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=8606
Bug ID: 8606
Summary: Problem compiling on Arch Linux
Product: buildroot
Version: 2015.11
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: l.andro.cs at gmail.com
CC: buildroot at uclibc.org
Hello,
This is not technically a bug with buildroot, but with libiconv in Arch
Linux, but the only "workaround" that I found so far has to be done with the
"configure" phase of building anything that use libiconv on Arch Linux.
I need to pass "--with-libiconv" option to the configure script of uCLib, or
any other that use the HOST (Arch Linux, in this case) libiconv, so that the
configure can setup the compiler to find it.
So, how can I pass this option in buildroot?
Thanks.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2016-01-14 21:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 21:57 bugzilla at busybox.net [this message]
2016-01-16 17:29 ` [Buildroot] [Bug 8606] Problem compiling on Arch Linux bugzilla at busybox.net
2016-02-14 21: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-8606-163@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