Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: chris at basementcode.com <chris@basementcode.com>
To: buildroot@busybox.net
Subject: [Buildroot] problems compiling crosstools-ng
Date: Tue, 22 Mar 2011 14:06:18 -0500	[thread overview]
Message-ID: <e76b8d6c5f12b51b804484cba5fd787d@basementcode.com> (raw)
In-Reply-To: <1300814816.3848.93.camel@sadov-t.linux-ink.vo>

 On Tue, 22 Mar 2011 20:26:56 +0300, Oleg Sadov <sadov@linux-ink.ru> 
 wrote:
> 22/03/2011 17:10 +0100, Yann E. MORIN wrote:
>> On Tuesday 22 March 2011 15:24:39 chris at basementcode.com wrote:
>> >  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  ......
>>
>> Yes, I know about this issue. You're not the first one to report it, 
>> but I
>> was not able to reproduce it, not to understand how it can happen 
>> (although
>> I have a small idea, but I'm not sure)
>>
>> I'm doing some changes right now, that should fix the issue if all 
>> goes well.
>
> I've got the same problem on my RHEL-based system. Seems like the 
> root
> of problem in search path for commands setted up by Croostool-NG
> environment -- local script 'makeinfo' placed in path before the real
> 'makeinfo'. This script trying to execute 'makeinfo --force' command
> and, voil? -- we got the infinite recursion!
>
> Quck & dirty solution -- place the real path of makeinfo utility
> (usually /usr/bin/makeinfo) in crosstool-NG.sh. Just put attached to
> this mail patch in directory:
>
> toolchain/toolchain-crosstool-ng
>
> and rerun make -- hopefully your problem will be solved.
 It was solved. Thank you very much for the patch.
>
>> Regards,
>> Yann E. MORIN.
>
> SY
> --Oleg

 Yann, you had asked me some question earlier about this problem I was 
 having. I will get back to you with answers to them as soon as I have a 
 moment to investigate.

 thanks again,
 -Chris

      reply	other threads:[~2011-03-22 19:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-22 14:24 [Buildroot] problems compiling crosstools-ng chris at basementcode.com
2011-03-22 16:10 ` Yann E. MORIN
2011-03-22 17:26   ` Oleg Sadov
2011-03-22 19:06     ` chris at basementcode.com [this message]

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=e76b8d6c5f12b51b804484cba5fd787d@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