Mga7.1, recently installed.d84926052d4256c3fffe1d75b31e5b8bd73051 -> ../../../../usr/lib64/libakregatorinterfaces.so.5.11.0
There is a directory
/usr/lib/.build-id, which has 256 subdirecties (all of the hex numbers
from 00 to ff) and each of which has on average 40 links. The links are
36 hex numbers long and point to a whole variety of files in the
filesystem.
eg
lrwxrwxrwx 1 root root 54 Apr 16 14:29
just to pick a random one.
This takes up 9MB of space which means about 1K for each link.
Installed from the Mageia 7.1 installation DVD
Can I erase them? And why are they there?
On Thu, 29 Aug 2019 05:24:07 -0000 (UTC), William Unruh wrote:
Mga7.1, recently installed.
There is a directory
/usr/lib/.build-id, which has 256 subdirecties (all of the hex numbers
from 00 to ff) and each of which has on average 40 links. The links are
36 hex numbers long and point to a whole variety of files in the
filesystem.
eg
lrwxrwxrwx 1 root root 54 Apr 16 14:29 d84926052d4256c3fffe1d75b31e5b8bd73051 -> ../../../../usr/lib64/libakregatorinterfaces.so.5.11.0
just to pick a random one.
This takes up 9MB of space which means about 1K for each link.
Installed from the Mageia 7.1 installation DVD
Can I erase them? And why are they there?
For help in debugging a problem. Take a look at https://bugs.mageia.org/show_bug.cgi?id=24654
I have opened several bug reports about missing build-id files. Response
on mageia dev discussion list suggested not a real problem so I modified
my install scripts to ignore any problems with them.
Mga7.1, recently installed.d84926052d4256c3fffe1d75b31e5b8bd73051 -> ../../../../usr/lib64/libakregatorinterfaces.so.5.11.0
There is a directory
/usr/lib/.build-id, which has 256 subdirecties (all of the hex numbers
from 00 to ff) and each of which has on average 40 links. The links are
36 hex numbers long and point to a whole variety of files in the
filesystem.
eg
lrwxrwxrwx 1 root root 54 Apr 16 14:29
just to pick a random one.
This takes up 9MB of space which means about 1K for each link.
Installed from the Mageia 7.1 installation DVD
Can I erase them? And why are they there?
On Thu, 29 Aug 2019 01:24:07 -0400, William Unruh <unruh@invalid.ca> wrote:
Mga7.1, recently installed.
There is a directory
/usr/lib/.build-id, which has 256 subdirecties (all of the hex numbers
from 00 to ff) and each of which has on average 40 links. The links are
36 hex numbers long and point to a whole variety of files in the
filesystem.
eg
lrwxrwxrwx 1 root root 54 Apr 16 14:29 d84926052d4256c3fffe1d75b31e5b8bd73051 -> ../../../../usr/lib64/libakregatorinterfaces.so.5.11.0
just to pick a random one.
This takes up 9MB of space which means about 1K for each link.
Installed from the Mageia 7.1 installation DVD
Can I erase them? And why are they there?
It doesn't take that much space. It's just a symlink. The 9MB of space
is the space used by the library module it links to.
As to what it's for, from https://pagure.io/jss/issue/8 ...us to link the debuginfo package to the library, and make magic happen with gdb if we ever need to step through the program with gdb."
"These come about as a result of the compiled library, libjss4.so, and allow
On my m7 x86_64 install, with all of the desktop environments installed,
that directory tree has 11933 symlinks. "du -s" shows that is taking
a total of 11M of space.
It's safe to remove them, but if you do you will not be able to run gdb,
if asked to by a packager trying to figure out why some package segfaults
on your system, but not on theirs.
Regards, Dave Hodgins
On Thu, 29 Aug 2019 01:24:07 -0400, William Unruh <unruh@invalid.ca> wrote:us to link the debuginfo package to the library, and make magic happen with gdb if we ever need to step through the program with gdb."
Mga7.1, recently installed.
There is a directory
/usr/lib/.build-id, which has 256 subdirecties (all of the hex numbers
from 00 to ff) and each of which has on average 40 links. The links are
36 hex numbers long and point to a whole variety of files in the
filesystem.
eg
lrwxrwxrwx 1 root root 54 Apr 16 14:29 d84926052d4256c3fffe1d75b31e5b8bd73051 -> ../../../../usr/lib64/libakregatorinterfaces.so.5.11.0
just to pick a random one.
This takes up 9MB of space which means about 1K for each link.
Installed from the Mageia 7.1 installation DVD
Can I erase them? And why are they there?
It doesn't take that much space. It's just a symlink. The 9MB of space
is the space used by the library module it links to.
As to what it's for, from https://pagure.io/jss/issue/8 ...
"These come about as a result of the compiled library, libjss4.so, and allow
On my m7 x86_64 install, with all of the desktop environments installed,
that directory tree has 11933 symlinks. "du -s" shows that is taking
a total of 11M of space.
It's safe to remove them, but if you do you will not be able to run gdb,
if asked to by a packager trying to figure out why some package segfaults
on your system, but not on theirs.
Regards, Dave Hodgins
Also, on my Mga6 and Mga5 machines, the directory does not exist or in onecase
has 3 links in it. This is something new that has been introduced into
Mga7. From your descirption it seems that in compiling Mga7 some
debugging flag was switched on for all programs. Why?
While this might have been useful for cauldron, it seems pretty useless
for the distro, and takes up 9MB of space (and I do not know how much
extra space that debugging flag causes each program to occupy. Yes, I
know disk space is "cheap" but that does not seem a good reason to waste
it for no purpose.
On 2019-08-29, David W. Hodgins <dwhodgins@nomail.afraid.org> wrote:
On Thu, 29 Aug 2019 01:24:07 -0400, William Unruh <unruh@invalid.ca> wrote: >>
Mga7.1, recently installed.
There is a directory
/usr/lib/.build-id, which has 256 subdirecties (all of the hex numbers
from 00 to ff) and each of which has on average 40 links. The links are
36 hex numbers long and point to a whole variety of files in the
filesystem.
eg
lrwxrwxrwx 1 root root 54 Apr 16 14:29 d84926052d4256c3fffe1d75b31e5b8bd73051 -> ../../../../usr/lib64/libakregatorinterfaces.so.5.11.0
just to pick a random one.
This takes up 9MB of space which means about 1K for each link.
Installed from the Mageia 7.1 installation DVD
Can I erase them? And why are they there?
It doesn't take that much space. It's just a symlink. The 9MB of space
is the space used by the library module it links to.
As to what it's for, from https://pagure.io/jss/issue/8 ...
"These come about as a result of the compiled library, libjss4.so, and allow us to link the debuginfo package to the library, and make magic happen with gdb if we ever need to step through the program with gdb."
On my m7 x86_64 install, with all of the desktop environments installed,
that directory tree has 11933 symlinks. "du -s" shows that is taking
a total of 11M of space.
It's safe to remove them, but if you do you will not be able to run gdb,
if asked to by a packager trying to figure out why some package segfaults
on your system, but not on theirs.
Regards, Dave Hodgins
I have just been thinking about this a bit more, and am even more(or the builder)
confused. This build-id is a constant for any distro release. Ie, "Mageia"
has this information. It is not something that is actually useful to the user. It is a way to identify which program a given gdb dump comes from.that file
A) almost no users every use gdb on their installed systems.
B) It is completely redundant, since every users build-id links are the
same from a given installation. So that is 9MB of completely wasted disk space.
Now, if that table of association of build-id to program were in a file,
would take up less than 1MB.
On Thu, 29 Aug 2019 14:38:33 -0000 (UTC), William Unruh wrote:changes.
I have just been thinking about this a bit more, and am even more
confused. This build-id is a constant for any distro release. Ie, "Mageia" (or the builder)
has this information. It is not something that is actually useful to the
user. It is a way to identify which program a given gdb dump comes from.
A) almost no users every use gdb on their installed systems.
B) It is completely redundant, since every users build-id links are the
same from a given installation. So that is 9MB of completely wasted disk
space.
Now, if that table of association of build-id to program were in a file, that file
would take up less than 1MB.
Your "supposed" solution is unsupportable as stated.
Build ids are not the same for a distro release.
Fact, build id is unique to the file on the system. I would assume all packages would require modification to support your proposal, and gdb
would require modification to use the build id file.
Any further discussion of the topic is a waste of time because the
Mageia support group does not have the resource/people power to make those
Ie, the build-id is in the package . It is not something that is
calculated on my machine. It is calculated by the packager. Thus, anyone
who uses the same distro set that I use has the same build-id.
The changes were "foisted" on us by the Redhat team in 2008. Mageia did
not have the /usr/lib/.build-id directory until Mageia 7 (2019)
Ie, in the past Mageia did not use the .build-id package, suddenly now
they do. This was a Mageia decision it seems.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 296 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 78:42:52 |
| Calls: | 6,658 |
| Calls today: | 4 |
| Files: | 12,203 |
| Messages: | 5,332,979 |
| Posted today: | 1 |