public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Steve McIntyre <steve.mcintyre@linaro.org>
Cc: libc-ports@sourceware.org
Subject: Re: [PATCH 2/4] Check for the FLAG_AARCH64_LIB64 flag in the ldconfig cache
Date: Fri, 08 Feb 2013 20:29:00 -0000	[thread overview]
Message-ID: <m2bobuzh0i.fsf@igel.home> (raw)
In-Reply-To: <20121126150434.GB28791@einval.com> (Steve McIntyre's message of	"Mon, 26 Nov 2012 15:04:34 +0000")

Steve McIntyre <steve.mcintyre@linaro.org> writes:

> +#define add_system_dir(dir) \
> +  do								\
> +    {								\
> +      size_t len = strlen (dir);				\
> +      char path[len + 3];					\
> +      memcpy (path, dir, len + 1);				\
> +      if (len >= 6 && ! memcmp (path + len - 6, "/lib64", 6))	\

Is aarch64 supposed to be using lib64?  If yes there should be a sysdeps
configure script that sets libc_cv_slibdir and libdir similar to
sysdeps/gnu/configure.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

  parent reply	other threads:[~2013-02-08 20:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-26 15:02 [PATCH 1/4] Tag ARM libc6-dependent libraries with FLAG_ELF_LIBC6 Steve McIntyre
2012-11-26 15:05 ` [PATCH 2/4] Check for the FLAG_AARCH64_LIB64 flag in the ldconfig cache Steve McIntyre
2012-11-28 20:58   ` Carlos O'Donell
2012-11-29 10:40     ` Marcus Shawcroft
2012-11-30 15:01     ` Steve McIntyre
2012-11-30 16:38       ` Carlos O'Donell
2012-12-03 15:19         ` Steve McIntyre
2013-02-08 20:29   ` Andreas Schwab [this message]
2012-11-26 15:10 ` [PATCH 3/4] Tag ARM and AArch64 binaries " Steve McIntyre
2012-11-26 16:32 ` [PATCH 1/4] Tag ARM libc6-dependent libraries with FLAG_ELF_LIBC6 Joseph S. Myers

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=m2bobuzh0i.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=libc-ports@sourceware.org \
    --cc=steve.mcintyre@linaro.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).