./configure.lineno: fork: Cannot allocate memory

[Pierre-82]

Hello,

I built a Linux From Scratch 6.5 yesterday and had no problem doing
"./configure" and "make" under chroot for all the packages. But since my
reboot, when I chroot, if I launch any "./configure" script, nothing happens
on the screen (configure loops, I echoed some messages), consumes more and
more memory ("free -m" on the host), and at the end displays the following
error message :

root:/sources/file-5.03# ./configure
./configure.lineno: fork: Cannot allocate memory
./configure.lineno: fork: Cannot allocate memory
No shell found that supports shell functions.
Please tell autoconf@... about your system,
including any error possibly output before this
message
./configure.lineno: fork: Cannot allocate memory

Which isn't very explicit... Could you please help me determine what's wrong
in my configuration ?

Thanks in advance,

Pierre
_______________________________________________
Autoconf mailing list
Autoconf@...
http://lists.gnu.org/mailman/listinfo/autoconf

[Ralf Wildenhues]

Hello Pierre,

* Pierre wrote on Sat, Sep 19, 2009 at 11:28:20PM CEST:
> I built a Linux From Scratch 6.5 yesterday

which kind of puts you in the boat of fixing things yourself, no?  ;-)

> and had no problem doing
> "./configure" and "make" under chroot for all the packages. But since my
> reboot, when I chroot, if I launch any "./configure" script, nothing happens
> on the screen (configure loops, I echoed some messages), consumes more and
> more memory ("free -m" on the host), and at the end displays the following
> error message :

Can you add 'set -x' as second line to the configure script, run it, and
try to analyze it?  If it doesn't help, we're looking for reasons why it
"loops" (create and spawn configure.lineno more than once, or so).

You can post some of the output here, but if it's large, then please
gzip it.

Please mention which versions of Autoconf, (what?) shell, libc, and
kernel you're using.  sed, grep, awk, coreutils can't hurt either.

> root:/sources/file-5.03# ./configure
> ./configure.lineno: fork: Cannot allocate memory
> ./configure.lineno: fork: Cannot allocate memory
> No shell found that supports shell functions.
> Please tell autoconf@... about your system,
> including any error possibly output before this
> message
> ./configure.lineno: fork: Cannot allocate memory

Cheers,
Ralf


_______________________________________________
Autoconf mailing list
Autoconf@...
http://lists.gnu.org/mailman/listinfo/autoconf

[Pierre-82]

Hello Ralf,

As adviced, I added "set -x" in the configure script of File-5.03. The
software versions are those of LFS 6.5
(http://www.linuxfromscratch.org/lfs/view/stable/chapter03/packages.html)
:
- Autoconf-2.64
- Bash-4.0
- Glibc-2.10.1
- kernel : when I am chrooting, the one of my host system :
2.6.28-15-generic #49-Ubuntu SMP Tue Aug 18 18:40:08 UTC 2009 i686
GNU/Linux; when I am booting from the LFS partition : Linux-2.6.30.2
- Sed-4.2.1
- Grep-2.5.4
- Gawk-3.1.7
- Coreutils-7.4

While in chroot, I ran the following command :
"root:/sources/file-5.03# ./configure >configure_stdout.log
2>configure_stderr.log". At the end, the configure_stdout.log is
empty, while the configure_stderr.log contains all the messages... I
also ran the same command on the host system (on which I have no
problem).

Please find attached a tar.bz2 file containing :
- configure : the configure script of File-5.03 (with "set -x")
- configure_stderr_chroot.log : the logfile in the chroot
- configure_stderr_host.log : the logfile on the host system

Thanks a lot for your help,

Pierre

On Wed, Sep 23, 2009 at 6:45 AM, Ralf Wildenhues <Ralf.Wildenhues@...> wrote:

> Hello Pierre,
>
> * Pierre wrote on Sat, Sep 19, 2009 at 11:28:20PM CEST:
>> I built a Linux From Scratch 6.5 yesterday
>
> which kind of puts you in the boat of fixing things yourself, no?  ;-)
>
>> and had no problem doing
>> "./configure" and "make" under chroot for all the packages. But since my
>> reboot, when I chroot, if I launch any "./configure" script, nothing happens
>> on the screen (configure loops, I echoed some messages), consumes more and
>> more memory ("free -m" on the host), and at the end displays the following
>> error message :
>
> Can you add 'set -x' as second line to the configure script, run it, and
> try to analyze it?  If it doesn't help, we're looking for reasons why it
> "loops" (create and spawn configure.lineno more than once, or so).
>
> You can post some of the output here, but if it's large, then please
> gzip it.
>
> Please mention which versions of Autoconf, (what?) shell, libc, and
> kernel you're using.  sed, grep, awk, coreutils can't hurt either.
>
>> root:/sources/file-5.03# ./configure
>> ./configure.lineno: fork: Cannot allocate memory
>> ./configure.lineno: fork: Cannot allocate memory
>> No shell found that supports shell functions.
>> Please tell autoconf@... about your system,
>> including any error possibly output before this
>> message
>> ./configure.lineno: fork: Cannot allocate memory
>
> Cheers,
> Ralf
>

