Chapter 6.9 - Glibc Make Install Errors

Jonathan Haws Jonathan.Haws at sdl.usu.edu
Mon Jun 11 07:22:21 PDT 2007


> Any time something tries to run 'no', it means configure tested for
> something and didn't find it, but the package failed to allow for
> that outcome.  Since it is trying to pass what sounds like a perl
> script to it, I surmise that you either failed to install perl, or
> you did something wrong when installing perl (I used to be good at
> leaving the old hard-coded perl version in my script across version
> upgrades, perhaps you made a typo in installing it).
> 
> ?en

Ken, 

I appreciate the response.  I will check into Perl.  I have triple
checked all the steps since the beginning of Ch6, but haven't gone back
to Ch. 5.  I will probably try reinstalling Perl as defined in Ch. 5
then come back to the Glibc in Ch. 6.  I'll let you know how that goes.
Thanks for the input.

Jonathan R. Haws
Jonathan.Haws at sdl.usu.edu
 
 
-----Original Message-----
From: lfs-support-bounces at linuxfromscratch.org
[mailto:lfs-support-bounces at linuxfromscratch.org] On Behalf Of
lfs-support-request at linuxfromscratch.org
Sent: Saturday, June 09, 2007 12:00 AM
To: lfs-support at linuxfromscratch.org
Subject: lfs-support Digest, Vol 1215, Issue 1

Send lfs-support mailing list submissions to
	lfs-support at linuxfromscratch.org

To subscribe or unsubscribe via the World Wide Web, visit
	http://linuxfromscratch.org/mailman/listinfo/lfs-support
or, via email, send a message with subject or body 'help' to
	lfs-support-request at linuxfromscratch.org

You can reach the person managing the list at
	lfs-support-owner at linuxfromscratch.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of lfs-support digest..."


Today's Topics:

   1. Chapter 6.9 - Glibc Make Install Errors (Jonathan Haws)
   2. Re: Headers problems (Tijnema)
   3. Re: Chapter 6.9 - Glibc Make Install Errors (Tijnema)
   4. Re: modprobe the right modules & hard drives not shown still
      (Tijnema)
   5. Re: Chapter 6.9 - Glibc Make Install Errors (Ken Moffat)
   6. Re: Headers problems (Ken Moffat)
   7. Re: Chapter 6.9 - Glibc Make Install Errors (Tijnema)
   8. Re: Headers problems (Tijnema)
   9. Re: Headers problems (Tijnema)
  10. Re: building LFS gcc compilation problem (Mauricio Henriquez)


----------------------------------------------------------------------

Message: 1
Date: Fri, 8 Jun 2007 14:17:21 -0600
From: "Jonathan Haws" <Jonathan.Haws at sdl.usu.edu>
Subject: Chapter 6.9 - Glibc Make Install Errors
To: <lfs-support at linuxfromscratch.org>
Message-ID:
	<468EB9093DC44F4D9CBADE5C87BE5D19AF579C at cobra.usurf.usu.edu>
Content-Type: text/plain;	charset="iso-8859-1"

When trying to install the Glibc headers in LFS there are numerous
issues.  First, make -k check produces quite a few errors (I will post
them all once I run the test again).  Most are nptl, which from what I
have read are nothing to worry about.  I am using the LiveCD as the
host.  Now down to the real problem:

I decided to continue when I read about not worrying about nptl, so the
next step is to run:

make install

When this is run, it fails at the end with these messages:

make[2]: Entering directory '/build/gclibc-2.3.6/manual'
pwd='pwd'; \
no libm-err-tab.pl $pwd/.. > lib-err-tmp
/bin/sh: no: command not found <<-----------------I believe the problem
is here!
make[2]: *** [stamp-libm-err] Error 127
make[2]: Leaving directory '/build/glibc-2.3.6/manual'
make[1]: *** [manual/subdir_install] Error 2
make[1]: Leaving directory '/build/glibc-2.3.6'
make: *** [install] Error 2
root:/build/glibc-build#

I have searched and cannot find a resolution.  I can't continue,
obviously without working headers, so I could use some expert help.
Thanks in advance!

