| Summary: | libsandbox.so gettting linked in to some applications? | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Daniel Robbins (RETIRED) <drobbins> |
| Component: | Unclassified | Assignee: | Geert Bevin <gbevin> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
this is normal and is not really a bug. |
I just created a new nvclock ebuild using portage 1.8.4 (which includes the sandbox). When I type "ldd nvclock": # ldd /usr/bin/nvclock /usr/lib/portage/lib/libsandbox.so => /usr/lib/portage/lib/libsandbox.so (0x40018000) libgtk-1.2.so.0 => /usr/lib/libgtk-1.2.so.0 (0x40028000) libgdk-1.2.so.0 => /usr/lib/libgdk-1.2.so.0 (0x40117000) libgmodule-1.2.so.0 => /usr/lib/libgmodule-1.2.so.0 (0x40149000) libglib-1.2.so.0 => /usr/lib/libglib-1.2.so.0 (0x4014c000) libdl.so.2 => /lib/libdl.so.2 (0x40172000) libXi.so.6 => /usr/X11R6/lib/libXi.so.6 (0x40176000) libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x4017e000) libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x4018d000) libm.so.6 => /lib/libm.so.6 (0x40277000) libc.so.6 => /lib/libc.so.6 (0x4029b000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000) Notice that libsandbox.so is linked in. I'm guessing that this is a bug?