On 3/29/19, Daniel Schepler via lfs-dev <lfs-dev@lists.linuxfromscratch.org> wrote: > On Fri, Mar 29, 2019 at 9:00 AM Bruce Dubbs via lfs-dev > <lfs-dev@lists.linuxfromscratch.org> wrote: >> Just for comparison, Arch does not create .dbg files and does not use >> --enable-gnu-build-id. >> >> https://git.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/glibc > > On further examination, it looks like the actual gcc configure flag is > --enable-linker-build-id. And I do see that being activated. > > https://git.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/gcc > > I can't answer to the question of creating .dbg files. > -- > Daniel Schepler
I'm out of my league here, but I'm stepping out on that very thin limb (again) because you mentioned "dbg". I had already been attempting some more self-education with previous knowledge of existing "-dbg" archives in mind as I searched around. In response to the currently very last post in this LFS thread, I just found the following about generating dbg packages as written by a self-described "student": https://people.debian.org/~osamu/fun2prog.html#_detached_debugging_symbols Found a few other things while searching around to see if I was at least partially understanding your conversation here. That was well-spent time because I've installed "-dbg" files that were "Suggested" packages, just never had a usage case to actually work with them to know their importance. I just tried a Debian "apt-cache search dbg" and received back a HUGE list in response. Most end in that "-dbg" and then several end with "-dev". When "gcc" is included in that search (solely because it's mentioned in this thread), "libgcc1-dbg" popped up with an extremely short description: "Description-en: GCC support library (debug symbols) Debug symbols for the GCC support library." In trying to further self-educate about your current discussion, I next tried an Internet search for "debian install package debugging information". From Debian: AutomaticDebugPackages (presents itself as tl;dr version).. https://wiki.debian.org/AutomaticDebugPackages My initial grasp is that at least some find community available "-dbg" files to be underused and overly mirrored thus wasting precious volunteer mirror disk space. Additionally, it is suggested that necessary *manual* attention to separate dbg packages' existences is a potential or real waste of time and resources. Ubuntu pulled up separately for that same Internet search... https://wiki.ubuntu.com/Debug%20Symbol%20Packages I next tried the originally proffered "enable-gnu-build-id". That search suggested "enabled-gnu-build-id" which did NOT work. In fact, neither did, and I now see that's been updated. On a whim, though, I used just "gnu-build-id" which brought up Redhat in with others sounding possibly at least slightly on topic. If I'm completely off-track, my apologies. That reference to .dbg packages empowered me to go ahead and poke my nose in. Maybe something in the above will help one way or the other since there are more than a few references to dbg packages and debugging. :) Cindy :) * going back into lurk-n-learn mode * -- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
