From: Andre <armcc2000@yahoo.com>
To: buildroot@busybox.net
Subject: [Buildroot] uClibc doesn't include legacy SuSv3 support by default anymore...
Date: Wed, 6 Dec 2006 17:08:54 -0800 (PST) [thread overview]
Message-ID: <820140.22973.qm@web35601.mail.mud.yahoo.com> (raw)
http://buildroot.uclibc.org/cgi-bin/viewcvs.cgi?rev=16732&view=rev
SuSv3 legacy support is required to build apps such as Wireless
Tools. Tweak Buildroot's default uClibc.config to compensate:
Index: toolchain/uClibc/uClibc.config
===========================================================
--- toolchain/uClibc/uClibc.config (revision 16783)
+++ toolchain/uClibc/uClibc.config (working copy)
@@ -84,6 +84,7 @@
UCLIBC_DYNAMIC_ATEXIT=y
# COMPAT_ATEXIT is not set
# UCLIBC_SUSV3_LEGACY is not set
+UCLIBC_SUSV3_LEGACY_MACROS=y
HAS_SHADOW=y
# UCLIBC_HAS_PROGRAM_INVOCATION_NAME is not set
UCLIBC_HAS___PROGNAME=y
Andre
--
____________________________________________________________________________________
Need a quick answer? Get one in minutes from people who know.
Ask your question on www.Answers.yahoo.com
next reply other threads:[~2006-12-07 1:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-07 1:08 Andre [this message]
2006-12-08 12:41 ` [Buildroot] uClibc doesn't include legacy SuSv3 support by default anymore Bernhard Fischer
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=820140.22973.qm@web35601.mail.mud.yahoo.com \
--to=armcc2000@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox