From: chris at basementcode.com <chris@basementcode.com>
To: buildroot@busybox.net
Subject: [Buildroot] problems compiling crosstools-ng
Date: Tue, 22 Mar 2011 09:24:39 -0500 [thread overview]
Message-ID: <cd12ab38cf1fa34fa4c10dfaf6eec135@basementcode.com> (raw)
I'm not sure if this belongs in the crosstools mailing list, or the
buildroot mailing list, so sorry if this in the wrong place.
I'm having a fair amount of trouble compiling the crosstools-ng
toolchain.
I just wanted to post the errors that I was unable to get around while
compiling with various versions of buildroot.
buildroot-2010.11:
m4 gives and error and says "--gnu" is not a valid option.
I have m4-1.4.15 installed, and the man page says that --gnu is valid.
Does buildroot have another copy of m4?
buildroot-2011.02:
during the configure stage of binutils the configure script spawns the
following process over and over until swap is filled and the system
crashes:
makeinfo --force --force --force --force --force --force --force
--force --force --force --force ......
Same for the latest git version.
I left the make menuconfig options as default, except to pick an arm
target and the crosstools-ng toolchain with glibc.
I'm running gentoo as a distro.
If anybody has encountered and solved these problems before, please let
me know.
thanks,
-Chris
next reply other threads:[~2011-03-22 14:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-22 14:24 chris at basementcode.com [this message]
2011-03-22 16:10 ` [Buildroot] problems compiling crosstools-ng Yann E. MORIN
2011-03-22 17:26 ` Oleg Sadov
2011-03-22 19:06 ` chris at basementcode.com
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=cd12ab38cf1fa34fa4c10dfaf6eec135@basementcode.com \
--to=chris@basementcode.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