_______________________________________________
Autoconf mailing list
Autoconf@...
http://lists.gnu.org/mailman/listinfo/autoconf

[Ralf Wildenhues]

* Pierre wrote on Wed, Sep 23, 2009 at 11:56:56PM CEST:
> As adviced, I added "set -x" in the configure script of File-5.03. The
> software versions are those of LFS 6.5
> (http://www.linuxfromscratch.org/lfs/view/stable/chapter03/packages.html)
> :
> - Autoconf-2.64
> - Bash-4.0

Please update bash to the latest patchlevel as per
<http://ftp.gnu.org/gnu/bash/bash-4.0-patches/>
and retry.  If the error persists: no need to resend logs,
but please try this out in the chroot:
  expr 426 + 1

I suspect that either bash has a problem with backquoted command
substitution within unquoted here-documents or coreutils' expr is not
working correctly.

You should consider not using LFS if all of this doesn't make sense to
you.  ;-)

Incidentally, the next chapter of the above LFS documentation also lists
a bash patch.  Did you use it?

Cheers,
Ralf


_______________________________________________
Autoconf mailing list
Autoconf@...
http://lists.gnu.org/mailman/listinfo/autoconf

[Pierre-82]

Hello Ralf,

You are right, it seems that expr is broken. Here is the result of the
command you advised :
root:/# expr 426 + 1
Illegal instruction

I don't know why I didn't have the problem sooner though, as in LFS,
once a package is built it is used in the following steps... So I
suppose I should have had the problem with expr after building
coreutils in chapter 6.

Anyway, no problem, I understood your instructions ;-) And yes, I
carefully built every LFS package with the recommended patches...

Will have to rebuild coreutils then and see if it works...

Again, thanks for your help !

Pierre

On Thu, Sep 24, 2009 at 9:05 PM, Ralf Wildenhues <Ralf.Wildenhues@...> wrote:

> * Pierre wrote on Wed, Sep 23, 2009 at 11:56:56PM CEST:
>> As adviced, I added "set -x" in the configure script of File-5.03. The
>> software versions are those of LFS 6.5
>> (http://www.linuxfromscratch.org/lfs/view/stable/chapter03/packages.html)
>> :
>> - Autoconf-2.64
>> - Bash-4.0
>
> Please update bash to the latest patchlevel as per
> <http://ftp.gnu.org/gnu/bash/bash-4.0-patches/>
> and retry.  If the error persists: no need to resend logs,
> but please try this out in the chroot:
>  expr 426 + 1
>
> I suspect that either bash has a problem with backquoted command
> substitution within unquoted here-documents or coreutils' expr is not
> working correctly.
>
> You should consider not using LFS if all of this doesn't make sense to
> you.  ;-)
>
> Incidentally, the next chapter of the above LFS documentation also lists
> a bash patch.  Did you use it?
>
> Cheers,
> Ralf
>

_______________________________________________
Autoconf mailing list
Autoconf@...
http://lists.gnu.org/mailman/listinfo/autoconf

[Ralf Wildenhues]

Hello Pierre,

please don't top-post, thank you.

* Pierre wrote on Fri, Sep 25, 2009 at 09:40:50AM CEST:
>
> You are right, it seems that expr is broken. Here is the result of the
> command you advised :
> root:/# expr 426 + 1
> Illegal instruction
>
> I don't know why I didn't have the problem sooner though, as in LFS,
> once a package is built it is used in the following steps...

Do you run 'make check' for each package you're building?  Or is it that
coreutils test suite requires perl and you didn't have perl built yet?

> So I
> suppose I should have had the problem with expr after building
> coreutils in chapter 6.

Well, it would be nice if you could report the issue to LFS or to
bug-coreutils, after ensuring that it is indeed a bug in coreutils and
not a pilot error.

The error sounds like your compiler may be generating code that your
processor can't process.  Like if you built for i686 but then used the
code on an i486.

> Anyway, no problem, I understood your instructions ;-) And yes, I
> carefully built every LFS package with the recommended patches...

Thanks,
Ralf


_______________________________________________
Autoconf mailing list
Autoconf@...
http://lists.gnu.org/mailman/listinfo/autoconf