[klibc] klibc 1.5.20 falls into an finite loop during build against linux 2.6.35.4

[kelly white]

The same slackbuild script builds well on my laptop while it falls
into an infinite loop on my desktop.
My laptop has slackware64-13.1, and my desktop has slackware64-current.
The infinite loop could have been specific slackware64-current or
there are other causes.


On Sun, Oct 17, 2010 at 2:31 AM, crocket <crockabiscuit at yahoo.com> wrote:

>> This is repeated indefinitely.
>> I used my own slackbuild script to build klibc and the script is included as
>> klibc.tar.bz2 in this message.
>> I also included .config I used to build kernel as config-generic-2.6.35.4.
>>
>> To build with my script, extract klibc.tar.bz2, and execute klibc.SlackBuild
>> with klibc-1.5.20.tar.bz2 in the same folder as klibc.SlackBuild.

>I'm using a different approach instead of a SlackBuild script.  My
>script imports and partially builds a version selected kernel because
>I'm doing builds against a number of different kernels.  The host
>kernel is 2.6.33.4 as originally installed in Slackware 13.1.  With
>klibc 1.5.20 and linux 2.6.35.4 as the source kernel to build against,
>I did not have any build loops in both 32 bit and 64 bit.  So maybe it
>is some aspect of trying to build in a way needed by the SlackBuild
>approach?