Think John’s question is pertinent. If you’re building a binaries to distribute, your best bet might actually be to produce multiple builds targeting specific Linux distributions.
![]()
Alternately, some specific LSBrelease (none of which, as far as I can tell, require glibc 2.19+).To allyes I meant glibc, not glib. Target environment — could be any version of Linux. This is for Apache OpenOffice. The buildbots we’ve been using are being decommisioned due to EOL.
![]()
As a developer on that project, Ineed to be able to test and use the builds. We’ll be moving to a Ubuntu 14environment, which is spec’d at glibc 2.19 near as I can determine. So a long story. We will not be building for targeted environments.Write after I wrote this, I thought maybe I could get a zip of what Ineeded and just install it without overwriting my setup. Then set an env variable to run the generated build.Thanks for the responses.glibc.
# cat /etc/redhat-release CentOS release 6.5 (Final) 2.安装系统库 # yum install -y glibc glibc-common glibc-devel glibc-headers glibc-static glibc-utils # yum install -y gcc # yum install -y gawk 3.查看未升级前系统glibc库版本. Download libc.so.6(GLIBC2.18) packages for ALTLinux, Fedora, Mageia, OpenMandriva, openSUSE, PCLinuxOS, ROSA.
Comments are closed.
|
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |