I used to build bzip2 with USE=static. Since this morning, I get: [07:48:40 alexander@server:~] $ ll /bin/bzip2 -rwxr-xr-x 1 root root 494048 13. Mai 18:27 /bin/bzip2 [07:48:45 alexander@server:~] $ file /bin/bzip2 /bin/bzip2: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.4.1, dynamically linked (uses shared libs), stripped [07:48:51 alexander@server:~] $ /bin/bzip2 bash: /bin/bzip2: No such file or directory [07:48:59 alexander@server:~] $ ldd /bin/bzip2 /usr/bin/ldd: line 124: /bin/bzip2: No such file or directory [07:49:01 alexander@server:~] $ LC_ALL=C wc /bin/bzip2 1616 14833 494048 /bin/bzip2 [07:51:30 alexander@server:/etc] $ cp -av /bin/bzip2 /tmp `/bin/bzip2' -> `/tmp/bzip2' [07:51:43 alexander@server:/etc] $ ls -la /tmp/bzip2 -rwxr-xr-x 1 alexander alexander 494048 May 13 18:27 /tmp/bzip2 [07:51:47 alexander@server:/etc] $ md5sum /bin/bzip2 /tmp/bzip2 e6fd9d79e28a34578ea3d9f6a4f9566a /bin/bzip2 e6fd9d79e28a34578ea3d9f6a4f9566a /tmp/bzip2 [07:51:52 alexander@server:/etc] $ /tmp/bzip2 bash: /tmp/bzip2: No such file or directory [07:51:56 alexander@server:/etc] $ After building bzip2 with USE=-static, I can exec bzip2. Why's that?
I just noticed another strange thing: [07:48:45 alexander@server:~] $ file /bin/bzip2 /bin/bzip2: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.4.1, dynamically linked (uses shared libs), stripped Why is "file" listing /bin/bzip2 as "dynamically linked (uses shared libs)", after doing "USE=static emerge bzip2"?
fixed in 1.0.3-r2
