You are not logged in.
- Topics: Active | Unanswered
#1 2012-07-16 06:07:42
- earlz
- Member
- Registered: 2010-07-11
- Posts: 39
pacman -S glibc won't continue, conflict on `/lib/libiberty.a`?
Hello, I've been hit with the recent glibc update that broke a lot of systems. I'm almost done fixing mine, but I'm not sure how to resolve this.
For reference, this is what I've done so far.
Used the `find /lib -exec pacman -Qo -- {} +` to determine what to do.
I found /lib/gcc/x86_64-elf was unowned. I think this may have been from a freestanding cross compiler I built. I moved it to /usr/lib/gcc
I also updated the android-udev AUR package which had a file in /lib.
Now, I'm stuck on one final conflict. There is a /lib/libiberty.a file left over that is unowned. I would move it to /usr/lib, but a file by the same name already exists, but oddly they are different sizes.
Stats from each:
[root@EarlzZeta lib]# stat /usr/lib/libiberty.a
File: ‘/usr/lib/libiberty.a’
Size: 383554 Blocks: 752 IO Block: 4096 regular file
Device: 905h/2309d Inode: 183093 Links: 1
Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2012-07-07 15:16:08.000000000 +0000
Modify: 2012-07-04 00:23:36.000000000 +0000
Change: 2012-07-07 15:16:08.260683565 +0000
Birth: -
[root@EarlzZeta lib]# stat /lib/libiberty.a
File: ‘/lib/libiberty.a’
Size: 1456978 Blocks: 2848 IO Block: 4096 regular file
Device: 903h/2307d Inode: 2116497 Links: 1
Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2012-07-15 23:58:15.015310067 +0000
Modify: 2012-02-26 22:41:42.994452142 +0000
Change: 2012-02-26 22:41:43.004452143 +0000
Birth: -What could this have been installed by? Will it break anything to remove it? And how do I resolve this conflict?
Offline
#2 2012-07-16 06:14:32
- Allan
- Pacman
- From: Brisbane, AU
- Registered: 2007-06-09
- Posts: 11,672
- Website
Re: pacman -S glibc won't continue, conflict on `/lib/libiberty.a`?
That probably was installed with your cross compiler too. Get rid of it.
Offline