From: Ulrich Drepper <drepper@redhat.com>
To: GNU libc hacker <libc-hacker@sources.redhat.com>
Subject: Re: sysdeps/generic
Date: Wed, 14 Dec 2005 15:59:00 -0000 [thread overview]
Message-ID: <43A04110.3090508@redhat.com> (raw)
In-Reply-To: <439FDBEE.6070608@redhat.com>
The check-in went fine, all is checked in.
If you have the chance, do a build on your arch(s) of interest before
updating cvs. Then again with the same options after the update and
compare the builds.
Just run size on libc_pic.a and find the files which changed. These
should be only a few. The look at the sections in the changed files. I
found only changes in debug info and unwind sections and those changes
are related to some path changes. I think I had in total 6 files which
changed on x86-64.
Things that need work: add-ons. Specifically the rtkio (LT should not
be an issue since it doesn't work on the trunk anyway). What is needed
for rtkio are a few files with
#include "../rt/*.c"
--
⧠Ulrich Drepper ⧠Red Hat, Inc. ⧠444 Castro St ⧠Mountain View, CA â
next prev parent reply other threads:[~2005-12-14 15:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-14 8:48 sysdeps/generic Ulrich Drepper
2005-12-14 13:43 ` sysdeps/generic Andreas Schwab
2005-12-14 15:59 ` Ulrich Drepper [this message]
2005-12-14 23:20 ` sysdeps/generic Andreas Schwab
2005-12-15 21:15 ` sysdeps/generic Roland McGrath
2005-12-15 9:48 ` sysdeps/generic Kaz Kojima
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=43A04110.3090508@redhat.com \
--to=drepper@redhat.com \
--cc=libc-hacker@sources.redhat.com \
/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).