[arch-general] ld-2.11.1.so and segfaults
christopher floess
skeptikos at gmail.com
Fri Feb 26 14:43:16 EST 2010
On 02/26/2010 01:00 PM, Damjan Georgievski wrote:
>> I'm out of ideas too, because they still segfault. Crap.
>>
>> I guess I could reinstall the system, but doesn't seem like the way to go
>> here. I have X working with wmii. I just have nasty looking window
>> decorations and random productivity Applications that don't work.
>>
>> Is there a way to de-install everything that's NOT in base? I looked around
>> for this, and will I could certainly create a command line chain for it
>> something like "pacman -R --all !base" would be nice
>>
> the "file" command will tell you if a binary is 32bit or 64bit, so go
> in /lib/ /usr/lib/ /usr/bin etc and do a
>
> file * | grep '32-bit'
>
> or a bit more robust
>
> find /usr/lib/ -print0 | xargs -0 file | grep '32-bit'
>
Since it's a pretty short list, here's the output
/usr/lib/syslinux/vpdtest.c32:
COM executable (32-bit COMBOOT)
/usr/lib/syslinux/elf.c32:
COM executable (32-bit COMBOOT)
/usr/lib/syslinux/kbdmap.c32:
COM executable (32-bit COMBOOT)
/usr/lib/syslinux/rosh.c32:
COM executable (32-bit COMBOOT)
/usr/lib/syslinux/ethersel.c32:
COM executable (32-bit COMBOOT)
/usr/lib/syslinux/config.c32:
COM executable (32-bit COMBOOT)
/usr/lib/syslinux/ifcpu.c32:
COM executable (32-bit COMBOOT)
/usr/lib/syslinux/cpuidtest.c32:
COM executable (32-bit COMBOOT)
/usr/lib/syslinux/gpxecmd.c32:
COM executable (32-bit COMBOOT)
/usr/lib/syslinux/chain.c32:
COM executable (32-bit COMBOOT)
/usr/lib/syslinux/mboot.c32:
COM executable (32-bit COMBOOT)
/usr/lib/syslinux/linux.c32:
COM executable (32-bit COMBOOT)
/usr/lib/syslinux/reboot.c32:
COM executable (32-bit COMBOOT)
/usr/lib/syslinux/sdi.c32:
COM executable (32-bit COMBOOT)
/usr/lib/syslinux/hdt.c32:
COM executable (32-bit COMBOOT)
/usr/lib/syslinux/vesainfo.c32:
COM executable (32-bit COMBOOT)
/usr/lib/syslinux/disk.c32:
COM executable (32-bit COMBOOT)
/usr/lib/syslinux/dmitest.c32:
COM executable (32-bit COMBOOT)
/usr/lib/syslinux/pmload.c32:
COM executable (32-bit COMBOOT)
/usr/lib/syslinux/cmd.c32:
COM executable (32-bit COMBOOT)
/usr/lib/syslinux/gfxboot.c32:
COM executable (32-bit COMBOOT)
/usr/lib/syslinux/ifcpu64.c32:
COM executable (32-bit COMBOOT)
/usr/lib/syslinux/vesamenu.c32:
COM executable (32-bit COMBOOT)
/usr/lib/syslinux/menu.c32:
COM executable (32-bit COMBOOT)
/usr/lib/syslinux/sanboot.c32:
COM executable (32-bit COMBOOT)
/usr/lib/syslinux/meminfo.c32:
COM executable (32-bit COMBOOT)
/usr/lib/syslinux/pcitest.c32:
COM executable (32-bit COMBOOT)
/usr/lib/mono/gac/avahi-sharp/1.0.0.0__4d116c78973743f5/avahi-sharp.dll:
PE32 executable for MS Windows (DLL) (console) Intel 80386 32-bit
Mono/.Net assembly
/usr/lib/mono/gac/avahi-ui-sharp/0.0.0.0__4d116c78973743f5/avahi-ui-sharp.dll:
PE32 executable for MS Windows (DLL) (console) Intel 80386 32-bit
Mono/.Net assembly
/usr/lib/mono/gac/gmime-sharp/2.4.0.0__2b75c2ad004c52e4/gmime-sharp.dll:
PE32 executable for MS Windows (DLL) (console) Intel 80386 32-bit
Mono/.Net assembly
/usr/lib/opera/10.10/operapluginwrapper-ia32-linux:
ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically
linked (uses shared libs), for GNU/Linux 2.6.8, stripped
/usr/lib/python2.6/site-packages/setuptools/gui.exe:
PE32 executable for MS Windows (GUI) Intel 80386 32-bit
/usr/lib/python2.6/site-packages/setuptools/cli.exe:
PE32 executable for MS Windows (console) Intel 80386 32-bit
/usr/lib/python2.6/distutils/command/wininst-7.1.exe: PE32
executable for MS Windows (GUI) Intel 80386 32-bit
/usr/lib/python2.6/distutils/command/wininst-8.0.exe: PE32
executable for MS Windows (GUI) Intel 80386 32-bit
/usr/lib/python2.6/distutils/command/wininst-9.0.exe: PE32
executable for MS Windows (GUI) Intel 80386 32-bit
/usr/lib/python2.6/distutils/command/wininst-6.0.exe: PE32
executable for MS Windows (GUI) Intel 80386 32-bit
Maybe it's just my untrained eye, but things don't seem to be out of the
ordinary here. /lib didn't show anything 32-bit.
At this point, if I could be fairly certain that a reinstall would work,
I'd try that. I'm just afraid that it won't produce anything. It
couldn't possibly have to do with the fact that my boot loader is the
grub from the 32-bit install, could it?
-- Chris
More information about the arch-general
mailing list