Building Glibc 2.1.2 again, again and again

Building Glibc 2.1.2 again, again and again

Post by Bj?rn-?ke Segrel » Mon, 10 Jan 2000 04:00:00



I finally built my glibc without errors.
And did a "make check" too. BUT where is the result from "make check" ?
It didn't report any errors as far as i could see.
Is there a log of  the outcome somewhere. I've been searching both rthe
source and build-drectories for some summarizing sort of log.
How can i tell if it's ok to do a "make install".

Any hints ?

 
 
 

Building Glibc 2.1.2 again, again and again

Post by Andrew Puruggan » Tue, 11 Jan 2000 04:00:00


: I finally built my glibc without errors.
: And did a "make check" too. BUT where is the result from "make check" ?
: It didn't report any errors as far as i could see.
: Is there a log of  the outcome somewhere. I've been searching both rthe
: source and build-drectories for some summarizing sort of log.
: How can i tell if it's ok to do a "make install".

: Any hints ?

Mine was all too happy dishing out errors. see if -echo does the trick.
It tells you where it's stepping into and out of

--
jazz            annandy AT dc DOT seflin DOT org
--------Fight for what you believe in:----------
Over-the-Roll Toilet Tissue Grabbers Enlist Now!

 
 
 

Building Glibc 2.1.2 again, again and again

Post by Steve Snyde » Thu, 13 Jan 2000 04:00:00



>I finally built my glibc without errors.
>And did a "make check" too. BUT where is the result from "make check" ?
>It didn't report any errors as far as i could see.
>Is there a log of  the outcome somewhere. I've been searching both rthe
>source and build-drectories for some summarizing sort of log.
>How can i tell if it's ok to do a "make install".

The fact that the "make check" didn't exit in error is confirmation
that none of the tests failed.  A failure of any of the tests would
cause make to quit.

Note that the success of "make check" doesn't guarantee a problem-free
build of glibc.  The tests exercise a pretty small percentage of the
functions supported by the libraries.  Don't get me wrong, doing a
"make check" is always a good idea.  Just don't consider it the last
word on the quality of the code.

***** Steve Snyder *****

 
 
 

Building Glibc 2.1.2 again, again and again

Post by Bj?rn-?ke Segrel » Tue, 18 Jan 2000 04:00:00




> > I finally built my glibc without errors.
> > And did a "make check" too. BUT where is the result from "make check" ?
> > It didn't report any errors as far as i could see.

> When "make check" does not abort, yup, then everything is ok and you can
> do a "make install" (after you have rebooted in single-user mode).

> --
> # Heinz Diehl, 68259 Mannheim, Germany

Darn !!!
I didn't reboot to single user.
Am I dead now, or just lucky :-)
 
 
 

Building Glibc 2.1.2 again, again and again

Post by Steve Snyde » Tue, 18 Jan 2000 04:00:00





>> > I finally built my glibc without errors.
>> > And did a "make check" too. BUT where is the result from "make check" ?
>> > It didn't report any errors as far as i could see.

>> When "make check" does not abort, yup, then everything is ok and you can
>> do a "make install" (after you have rebooted in single-user mode).

>> --
>> # Heinz Diehl, 68259 Mannheim, Germany

>Darn !!!
>I didn't reboot to single user.
>Am I dead now, or just lucky :-)

I never boot to single-user mode when I update the glibc libraries.  I
just install the RPMs (this is on a RedHat system) and reboot.  No
problems whatsoever.

***** Steve Snyder *****

 
 
 

1. Splitting c.o.l Again, and Again, and AGAIN!!!

I think I have the absolute best solution to the hoards/mounds/gobs
of articles posted to c.o.l ( The reason for the *proposed* split )

Why don't we create comp.os.linux.split and let all of this
discussion/CR*P go there.  That should cut the load by 10% - 20%.

infuriatingly yours, jeff

BTW ( By The Way, for the TLA impaired ) : I speak for MYSELF and no one else!
--

Yes, I Richard Chamberland do think that we are the creeeam of Hooollywood
talent.  Sorry let me take that again.   We are the cream of Hooollwood
taaaaleeent.  Oh forget it just give me a face lift.  - Spitting Image

2. Panasonic EIDE ATAPI Solution.

3. Again, again, and again

4. repairing damaged partition

5. LinuxMall spams again and again and again...

6. Linux Kernel revision history

7. PPP again, and again, and...

8. Mr Smith's "quality" software

9. System restart again and again automatically

10. GNORpm On again off again...

11. The newbie ask sth. again again...

12. System restart again and again automatically

13. ppp again (and again...)