Jonathan R. Haws
Jonathan.Haws at sdl.usu.edu
?
?



------------------------------

Message: 2
Date: Fri, 8 Jun 2007 23:23:19 +0200
From: Tijnema <tijnema at gmail.com>
Subject: Re: Headers problems
To: "LFS Support List" <lfs-support at linuxfromscratch.org>
Message-ID:
	<d8269d910706081423h7ba46de5p6d17fd5bcc1f53d9 at mail.gmail.com>
Content-Type: text/plain; charset=EUC-KR; format=flowed

On 6/8/07, Ken Moffat <ken at linuxfromscratch.org> wrote:
> On Fri, Jun 08, 2007 at 05:34:29PM +0200, Tijnema wrote:
> > On 6/8/07, Ken Moffat <ken at linuxfromscratch.org> wrote:
> > > > I'm currently at glibc-2.3.6, and I would love to upgrade it to
> > > > glibc-2.6,
> > >
> > >  Why ?  I've only built glibc-2.6 on ppc64, to see if it helped
with
> > > the showstopper gcc-4.2 problems (it didn't), but I came across
posts
> > > on diy-linux pointing to some problems, both with itself (maybe
> > > 2.6.1 will be released) and with its decision to include a version
> > > of futimens().
> >
> > I hate old versions :P I want to keep my system up to date, so when
I
> > want to install a small app, i don't need to reinstall my complete
> > system because glibc is outdated :P
> >
>  If glibc suddenly provides a new feature, it will take time for
> applications to be altered to test for it and use it.  For
> bug-fixes, no doubt they are nice (if they work correctly), but I
> don't follow the toolchain lists so I've no idea what fixes have
> gone in, or if any of the bugs are likely to bite me.
>
>  As to your hardware problems, I can't think of anything else to
> suggest.  If it was mine, I'd eventually be tempted to start swapping
> things around (e.g. power supply) in case it helped (simply because a
> box that can't build gcc isn't very useful to me).
>
> ?en

It can build GCC fine, I've builded a complete GCC package (Including
ada, fortran,...) lately, I just didn't run GCC testsuite completely,
but compiling and installing works fine, and gcc works fine now :)

I can swap psu of the thing, but that's it, I don't have replacement
parts for such old PC... I mean it's socket A with SD Ram...
Oh yeah, i can replace GFX card and LAN card etc, but would that
matter? I don't think so...

And how sure are you that it is a hardware problem, and not a software
problem? Maybe a specific number of simultaneous threads?

Tijnema

------------------------------

Message: 3
Date: Fri, 8 Jun 2007 23:29:30 +0200
From: Tijnema <tijnema at gmail.com>
Subject: Re: Chapter 6.9 - Glibc Make Install Errors
To: "LFS Support List" <lfs-support at linuxfromscratch.org>
Message-ID:
	<d8269d910706081429o78cc452em37b0a9b2ab13db85 at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

On 6/8/07, Jonathan Haws <Jonathan.Haws at sdl.usu.edu> wrote:
> When trying to install the Glibc headers in LFS there are numerous
issues.  First, make -k check produces quite a few errors (I will post
them all once I run the test again).  Most are nptl, which from what I
have read are nothing to worry about.  I am using the LiveCD as the
host.  Now down to the real problem:
>
> I decided to continue when I read about not worrying about nptl, so
the next step is to run:
>
> make install
>
> When this is run, it fails at the end with these messages:
>
> make[2]: Entering directory '/build/gclibc-2.3.6/manual'
> pwd='pwd'; \
> no libm-err-tab.pl $pwd/.. > lib-err-tmp
> /bin/sh: no: command not found <<-----------------I believe the
problem is here!
> make[2]: *** [stamp-libm-err] Error 127
> make[2]: Leaving directory '/build/glibc-2.3.6/manual'
> make[1]: *** [manual/subdir_install] Error 2
> make[1]: Leaving directory '/build/glibc-2.3.6'
> make: *** [install] Error 2
> root:/build/glibc-build#
>
> I have searched and cannot find a resolution.  I can't continue,
obviously without working headers, so I could use some expert help.
Thanks in advance!
>
> Jonathan R. Haws
> Jonathan.Haws at sdl.usu.edu

