[arch-ports] [arch64] glibc/gcc update in testing
well, i still don't have access to a testing repo on archlinux.org. so i use the old one from arch64.org for testing this major upgrade. http://arch64.org/packages/testing/ bin86 binutils gcc glibc kernel-headers libstdc++5 Most important change: we move our libs from /lib64 and /usr/lib64 to /lib and /usr/lib. We also remove the old symlinks. It was really tricky to get pacman do this update. I have tested as much as possible and at least it worked well here on my system. But be warned: if the update fails you will probably loose the ability to make a rollback. Without a working glibc you can only load static binaries. So i suggest to leave open a root instance of "mc" and Gaim/Xchat. When the Update fails use "mc" to copy or rename the lib path to lib64 and create the old symlinks. So watch the structure carefully before updating. If anybody wants to see the pkgbuilds or *.install files let me know. So good luck to everybody. Hope to get positive reports so we can soon move the updates together with arch32 to current. AndyRTR
Hi, seems to work so far. But why is this: [pierre@athlon64 ~]$ pacman -Qo /lib64/* /lib64/ld-2.4.so is owned by glibc 2.4-2 /lib64/ld-linux-x86-64.so.2 is owned by glibc 2.4-2 Will everything be rebuild with new gcc? And btw. mc does not work: [pierre@athlon64 ~]$ mc mc: error while loading shared libraries: libslang.so.2: cannot open shared object file: No such file or directory Greetings Pierre Am Mittwoch, 7. Juni 2006 20:03 schrieb Andreas Radke:
well, i still don't have access to a testing repo on archlinux.org. so i use the old one from arch64.org for testing this major upgrade.
http://arch64.org/packages/testing/
bin86 binutils gcc glibc kernel-headers libstdc++5
Most important change: we move our libs from /lib64 and /usr/lib64 to /lib and /usr/lib. We also remove the old symlinks.
It was really tricky to get pacman do this update.
I have tested as much as possible and at least it worked well here on my system. But be warned: if the update fails you will probably loose the ability to make a rollback. Without a working glibc you can only load static binaries.
So i suggest to leave open a root instance of "mc" and Gaim/Xchat. When the Update fails use "mc" to copy or rename the lib path to lib64 and create the old symlinks. So watch the structure carefully before updating.
If anybody wants to see the pkgbuilds or *.install files let me know.
So good luck to everybody. Hope to get positive reports so we can soon move the updates together with arch32 to current.
AndyRTR
_______________________________________________ arch-ports mailing list arch-ports@archlinux.org http://www.archlinux.org/mailman/listinfo/arch-ports
On Wed, 2006-06-07 at 22:19 +0200, Pierre Schmitz wrote:
seems to work so far. But why is this:
[pierre@athlon64 ~]$ pacman -Qo /lib64/* /lib64/ld-2.4.so is owned by glibc 2.4-2 /lib64/ld-linux-x86-64.so.2 is owned by glibc 2.4-2
that's because the main linker is looked for in /lib64. When a program links to it in /lib64, it will link the rest of the libraries from /lib. Programs that don't have /lib defined in the rpath will fail to run because they can't find the linker.
we will soon start to build all the updates. post broken packages after the glibc update that are not in arch32 testing(!) here so we know what to rebuild. AndyRTR
participants (3)
-
Andreas Radke
-
Jan de Groot
-
Pierre Schmitz