Re: About upgrading to glibc-2.40
| Newsgroups | gmane.linux.lfs.support |
|---|---|
| Message-ID | <[email protected]> |
On 1/5/25 11:00 AM, Pierre Labastie ([email protected] via lfs-support Mailing List) wrote: > Le dimanche 05 janvier 2025 à 10:18 +0100, tjoen a écrit : .. >> Failed twice upgrading glibc with RPM >> I came with a new idea: >> >> 1. add in %pre >> rpm -e --justdb --nodeps glibc >> 2. add in %install >> cd $RPM_BUILD_ROOT/ >> mkdir usr/lib64/glibc >> mv lib64/*.so.* usr/lib64/glibc/ >> 3. add in %post >> install /usr/lib64/glibc/*.so.* /lib64/ >> >> (/lib64 is a symlink to /usr/lib64) >> >> Would that work? > > I don't know much of rpm, especially when in the build/install process > %pre, %install, and %post are run. > > So I assume %pre is the configure step, %install is a DESTDIR install, > and %post is run after the package has been installed onto the system. tldp.org/HOWTO/RPM-HOWTO/index.html %pre is the macro to do pre-install scripts. > If so, it should work, although I am not sure why you need to rpm -e > the db (maybe to prevent erasing existing files when installing the > package onto the system?). That is what I hoped. If erased in the db then the original files would not be deleted -- http://lists.linuxfromscratch.org/sympa/info/lfs-support Unsubscribe: See the above information page