Seems like the symlink to bash is missing, try this:
ln -s bash /bin/sh

That would create the required symlink, and your install command
should run fine.

Tijnema


------------------------------

Message: 4
Date: Fri, 8 Jun 2007 23:57:29 +0200
From: Tijnema <tijnema at gmail.com>
Subject: Re: modprobe the right modules & hard drives not shown still
To: "LFS Support List" <lfs-support at linuxfromscratch.org>
Message-ID:
	<d8269d910706081457v2b3a64e8hf02809be87171978 at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

On 6/7/07, junk at realtechtalk.com <junk at realtechtalk.com> wrote:
> Hi guys
>
> I have run modprobe for the modules I know are correct and I actually
> get output/feedback from.
> But when I run fdisk -l I get nothing still
>
> The only surefire way I know to get my hard drives working is to
compile
> every single driver into the kernel, but of course this is inefficient
>
> What am I missing here?  I loaded the correct modules for my SATA and
> SCSI controller but I still don't see my drives.
>
> Thanks guys!

Try running the udev boot script, or run the udev programs manually like
this:
udevtrigger
udevsettle
When both are done, you're new drives are probably created

Tijnema


------------------------------

Message: 5
Date: Fri, 8 Jun 2007 23:19:48 +0100
From: Ken Moffat <ken at linuxfromscratch.org>
Subject: Re: Chapter 6.9 - Glibc Make Install Errors
To: LFS Support List <lfs-support at linuxfromscratch.org>
Message-ID: <20070608221948.GA26354 at deepthought>
Content-Type: text/plain; charset=utf-8

On Fri, Jun 08, 2007 at 02:17:21PM -0600, Jonathan Haws wrote:
> 
> I decided to continue when I read about not worrying about nptl, so
the next step is to run:
> 
> make install
> 
> When this is run, it fails at the end with these messages:
> 
> make[2]: Entering directory '/build/gclibc-2.3.6/manual'
> pwd='pwd'; \
> no libm-err-tab.pl $pwd/.. > lib-err-tmp
> /bin/sh: no: command not found <<-----------------I believe the
problem is here!

 Any time something tries to run 'no', it means configure tested for
something and didn't find it, but the package failed to allow for
that outcome.  Since it is trying to pass what sounds like a perl
script to it, I surmise that you either failed to install perl, or
you did something wrong when installing perl (I used to be good at
leaving the old hard-coded perl version in my script across version
upgrades, perhaps you made a typo in installing it).

?en
-- 
das eine Mal als Trag?die, das andere Mal als Farce


------------------------------

Message: 6
Date: Fri, 8 Jun 2007 23:56:30 +0100
From: Ken Moffat <ken at linuxfromscratch.org>
Subject: Re: Headers problems
To: LFS Support List <lfs-support at linuxfromscratch.org>
Message-ID: <20070608225630.GB26354 at deepthought>
Content-Type: text/plain; charset=utf-8

On Fri, Jun 08, 2007 at 11:23:19PM +0200, Tijnema wrote:
> 
> It can build GCC fine, I've builded a complete GCC package (Including
> ada, fortran,...) lately, I just didn't run GCC testsuite completely,
> but compiling and installing works fine, and gcc works fine now :)
> 
 Oh, I misunderstood.  Testing should be easier than compiling, a
lot of the time the box sits fairly idle during tests.

> I can swap psu of the thing, but that's it, I don't have replacement
> parts for such old PC... I mean it's socket A with SD Ram...
> Oh yeah, i can replace GFX card and LAN card etc, but would that
> matter? I don't think so...
> 

 I've known memory to fail, particularly PC100/PC133 SDRAM, but you
said you had run memtest.  Unrelatedly, I was idly reading a
magazine this afternoon which showed how to thermal paste, and
showed an athlon XP in the picture (the answer, as you probably
know, is "use as little as possible").

 I suppose you could try lm_sensors.  Build _all_ the possible
