public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: Evgeny Morozov <evgeny+libclist@loop54.com>
To: libc-help@sourceware.org
Subject: Patching glibc 2.27 on Ubuntu
Date: Thu, 25 Nov 2021 09:53:25 +0100	[thread overview]
Message-ID: <CAAi0WvH78RGyUxvbbMJQZm_ZMTRSWS8yGuHW5DpQ1vvS_-6fXg@mail.gmail.com> (raw)

Hi,

I'd like to apply a patch from
https://sourceware.org/bugzilla/show_bug.cgi?id=25847 (the "mitigation
patch": https://sourceware.org/bugzilla/attachment.cgi?id=12484) to many
x64 systems running Ubuntu 18.04. They should all have the same version of
the libc6 package installed. Is it possible to build it on one system and
just copy the affected binaries to all of them, or do I have to build and
install it on each system? If I can copy just a few binaries, should I copy
only libpthread.so, libc.so, both, something else?

I was able to build glibc as follows:

sudo apt build-dep glibc
mkdir src
apt source glibc
mkdir build
cd build
../glibc-2.27/configure --prefix=/usr
make -j

This generates a 17MB libc.so file, while the system one is ~2MB. Should I
run strip on it?

Thanks in advance,
Evgeny Morozov

             reply	other threads:[~2021-11-25  8:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-25  8:53 Evgeny Morozov [this message]
2021-11-25 17:24 ` Carlos O'Donell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAAi0WvH78RGyUxvbbMJQZm_ZMTRSWS8yGuHW5DpQ1vvS_-6fXg@mail.gmail.com \
    --to=evgeny+libclist@loop54.com \
    --cc=libc-help@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).