public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Andreas Jaeger <aj@suse.de>
To: Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Fix sunrpc/xcrypt.c for GCC 4.0
Date: Sun, 19 Dec 2004 19:26:00 -0000	[thread overview]
Message-ID: <m33by285ha.fsf@gromit.moeb> (raw)

[-- Attachment #1: Type: text/plain, Size: 1393 bytes --]


Ok to commit the appended patch to fix xcrypt with GCC 4.0?  This is
similar to a patch by Alexandre for getnetgrent_r.

Andreas

2004-12-19  Andreas Jaeger  <aj@suse.de>

	[BZ #573]
	* sunrpc/xcrypt.c (passwd2des_internal): Make it hidden instead of
	internal linkage.

============================================================
Index: sunrpc/xcrypt.c
--- sunrpc/xcrypt.c	17 Sep 2002 10:58:00 -0000	1.7
+++ sunrpc/xcrypt.c	19 Dec 2004 15:13:10 -0000
@@ -69,13 +69,15 @@ static char hexval (char) internal_funct
 
 static void hex2bin (int, char *, char *) internal_function;
 static void bin2hex (int, unsigned char *, char *) internal_function;
-static void passwd2des_internal (char *pw, char *key);
-
+void passwd2des_internal (char *pw, char *key);
+#ifdef _LIBC
+libc_hidden_proto (passwd2des_internal)
+#endif
 
 /*
  * Turn password into DES key
  */
-static void
+void
 passwd2des_internal (char *pw, char *key)
 {
   int i;
@@ -88,6 +90,7 @@ passwd2des_internal (char *pw, char *key
 }
 
 #ifdef _LIBC
+libc_hidden_def (passwd2des_internal)
 strong_alias (passwd2des_internal, passwd2des)
 #else
 void passwd2des (char *pw, char *key)

-- 
 Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj
  SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
   GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126

[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]

             reply	other threads:[~2004-12-19 19:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-19 19:26 Andreas Jaeger [this message]
2004-12-19 20:33 ` Roland McGrath
2004-12-19 20:59 ` H. J. Lu

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=m33by285ha.fsf@gromit.moeb \
    --to=aj@suse.de \
    --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).