sensors as modules, let the package try them out and hope it doesn't
lock up the box modprobing isa etc, then see if the results (if any)
make any sense - often, you need a degree in the black arts to get
the configuration correct, but I suppose you could keep an eye on
indicated voltages and temperatures while running a test.

> And how sure are you that it is a hardware problem, and not a software
> problem? Maybe a specific number of simultaneous threads?
> 

 I'm not especially sure, but your hardware is at least common and
in wide use, so I'm fairly confident it doesn't have too many weird
bugs.  I don't think the number of threads will make much difference
- a non-SMP machine can schedule exactly one process at a time (and
you'll have things like X, xterm, kswapd, kjournald kicking in even
when it's nominally idle, so it is always switching processes
although something like CONFIG_HZ_1000 would probably increase the
overhead and hence the load.

 However, you said you had to underclock it to get it to boot.  That
certainly sounds like a hardware problem.

 If you can be bothered to try the things that usually lock it up,
you could have 'top' running at the same time to see what sort of
load average and swap usage you have.

 My personal experience is that shutdowns or reboots are caused by
(i) insane hardware (which doesn't apply to your case)
(ii) hardware failing or just wearing out
(iii) inadequate cooling
(iv) cosmic rays, or suchlike - I went through a period at the
start of the year when one of my x86_64 boxes would sporadically
reboot.  Each time it was in X, so nothing made it to the logs, and
each time it happened to be running a 32-bit kernel.  After taking
it to lkml, the problem eventually disappeared.  In the meantime, a
separate thread on lkml strayed into the area of "there has been a
lot of cosmic ray (or alpha particle, or something - I no longer
remember) activity which can cause 'random' errors".

?en
-- 
das eine Mal als Trag?die, das andere Mal als Farce


------------------------------

Message: 7
Date: Sat, 9 Jun 2007 01:21:20 +0200
From: Tijnema <tijnema at gmail.com>
Subject: Re: Chapter 6.9 - Glibc Make Install Errors
To: "LFS Support List" <lfs-support at linuxfromscratch.org>
Message-ID:
	<d8269d910706081621s6a7bd133y2cd2db1b877d0847 at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

On 6/8/07, Tijnema <tijnema at gmail.com> wrote:
> On 6/8/07, Jonathan Haws <Jonathan.Haws at sdl.usu.edu> wrote:
> > When trying to install the Glibc headers in LFS there are numerous
issues.  First, make -k check produces quite a few errors (I will post
them all once I run the test again).  Most are nptl, which from what I
have read are nothing to worry about.  I am using the LiveCD as the
host.  Now down to the real problem:
> >
> > I decided to continue when I read about not worrying about nptl, so
the next step is to run:
> >
> > make install
> >
> > When this is run, it fails at the end with these messages:
> >
> > make[2]: Entering directory '/build/gclibc-2.3.6/manual'
> > pwd='pwd'; \
> > no libm-err-tab.pl $pwd/.. > lib-err-tmp
> > /bin/sh: no: command not found <<-----------------I believe the
problem is here!
> > make[2]: *** [stamp-libm-err] Error 127
> > make[2]: Leaving directory '/build/glibc-2.3.6/manual'
> > make[1]: *** [manual/subdir_install] Error 2
> > make[1]: Leaving directory '/build/glibc-2.3.6'
> > make: *** [install] Error 2
> > root:/build/glibc-build#
> >
> > I have searched and cannot find a resolution.  I can't continue,
obviously without working headers, so I could use some expert help.
Thanks in advance!
> >
> > Jonathan R. Haws
> > Jonathan.Haws at sdl.usu.edu
>
> Seems like the symlink to bash is missing, try this:
> ln -s bash /bin/sh
>
> That would create the required symlink, and your install command
> should run fine.
>
> Tijnema

Ok, forgive me pls :P I must be sleeping when making this post...

Tijnema
>


------------------------------

Message: 8
Date: Sat, 9 Jun 2007 03:26:08 +0200
From: Tijnema <tijnema at gmail.com>
Subject: Re: Headers problems
To: "LFS Support List" <lfs-support at linuxfromscratch.org>
Message-ID:
	<d8269d910706081826l341f0704i924a59ca9802466c at mail.gmail.com>
Content-Type: text/plain; charset=EUC-KR; format=flowed

On 6/9/07, Ken Moffat <ken at linuxfromscratch.org> wrote:
> On Fri, Jun 08, 2007 at 11:23:19PM +0200, Tijnema wrote:
> >
> > It can build GCC fine, I've builded a complete GCC package
(Including
> > ada, fortran,...) lately, I just didn't run GCC testsuite
completely,
> > but compiling and installing works fine, and gcc works fine now :)
> >
>  Oh, I misunderstood.  Testing should be easier than compiling, a
> lot of the time the box sits fairly idle during tests.

Hmm, it's always at the same point, or atleast the same file:
/gcc/testsuite/gcc.c-torture/execute/execute.exp
>
> > I can swap psu of the thing, but that's it, I don't have replacement
> > parts for such old PC... I mean it's socket A with SD Ram...
> > Oh yeah, i can replace GFX card and LAN card etc, but would that
> > matter? I don't think so...
> >
>
>  I've known memory to fail, particularly PC100/PC133 SDRAM, but you
> said you had run memtest.  Unrelatedly, I was idly reading a
> magazine this afternoon which showed how to thermal paste, and
> showed an athlon XP in the picture (the answer, as you probably
> know, is "use as little as possible").

Yes, i've ran memtest lately, maybe i'll run it again once these days...
I think my thermal paste is gone :P dryed out or such.
>
>  I suppose you could try lm_sensors.  Build _all_ the possible
> sensors as modules, let the package try them out and hope it doesn't
> lock up the box modprobing isa etc, then see if the results (if any)
> make any sense - often, you need a degree in the black arts to get
> the configuration correct, but I suppose you could keep an eye on
> indicated voltages and temperatures while running a test.

Hmm, didn't know of that program, and will defenitly take a look at it
, thanks :)
>
> > And how sure are you that it is a hardware problem, and not a
software
> > problem? Maybe a specific number of simultaneous threads?
> >
>
>  I'm not especially sure, but your hardware is at least common and
> in wide use, so I'm fairly confident it doesn't have too many weird
> bugs.  I don't think the number of threads will make much difference
> - a non-SMP machine can schedule exactly one process at a time (and
> you'll have things like X, xterm, kswapd, kjournald kicking in even
> when it's nominally idle, so it is always switching processes
> although something like CONFIG_HZ_1000 would probably increase the
> overhead and hence the load.
Good to know :)
>
>  However, you said you had to underclock it to get it to boot.  That
> certainly sounds like a hardware problem.
yes, but it might be motherboard related or such, as when I had it at
full speed, what worked before but once stopped working, i don't even
get a screen, and fans aren't starting too...


