All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: "Linas Vepstas (Code Aurora)" <linas@codeaurora.org>
Cc: GLIBC Devel <libc-alpha@sourceware.org>,
	Chris Metcalf <cmetcalf@tilera.com>,
	Jonas Bonn <jonas.bonn@gmail.com>,
	libc-ports@sourceware.org, linux-hexagon@vger.kernel.org,
	linux-arch@vger.kernel.org, Mark Salter <msalter@redhat.com>,
	Tobias Klauser <tklauser@distanz.ch>,
	Guan Xuetao <gxt@mprc.pku.edu.cn>
Subject: Re: __ARCH_WANT_SYSCALL_DEPRECATED
Date: Mon, 22 Aug 2011 22:43:18 +0200	[thread overview]
Message-ID: <2047151.mWElcT8jZQ@wuerfel> (raw)
In-Reply-To: <20110822193602.GA23301@codeaurora.org>

On Monday 22 August 2011 14:36:02 Linas Vepstas wrote:
> 
> So: What's the latest on asm-generic support on glibc? 
> I just pulled glibc-2.14 and note that Chris Metcalf's
> generic implementation hasn't been folded in yet. 
> It seems to work well for me, so can we expect it
> anytime soon?
> 
> Another problem:  If I don't define __ARCH_WANT_SYSCALL_DEPRECATED
> in the kernel asm/unistd.h  then glibc won't build: currently,
> I get 
> ../sysdeps/unix/sysv/linux/getdents.c:105: error: ‘__NR_getdents’ undeclared (first use in this function)
> 
> A very quick grep tells me that asm-generic defines a getdents64
> but that is not what glibc is looking for.  Is there any chance
> that there are glibc patches floating around somewhere that heal
> this and any remaining __ARCH_WANT_SYSCALL_DEPRECATED issues?

I don't know the answer to your question, but I've added Mark Salter,
Guan Xuetao and Tobias Klauser to the list, since they probably have
the same issue on c64x, unicore32 and nios2. c64x is currently nommu,
but there is a similar problem with uclibc and I expect that architecture
to grow an mmu at some point.

As far as I can tell, there is now a total of six architectures using
the generic syscalls (not counting s*core, because that relies on
the deprecated calls) and at least two unnamed ones waiting to have
their coming-out, plus a few stagnated ports (lm32, arc, mmix, meta, ...)
that would need to get converted if someone wanted to push kernel
support upstream.

	Arnd

  reply	other threads:[~2011-08-22 20:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-22 19:36 __ARCH_WANT_SYSCALL_DEPRECATED Linas Vepstas (Code Aurora)
2011-08-22 19:36 ` __ARCH_WANT_SYSCALL_DEPRECATED Linas Vepstas (Code Aurora)
2011-08-22 20:43 ` Arnd Bergmann [this message]
2011-08-24  2:01   ` __ARCH_WANT_SYSCALL_DEPRECATED Guan Xuetao
2011-08-24 15:25     ` __ARCH_WANT_SYSCALL_DEPRECATED Linas Vepstas (Code Aurora)
2011-08-25  2:33       ` __ARCH_WANT_SYSCALL_DEPRECATED Guan Xuetao
2011-08-26  2:56       ` __ARCH_WANT_SYSCALL_DEPRECATED Chris Metcalf
2011-08-29 10:43   ` __ARCH_WANT_SYSCALL_DEPRECATED Tobias Klauser
2011-08-29 15:21     ` __ARCH_WANT_SYSCALL_DEPRECATED Joseph S. Myers
2011-08-29 16:18       ` __ARCH_WANT_SYSCALL_DEPRECATED Tobias Klauser
2011-08-22 22:11 ` __ARCH_WANT_SYSCALL_DEPRECATED Joseph S. Myers
2011-08-22 19:36 __ARCH_WANT_SYSCALL_DEPRECATED Linas Vepstas (Code Aurora)

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=2047151.mWElcT8jZQ@wuerfel \
    --to=arnd@arndb.de \
    --cc=cmetcalf@tilera.com \
    --cc=gxt@mprc.pku.edu.cn \
    --cc=jonas.bonn@gmail.com \
    --cc=libc-alpha@sourceware.org \
    --cc=libc-ports@sourceware.org \
    --cc=linas@codeaurora.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-hexagon@vger.kernel.org \
    --cc=msalter@redhat.com \
    --cc=tklauser@distanz.ch \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.