Re: ./configure.lineno: fork: Cannot allocate memory

2009-09-22 Thread 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

./configure.lineno: fork: Cannot allocate memory

2009-09-22 Thread Pierre
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 an

Re: why not #include "config.h"?

2009-09-22 Thread Thomas Dickey
On Tue, 22 Sep 2009, Patrick Welche wrote: On Tue, Sep 22, 2009 at 10:49:58AM +0200, Steffen Dettmer wrote: I hope I don't ask a FAQ. If so, an URL would be appreciated. I've read here that someone could (should?) write #include specifying a system header instead of the IMHO correct #incl

Re: why not #include "config.h"?

2009-09-22 Thread Ralf Wildenhues
* Steffen Dettmer wrote on Tue, Sep 22, 2009 at 05:06:41PM CEST: > I though this was a kind of lazyness; just used "" and <> > interchangingly without deeper meaning? You can do that only as long as there is at most one header file with that name involved. > I tought correct is: > > - with -I (a

Re: why not #include "config.h"?

2009-09-22 Thread Steffen Dettmer
On Tue, Sep 22, 2009 at 3:02 PM, Patrick Welche wrote: > On Tue, Sep 22, 2009 at 10:49:58AM +0200, Steffen Dettmer wrote: >> I've read here that someone could (should?) write >>   #include >> specifying a system header instead of the IMHO correct >>   #include "config.h" > > I think this is the r

Re: why not #include "config.h"?

2009-09-22 Thread Patrick Welche
On Tue, Sep 22, 2009 at 10:49:58AM +0200, Steffen Dettmer wrote: > I hope I don't ask a FAQ. If so, an URL would be appreciated. > > I've read here that someone could (should?) write > #include > specifying a system header instead of the IMHO correct > #include "config.h" > > As far as I kno

why not #include "config.h"?

2009-09-22 Thread Steffen Dettmer
I hope I don't ask a FAQ. If so, an URL would be appreciated. I've read here that someone could (should?) write #include specifying a system header instead of the IMHO correct #include "config.h" As far as I know the difference is that in the first version system directories are searched but