Hello all--
Due to a proposed changeover to build machines for a project I'm involved with, I need at least glib 2.19. Right now I have glib 2.12, and even on CentOS7-32 bit, what I see is glib 2.14. Is a higher glib available anywhere that might work with my current 6.8. I see I can download it from SourceForge but I am wondering what the results might me.
I really like CentOS and would hate to change distros at this point, but, well, it might come to that. :(
Any advice truly appreciated.
On 8/24/2016 4:22 PM, Kay Schenk wrote:
Due to a proposed changeover to build machines for a project I'm involved with, I need at least glib 2.19. Right now I have glib 2.12, and even on CentOS7-32 bit, what I see is glib 2.14. Is a higher glib available anywhere that might work with my current 6.8. I see I can download it from SourceForge but I am wondering what the results might me.
whats the target OS for the builds from these build machines ?
to change the default libc would require rebuilding (and retesting) the whole OS.
On Thu, Aug 25, 2016 at 9:44 AM, John R Pierce pierce@hogranch.com wrote:
On 8/24/2016 4:22 PM, Kay Schenk wrote:
Due to a proposed changeover to build machines for a project I'm involved with, I need at least glib 2.19. Right now I have glib 2.12, and even on CentOS7-32 bit, what I see is glib 2.14. Is a higher glib available anywhere that might work with my current 6.8. I see I can download it from SourceForge but I am wondering what the results might me.
whats the target OS for the builds from these build machines ?
to change the default libc would require rebuilding (and retesting) the whole OS.
I believe glib is just the Gnome utility libraries, unlike glibc which has the core C runtime libraries. Upgrading glib is probably less dire, though it
On 08/24/2016 04:22 PM, Kay Schenk wrote:
Due to a proposed changeover to build machines for a project I'm involved with, I need at least glib 2.19.
Do you know why? As in, what features or fixes are required? If not, I 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 LSB release (none of which, as far as I can tell, require glibc 2.19+).
Right now I have glib 2.12, and even on CentOS7-32 bit, what I see is glib 2.14.
CentOS 7 is built on glibc 2.17.
Also, minor correction: "glib" is the name of a different library than glibc.
On Aug 24, 2016 5:05 PM, "Gordon Messmer" gordon.messmer@gmail.com wrote:
On 08/24/2016 04:22 PM, Kay Schenk wrote:
Due to a proposed changeover to build machines for a project I'm involved with, I need at least glib 2.19.
Do you know why? As in, what features or fixes are required? If not, I
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 LSB release (none of which, as far as I can tell, require glibc 2.19+).
To all...yes 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, I need to be able to test and use the builds. We'll be moving to a Ubuntu 14 environment, 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 I needed and just install it without overwriting my setup. Then set an env variable to run the generated build.
Thanks for the responses.
Right now I have glib 2.12, and even on CentOS7-32 bit, what I see is glib 2.14.
CentOS 7 is built on glibc 2.17.
Also, minor correction: "glib" is the name of a different library than
glibc.
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
On 25/08/16 13:21, Kay Schenk wrote:
To all...yes 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, I need to be able to test and use the builds. We'll be moving to a Ubuntu 14 environment, 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.
Well, at the end of the day, if you're trying to build for multiple environments then you really need to build to the lowest common denominator. What you seem to want is just the opposite, so short story is that it's bad planning to build to such a new version of glibc. You're not going to get around this, it just won't work.
Peter
On 08/24/2016 07:53 PM, Peter wrote:
On 25/08/16 13:21, Kay Schenk wrote:
To all...yes 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, I need to be able to test and use the builds. We'll be moving to a Ubuntu 14 environment, 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.
Well, at the end of the day, if you're trying to build for multiple environments then you really need to build to the lowest common denominator. What you seem to want is just the opposite, so short story is that it's bad planning to build to such a new version of glibc. You're not going to get around this, it just won't work.
Peter
Copy that. I do realize the sane thing to do is to have the builbots -- smoketest environments -- match the production environment, which currently is spec'd at CentOS 5.x. Unfortunately, I don't have direct control over some of this. <sigh>
On 08/25/2016 09:49 AM, Kay Schenk wrote:
I do realize the sane thing to do is to have the builbots -- smoketest environments -- match the production environment
I think the sane thing to do would be to use buildbots that support LSB:
Am 25.08.2016 um 19:44 schrieb Gordon Messmer:
On 08/25/2016 09:49 AM, Kay Schenk wrote:
I do realize the sane thing to do is to have the builbots -- smoketest environments -- match the production environment
I think the sane thing to do would be to use buildbots that support LSB:
These days you would use container technology to achieve that, docker i.e., with fitting images.
Alexander
On 08/25/2016 10:44 AM, Gordon Messmer wrote:
On 08/25/2016 09:49 AM, Kay Schenk wrote:
I do realize the sane thing to do is to have the builbots -- smoketest environments -- match the production environment
I think the sane thing to do would be to use buildbots that support LSB:
Great resource! Thanks...
On 26/08/16 06:18, Kay Schenk wrote:
On 08/25/2016 09:49 AM, Kay Schenk wrote:
I do realize the sane thing to do is to have the builbots -- smoketest environments -- match the production environment
I think the sane thing to do would be to use buildbots that support LSB:
Great resource! Thanks...
mock is available for ubuntu:
https://launchpad.net/ubuntu/+source/mock
Using that you can target various different rpm plaforms properly without requiring a different build host for each.
This is what many (if not most) projects use to build for CentOS.
Peter
On 08/25/2016 06:26 PM, Peter wrote:
On 26/08/16 06:18, Kay Schenk wrote:
On 08/25/2016 09:49 AM, Kay Schenk wrote:
I do realize the sane thing to do is to have the builbots -- smoketest environments -- match the production environment
I think the sane thing to do would be to use buildbots that support LSB:
Great resource! Thanks...
mock is available for ubuntu:
https://launchpad.net/ubuntu/+source/mock
Using that you can target various different rpm plaforms properly without requiring a different build host for each.
This is what many (if not most) projects use to build for CentOS.
Peter
Thanks again. These build systems are not under my project's direct control, so ???
On 8/26/2016 9:28 AM, Kay Schenk wrote:
Thanks again. These build systems are not under my project's direct control, so ???
so what target environments are these build environments currently used for? thats pretty much what you're going to get.
On 08/24/2016 08:21 PM, Kay Schenk wrote: <<<>>>
We'll be moving to a Ubuntu 14 environment, 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.
answer to you problem is in your reply.
install ubuntu 14 to a system and build with it.
have you not heard the adage, 'you can not get blood from a turnip'?
-
Alexander Dalloz -
geo.inbox.ignored -
Gordon Messmer -
John R Pierce -
Kahlil Hodgson -
Kay Schenk -
Peter