public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/721] glibc-2.3.4 fails to build with gcc-4.0-20050213
Date: Mon, 17 Oct 2005 04:52:00 -0000	[thread overview]
Message-ID: <20051017045230.16358.qmail@sourceware.org> (raw)
In-Reply-To: <20050214210840.721.matthew@linuxfromscratch.org>


------- Additional Comments From cvs-commit at gcc dot gnu dot org  2005-10-17 04:52 -------
Subject: Bug 721

CVSROOT:	/cvs/glibc
Module name:	libc
Branch: 	glibc-2_3-branch
Changes by:	roland@sources.redhat.com	2005-10-17 04:52:25

Modified files:
	include        : libc-symbols.h 

Log message:
	2005-03-16  Richard Henderson  <rth@redhat.com>
	
	[BZ #721]
	* include/libc-symbols.h (__hidden_proto): Remove bogus declaration
	of internal.
	(__hidden_def1, __hidden_dot_def1): Remove.
	(__hidden_def2, __hidden_def3): Remove.
	(__hidden_ver1): New.
	(hidden_ver, hidden_def, hidden_weak): Use it.
	(hidden_data_ver, hidden_data_ver, hidden_data_weak): Use non-data
	version of the macro.

Patches:
http://sources.redhat.com/cgi-bin/cvsweb.cgi/libc/include/libc-symbols.h.diff?cvsroot=glibc&only_with_tag=glibc-2_3-branch&r1=1.69&r2=1.69.2.1



-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=721

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


  parent reply	other threads:[~2005-10-17  4:52 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-14 21:08 [Bug libc/721] New: " matthew at linuxfromscratch dot org
2005-02-17  1:17 ` [Bug libc/721] " cvs-commit at gcc dot gnu dot org
2005-02-17  1:17 ` cvs-commit at gcc dot gnu dot org
2005-02-26 12:36 ` matthew at linuxfromscratch dot org
2005-03-01 20:35 ` cvs-commit at gcc dot gnu dot org
2005-03-02 23:40 ` halcyon at whiterapid dot com
2005-03-03  0:34 ` roland at gnu dot org
2005-03-03 10:32 ` matthew at linuxfromscratch dot org
2005-03-03 19:12 ` halcyon at whiterapid dot com
2005-10-17  4:52 ` cvs-commit at gcc dot gnu dot org
2005-10-17  4:52 ` cvs-commit at gcc dot gnu dot org
2005-10-17  4:52 ` cvs-commit at gcc dot gnu dot org
2005-10-17  4:52 ` cvs-commit at gcc dot gnu dot org
2005-10-17  4:52 ` cvs-commit at gcc dot gnu dot org
2005-10-17  4:52 ` cvs-commit at gcc dot gnu dot org
2005-10-17  4:52 ` cvs-commit at gcc dot gnu dot org
2005-10-17  4:52 ` cvs-commit at gcc dot gnu dot org
2005-10-17  4:52 ` cvs-commit at gcc dot gnu dot org [this message]
2005-10-17  4:52 ` cvs-commit at gcc dot gnu dot org
2005-10-17  4:52 ` cvs-commit at gcc dot gnu dot org
2005-10-17  4:52 ` cvs-commit at gcc dot gnu dot org
2005-10-17  4:52 ` cvs-commit at gcc dot gnu dot org
2005-10-17  4:53 ` cvs-commit at gcc dot gnu dot org
2005-10-17  4:53 ` cvs-commit at gcc dot gnu dot org
2005-10-17  4:57 ` cvs-commit at gcc dot gnu dot org
2005-10-17  5:00 ` roland at gnu dot org
2005-12-05 23:12 ` cvs-commit at gcc dot gnu dot org

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=20051017045230.16358.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).