[Buildroot] problems compiling crosstools-ng

[Buildroot] problems compiling crosstools-ng

[chris at basementcode.com]

 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

[Buildroot] problems compiling crosstools-ng

[Yann E. MORIN]

Cris, All,

On Tuesday 22 March 2011 15:24:39 chris at basementcode.com wrote:
>  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.

Basically, I'd say:
- if crosstool-NG works OK standalone, but fails in buildroot with the
  same options, then the issue is to be reported here, on the BR ML,
- but if crosstool-NG does not work standalone with the same config
  options, then please report to the crossgcc ML.

>  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?

Do you mean the m4 built by buildroot as a package, or the m4 built by
crosstool-NG as part of the companion tools (which you should not use,
except under very exceptional conditions) ?

>  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.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

[Buildroot] problems compiling crosstools-ng

[Oleg Sadov]

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.

> Regards,
> Yann E. MORIN.

SY
--Oleg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 002-crosstool-NG.sh.patch
Type: text/x-patch
Size: 935 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110322/ca6a9c70/attachment.bin>

[Buildroot] problems compiling crosstools-ng

[chris at basementcode.com]

 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