[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Just to be Sure




On Sun, 19 Jul 1998, Peter L. Peres wrote:

> >      glibc-debug-2.0.7-19.i386.rpm
> 
> required only if you're a C programmer and use gdb et al.

please.. lets not spread miss-information. there is no need what-so-ever
to install a debug version of these libraries, unless you want to modify
these libraaries themselves and then debug _them_.  normally, if my
program crashes inside libc, i'm not interested in knowing what i screwed
up that caused libc code to crush. the stack trace given using the debug
code _in my code_ suffices. in fact, it is quite very rare that i'll wish
for debug info in there.

> >      glibc-devel-2.0.7-19.i386.rpm
> 
> required only if you develop libs and C code based on them.

again, just like the above comment (besides, you're repeating the same
module twice?).

> >    glibc-profile-2.0.7-19.i386.rpm
> 
> required only if you're a C programmer and use gprof et al.

here i'm not completely sure (just cause i didn't try it), but as far as i
know, there's no need for profiling information inside libc in order to
profile one's program (please correct me if i'm wrong - i don't tend to
use profiles. i never did use any profiler, shame on me).

> > do i need to install glibc-debug-2.0.7-19.i386.rpm and
> > glibc-profile-2.0.7-19.i386.rpm or just the upgrade of the pakages that
> > i already got ?
> 
> In fact, some packages under Linux come with the -g option used in the
> makefiles for reasons that elude my (low) IQ, and these will fail to build
> if you don't install the 3 extra libs (profile, devel and debug).

NOT AT ALL. forgive me for shouting, but one does NOT need to have all the
libraries with debug info, neither all the object files of a program with
debug info. one only needs that in the part of the code they mean to
actually debug... thus, no program will fail to compile, debug info or
not.

>  Since
> you don't seem to know what the hell I'm talking about, install them too.

or actually - don't. you don't need them at all, you will probably never
miss them, unless you have intentions of developing or modifying the C
library itself. and when you'll get to a stage you will want that - you'll
always be able to install them. i'm sure they'll change many times before
you get to this stage in your "programming life".

peter - i do hope you wrote all this a ta late hour nigh, after not
sleeping for a few days? 

> > How the hell i canknow if they dont tell ?

i would *think* that that's what rpm files are for - if one of the
packages was required, rpm would tell you that. if you didn't have these
packages until now - you most likely don't need them from now on either.

hope this helps avoid the evil corruption peter was trying to lay upon
us ;),
guy