>
>  If you can be bothered to try the things that usually lock it up,
> you could have 'top' running at the same time to see what sort of
> load average and swap usage you have.

I'm running top and the gcc testsuite now, but i'm using already
installed source with some weird symlinks, defenitly not the correct
way to test, but hope it works enough
>
>  My personal experience is that shutdowns or reboots are caused by
> (i) insane hardware (which doesn't apply to your case)
> (ii) hardware failing or just wearing out
> (iii) inadequate cooling
> (iv) cosmic rays, or suchlike - I went through a period at the
> start of the year when one of my x86_64 boxes would sporadically
> reboot.  Each time it was in X, so nothing made it to the logs, and
> each time it happened to be running a 32-bit kernel.  After taking
> it to lkml, the problem eventually disappeared.  In the meantime, a
> separate thread on lkml strayed into the area of "there has been a
> lot of cosmic ray (or alpha particle, or something - I no longer
> remember) activity which can cause 'random' errors".
>
> ?en

I don't think i'm affected by IV either, because the pc is standing
alone in the room, no other digital things inside same room, so then
iot must come out of another room, but if that would be, than AMD
Athlon's couldn't be sold i think.

Then II and III are left, II might be the actual problem, i'm thinking
about a damaged motherboard, as I already repaired it a few times,
changed leaking condensators and such.
III is last option i think, but i think the problem came more or less
when the original fan was damaged and i replaced it with a standard
8CM fan..

Tijnema

------------------------------

Message: 9
Date: Sat, 9 Jun 2007 03:36:07 +0200
From: Tijnema <tijnema at gmail.com>
Subject: Re: Headers problems
To: "LFS Support List" <lfs-support at linuxfromscratch.org>
Message-ID:
	<d8269d910706081836v1814b2edt11b224d59e6ae451 at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

On 6/9/07, Tijnema <tijnema at gmail.com> wrote:
> On 6/9/07, Ken Moffat <ken at linuxfromscratch.org> wrote:
> >
> >  If you can be bothered to try the things that usually lock it up,
> > you could have 'top' running at the same time to see what sort of
> > load average and swap usage you have.
>
> I'm running top and the gcc testsuite now, but i'm using already
> installed source with some weird symlinks, defenitly not the correct
> way to test, but hope it works enough

It just went down, after i ran the GCC testsuite again, left screen
shows test suite, right screen show last update of top before it went
down.
Screen:
http://img201.imageshack.us/img201/3600/topyp3.png

Please have a look at it, as I don't see anything weird, and CPU usage
isn't too high, but screen is only updated once in 3 seconds it looks,
so the actual CPU usage at reboot point might be slightly different...

Tijnema


------------------------------

Message: 10
Date: Fri, 08 Jun 2007 21:55:46 -0400
From: Mauricio Henriquez <mhenriquezs at terra.cl>
Subject: Re: building LFS gcc compilation problem
To: LFS Support List <lfs-support at linuxfromscratch.org>
Message-ID: <466A08A2.7020303 at terra.cl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed


uuuhuuuu!!!, my new shiny LFS (by hand no automatic tool) system is 
ready!!!, thank you very much fo such a great book, I follow they 
instructions one by one and I don't have any problem, the book don't 
have even a typo bug.
...now to read and follow BFLS book...my new system have only a basic 
bash console but I think that is better than Fedora 7...uhuuu jajaja :-)

