Building and installing a new version of GLIBC on CentOS

Building and installing a new version of GLIBC on CentOS

[Ian Trudel]

My system requires a newer version of GLIBC and I had a partial success so
far. Building 64 bit works without a hitch; the installation failed to
complete but I suspect it is because of the older 32 bit libm.so.

Unfortunately, building a 32 bit version fails early. I searched around on
the web to find the proper way to build GLIBC version 2.29 for 32 bit but
nothing worked.

Having an old 32 bit and a new 64 bit libraries mess up the locale, e.g.
utf-8 vs utf8, and even prevent some apps to start.

I truly need a full replacement. Installing GLIBC in /opt would not work
due to my system requirements.

Anyone would be so kind to help me? :)


Ian.

Re: Building and installing a new version of GLIBC on CentOS

[Carlos O'Donell]

On 7/18/19 11:56 PM, Ian Trudel wrote:
> My system requires a newer version of GLIBC and I had a partial success so
> far. Building 64 bit works without a hitch; the installation failed to
> complete but I suspect it is because of the older 32 bit libm.so.
> 
> Unfortunately, building a 32 bit version fails early. I searched around on
> the web to find the proper way to build GLIBC version 2.29 for 32 bit but
> nothing worked.
> 
> Having an old 32 bit and a new 64 bit libraries mess up the locale, e.g.
> utf-8 vs utf8, and even prevent some apps to start.
> 
> I truly need a full replacement. Installing GLIBC in /opt would not work
> due to my system requirements.
> 
> Anyone would be so kind to help me? :)

I would not recommend upgrading your system glibc. It requires expert
level knowledge not to break your system.

Can you run your application in a container with a distribution that it
was intended to work with?

-- 
Cheers,
Carlos.

Re: Building and installing a new version of GLIBC on CentOS

[Florian Weimer]

* Ian Trudel:

> My system requires a newer version of GLIBC and I had a partial success so
> far. Building 64 bit works without a hitch; the installation failed to
> complete but I suspect it is because of the older 32 bit libm.so.
>
> Unfortunately, building a 32 bit version fails early. I searched around on
> the web to find the proper way to build GLIBC version 2.29 for 32 bit but
> nothing worked.

Do you use rpmbuild?

Thanks,
Florian

Re: Building and installing a new version of GLIBC on CentOS

[Ian Trudel]

Here is the solution to build the 32 bit version of glibc on CentOS:

../../configure --prefix=/usr --disable-profile --enable-add-ons
--with-headers=/usr/include --with-binutils=/usr/bin
--build=x86_64-x32-linux-gnu --host=i686-pc-linux-gnu CC="gcc -m32"
CXX="g++ -m32" CFLAGS="-O2 -march=i686" CXXFLAGS="-O2 -march=i686"

The build and host switches have to be different for some strange reason.

Thank you for your help Florian and Carlos.

Best regards,
Ian

Le ven. 19 juill. 2019, à 02 h 47, Florian Weimer <fweimer@redhat.com> a
écrit :

> * Ian Trudel:
>
> > On Fri, Jul 19, 2019, 1:50 AM Florian Weimer <fweimer@redhat.com> wrote:
> >
> >  * Ian Trudel:
> >
> >  >  Do you use rpmbuild?
> >  >
> >  > It's installed on my system. I've used it a few times. What are you
> >  > thinking about?
> >
> >  Do you use rpmbuild to rebuild glibc, perhaps indirectly through mock?
> >
> > I used the source code provided directly from glibc project page. The
> > 64 bit version compile just fine and worked with the programs that
> > need it. The problem is compiling the 32 bit version.
>
> You will have to install the 32-bit development libraries
> (glibc-devel.i686, libgcc.i686).  Please post the actual error messages
> to the mailing list.
>
> Thanks,
> Florian
>

Re: Building and installing a new version of GLIBC on CentOS

[Florian Weimer]

* Ian Trudel:

> Here is the solution to build the 32 bit version of glibc on CentOS:
>
> ../../configure --prefix=/usr --disable-profile --enable-add-ons --with-headers=/usr/include --with-binutils=/usr/bin
> --build=x86_64-x32-linux-gnu --host=i686-pc-linux-gnu CC="gcc -m32" CXX="g++ -m32" CFLAGS="-O2 -march=i686"
> CXXFLAGS="-O2 -march=i686"
>
> The build and host switches have to be different for some strange reason.

--build=x86_64-x32-linux-gnu seems wrong.

  CC="gcc -m32" CXX="g++ -m32" --build=i686-linux-gnu

works for me, with a sufficiently recent gcc and g++ on the path.

Thanks,
Florian

Re: Building and installing a new version of GLIBC on CentOS

[Ian Trudel]

Hi Florian,

The reason I came up with this build switch is that it was reported by
configure. I inspected the results and noticed build and host were
different, used the value reported and it worked.

Ian

Le ven. 23 août 2019, à 08 h 56, Florian Weimer <fweimer@redhat.com> a
écrit :

> * Ian Trudel:
>
> > Here is the solution to build the 32 bit version of glibc on CentOS:
> >
> > ../../configure --prefix=/usr --disable-profile --enable-add-ons
> --with-headers=/usr/include --with-binutils=/usr/bin
> > --build=x86_64-x32-linux-gnu --host=i686-pc-linux-gnu CC="gcc -m32"
> CXX="g++ -m32" CFLAGS="-O2 -march=i686"
> > CXXFLAGS="-O2 -march=i686"
> >
> > The build and host switches have to be different for some strange reason.
>
> --build=x86_64-x32-linux-gnu seems wrong.
>
>   CC="gcc -m32" CXX="g++ -m32" --build=i686-linux-gnu
>
> works for me, with a sufficiently recent gcc and g++ on the path.
>
> Thanks,
> Florian
>

Re: Building and installing a new version of GLIBC on CentOS

[Florian Weimer]

* Ian Trudel:

> The reason I came up with this build switch is that it was reported by
> configure. I inspected the results and noticed build and host were
> different, used the value reported and it worked.

Huh.  x86-64-x32 is very different from both x86-64 and i386 (CentOS
does not support it), so it's surprising that it comes up.

Thanks,
Florian

Re: Building and installing a new version of GLIBC on CentOS

[Ian Trudel]

Le ven. 23 août 2019, à 09 h 33, Florian Weimer <fweimer@redhat.com> a
écrit :

>
> Huh.  x86-64-x32 is very different from both x86-64 and i386 (CentOS
> does not support it), so it's surprising that it comes up.
>

Yes, this is confusing but nothing worked until then. Perhaps I should
retry with --build=i686-linux-gnu as you suggested.

I've been using this glibc 32 bit for a week or so and it works perfectly
fine.

Who am I to argue? haha

Ian