From: Jakub Jelinek <jakub@redhat.com>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: libc-hacker@sources.redhat.com
Subject: [PATCH] */lib64 for s390x
Date: Wed, 09 Oct 2002 07:05:00 -0000 [thread overview]
Message-ID: <20021009151537.O3451@sunsite.ms.mff.cuni.cz> (raw)
In-Reply-To: <200210091505.12166.schwidefsky@de.ibm.com>; from schwidefsky@de.ibm.com on Wed, Oct 09, 2002 at 03:05:11PM +0200
On Wed, Oct 09, 2002 at 03:05:11PM +0200, Martin Schwidefsky wrote:
> All I can say is: he is right. I wanted to look into versioned symbols for
> the glibc functions that are affected by the utmp.h/utmpx.h change but I
> am too busy with other stuff right now (and I know that extreme caution
> is required for anything to do with versioning).
Don't you need following too?
2002-10-09 Jakub Jelinek <jakub@redhat.com>
* sysdeps/unix/sysv/linux/configure.in: Use */lib64 for s390x too.
* sysdeps/unix/sysv/linux/configure: Rebuilt.
--- libc/sysdeps/unix/sysv/linux/configure.in 28 Sep 2002 20:39:35 -0000 1.1.1.17
+++ libc/sysdeps/unix/sysv/linux/configure.in 9 Oct 2002 11:14:45 -0000 1.14
@@ -185,7 +185,8 @@ fi
if test "$prefix" = "/usr" -o "$prefix" = "/usr/"; then
# 64bit libraries on sparc go to /lib64 and not /lib
if test "$machine" = "sparc/sparc64" -o "$machine" = "x86_64" \
- -o "$machine" = "powerpc/powerpc64"; then
+ -o "$machine" = "powerpc/powerpc64" \
+ -o "$machine" = "s390/s390-64"; then
libc_cv_slibdir="/lib64"
if test "$libdir" = '${exec_prefix}/lib'; then
libdir='${exec_prefix}/lib64';
--- libc/sysdeps/unix/sysv/linux/configure 28 Sep 2002 20:39:35 -0000 1.1.1.17
+++ libc/sysdeps/unix/sysv/linux/configure 9 Oct 2002 11:14:45 -0000 1.14
@@ -185,7 +185,8 @@ fi
if test "$prefix" = "/usr" -o "$prefix" = "/usr/"; then
# 64bit libraries on sparc go to /lib64 and not /lib
if test "$machine" = "sparc/sparc64" -o "$machine" = "x86_64" \
- -o "$machine" = "powerpc/powerpc64"; then
+ -o "$machine" = "powerpc/powerpc64" \
+ -o "$machine" = "s390/s390-64"; then
libc_cv_slibdir="/lib64"
if test "$libdir" = '${exec_prefix}/lib'; then
libdir='${exec_prefix}/lib64';
Jakub
next prev parent reply other threads:[~2002-10-09 13:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-09 6:15 utmp.h & utmpx.h for s390 Martin Schwidefsky
2002-10-09 7:05 ` Jakub Jelinek [this message]
2002-10-15 15:26 ` [PATCH] */lib64 for s390x Andreas Jaeger
2002-10-09 7:35 Martin Schwidefsky
2002-10-09 7:48 ` Jakub Jelinek
2002-10-09 10:00 Martin Schwidefsky
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=20021009151537.O3451@sunsite.ms.mff.cuni.cz \
--to=jakub@redhat.com \
--cc=libc-hacker@sources.redhat.com \
--cc=schwidefsky@de.ibm.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).