From: Quinn Harris <quinn@nmt.edu>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] glibc-2.3 and prelinking
Date: 05 Oct 2002 00:22:15 -0600 [thread overview]
Message-ID: <1033798935.27154.112.camel@quinn.rcn.nmt.edu> (raw)
I have started to build a system with glibc-2.3 primarily to use
prelinking. But I just realized that prelinking and portage aren't
going to get along.
The prelink tool will change binaries and shared libraries on the system
and therefor the modify time and the MD5 checksum. I expect portage
will no longer properly unmerge these changed files.
The prelink tool can be changed to update the portage db probably by
using a wrapper script. Or, portage could be modified to utilize
prelink to determine if the file was modified by prelink. This is
explained in
http://sources.redhat.com/ml/libc-alpha/2002-10/msg00089.html
What would be the best solution?
Some info about prelinking
http://dforce.sh.cvut.cz/~seli/en/linking2/
On a side note. gcc-3.2 won't compile right with glibc-2.3. It looks
like the gcc-3.2-branch cvs has the problem fixed.
http://gcc.gnu.org/ml/gcc/2002-10/msg00333.html
next reply other threads:[~2002-10-05 6:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-05 6:22 Quinn Harris [this message]
2002-10-05 22:16 ` [gentoo-dev] glibc-2.3 and prelinking Quinn Harris
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=1033798935.27154.112.camel@quinn.rcn.nmt.edu \
--to=quinn@nmt.edu \
--cc=gentoo-dev@gentoo.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