Summary: | fsck.reiser4 cant find libreiser4-1.0.so.2 --> booting abborted | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Carl Bach <crazy-b> |
Component: | [OLD] Core system | Assignee: | SpanKY <vapier> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | CC: | avuton, kenyon, motaboy, radek, xmit |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | reiser4progs-1.0.3_autoreconf.patch |
Description
Carl Bach
2004-12-18 02:49:51 UTC
I've got two machines that are unbootable, until I get a chance to run a livecd on them. Until this is fixed I think this package should definitely be masked. Thank you. what does `ldd /sbin/fsck.reiser4` show ? Strange. Everything seems to be correct. ldd /sbin/fsck.reiser4 linux-gate.so.1 => (0xffffe000) libreiser4-1.0.so.3 => /lib/libreiser4-1.0.so.3 (0xb7f8e000) librepair-1.0.so.3 => /lib/librepair-1.0.so.3 (0xb7f76000) libaal-1.0.so.3 => /lib/libaal-1.0.so.3 (0xb7f6e000) libuuid.so.1 => /lib/libuuid.so.1 (0xb7f6b000) libreadline.so.5 => /lib/libreadline.so.5 (0xb7f3d000) libncurses.so.5 => /lib/libncurses.so.5 (0xb7ef8000) libc.so.6 => /lib/libc.so.6 (0xb7dcd000) /lib/ld-linux.so.2 (0xb7fea000) so if you rm the libreiser4-1.0.so.2 symlink you made, does `fsck.resier4` work again ? Stragely, not! rm libreiser4-1.0.so.2 h0m3r lib # fsck.reiser4 fsck.reiser4: error while loading shared libraries: libreiser4-1.0.so.2: cannot open shared object file: No such file or directory ldd /sbin/fsck.reiser4 linux-gate.so.1 => (0xffffe000) libreiser4-1.0.so.3 => /lib/libreiser4-1.0.so.3 (0xb7f8e000) librepair-1.0.so.3 => /lib/librepair-1.0.so.3 (0xb7f76000) libaal-1.0.so.3 => /lib/libaal-1.0.so.3 (0xb7f6e000) libuuid.so.1 => /lib/libuuid.so.1 (0xb7f6b000) libreadline.so.5 => /lib/libreadline.so.5 (0xb7f3d000) libncurses.so.5 => /lib/libncurses.so.5 (0xb7ef8000) libc.so.6 => /lib/libc.so.6 (0xb7dcd000) /lib/ld-linux.so.2 (0xb7fea000) libreiser4-1.0.so.2 => not found There is a more proper solution than symlinking found here: http://forums.gentoo.org/viewtopic.php?t=268386 Just emerge reiser4progs a second time. Works now, even without the symlink :-) The problems is caused by librepair and other that links against the installed libreiser4 (libreiser4-1.0.so.2) instead of the just compiled one (libreiser4-1.0.so.3). # ldd /lib/librepair.so linux-gate.so.1 => (0xffffe000) libreiser4-1.0.so.2 => not found <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< libc.so.6 => /lib/libc.so.6 (0xb7ea9000) /lib/ld-linux.so.2 (0x80000000) Using "elibtoolize" inside src_unpack DIDN'T fixed it. So I forced the regeneration of all the build system running "autoreconf --install --force", and then it worked. vapier: I'm not very libtool expert so I don't know if this is the right solution to this problem. I just tried to help you :D. Created attachment 46530 [details, diff]
reiser4progs-1.0.3_autoreconf.patch
Why is the fix not in reiser4progs 1.0.4 ? I had the same problem when upadating to reiser4progs 1.0.4. FWIW, I've just had the same problem upgrading to libreiser4-1.0.4 as well. I confirm that this is still not fixed. Sorry to bother you all with the e-mail notification. I didn't know it would send you all an e-mail. x_x thanks Simone for that ... forced rebuilding of autotools in src_unpack() |