Mauricio, from Chili

Mauricio Henriquez wrote:
> Hi to all:
>
> thank for your quick help, I re-read your book instruction and off 
> course you don't put anything on there that is not necesary :-) I was 
> using the Gcc compiled version of the chapter 5 of the book, I delete 
> the folder, re-extract and build again without problems.
>
> As I think, only a begginer problem...sorry :-( I had panic :-) , from

> now on I going to re-re-read your book instruction more carefully.. I 
> try to finish the job now.
>
> thanks again..
>
> Mauricio
>
> Dan Nicholson wrote:
>   
>> Welcome.
>>
>> On 6/6/07, mhenriquezs at terra.cl <mhenriquezs at terra.cl> wrote:
>>   
>>     
>>> #Gcc Make error (page 97 of the PDF LFS 6.2 book)
>>> In file included from ../../gcc-4.0.3/gcc/crtstuff.c:64:
>>> ../../gcc-4.0.3/gcc/tsystem.h:90:19: error: stdio.h: No such file or
directory
>>> ../../gcc-4.0.3/gcc/tsystem.h:93:23: error: sys/types.h: No such
file or
>>> directory
>>>     
>>>       
>> I know this has come up before, but I can't recall what the issue is
>> exactly. So, at that point, it should be finding those headers from
>> the Ch. 5 glibc in /tools/include. But it's not for some reason.
>>
>> So, do those headers exist? You should definitely have
>> /tools/include/stdio.h. If so, let's find out where gcc is trying to
>> look. Here's a quick one-liner to make gcc be verbose about what it's
>> doing.
>>
>> # echo | gcc -v -x c -
>>
>> That should spit out some info including where the system header
>> search path is. Mine (using the final gcc) says:
>>
>> #include <...> search starts here:
>>  /usr/local/include
>>  /usr/lib/gcc/i686-pc-linux-gnu/4.1.2/include
>>  /usr/include
>> End of search list.
>>
>> Yours should include /tools/include and /tools/lib/gcc-... What does
>> it say for you?
>>
>> --
>> Dan
>>   
>>     
>
>   



------------------------------

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page


End of lfs-support Digest, Vol 1215, Issue 1
********************************************



More information about the lfs-support mailing list