All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaud Patard (Rtp) <arnaud.patard@rtp-net.org>
To: Laurent Desnogues <laurent.desnogues@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [7118] linux-user: prefer glibc over direct syscalls
Date: Tue, 21 Apr 2009 10:36:13 +0200	[thread overview]
Message-ID: <87ws9ee742.fsf@lechat.rtp-net.org> (raw)
In-Reply-To: <761ea48b0904210056w37100e85tcf71162c84e961d1@mail.gmail.com> (Laurent Desnogues's message of "Tue\, 21 Apr 2009 09\:56\:12 +0200")

Laurent Desnogues <laurent.desnogues@gmail.com> writes:

Hi,

>> +#ifdef TARGET_NR_utimensat
>> +static int sys_utimensat(int dirfd, const char *pathname,
>> +    const struct timespec times[2], int flags)
>> +{
>> +  return (utimensat(dirfd, pathname, times, flags));
>> +}
>> +#endif
>
> Just to point that my system has all *at functions except for utimensat.
> This breaks compilation.  Shouldn't all *at functions be tested in the
> configure script?

This utimensat change is broken, I've sent a patch to revert to the
syscall interface. As a side effect, it'll bring back the check :

#if defined(TARGET_NR_utimensat) && defined(__NR_utimensat)

It will likely solve your trouble. Lets hope the patch will be merged :)

>
> For the record I am running CentOS 5.3 x86_64.

hmm... glibc older than 2.6 or kernel older than 2.6.22 ?

Arnaud

  reply	other threads:[~2009-04-21  8:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-15 16:12 [Qemu-devel] [7118] linux-user: prefer glibc over direct syscalls Aurelien Jarno
2009-04-15 19:21 ` Stefan Weil
2009-04-15 19:48   ` Aurelien Jarno
2009-04-16 15:25 ` Laurent Desnogues
2009-04-16 16:47   ` Riku Voipio
2009-04-17 13:51     ` Aurelien Jarno
2009-04-17  0:16 ` Paul Brook
2009-04-17  8:03   ` Riku Voipio
2009-04-21  7:56 ` Laurent Desnogues
2009-04-21  8:36   ` Arnaud Patard [this message]
2009-04-21  8:35     ` Laurent Desnogues

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=87ws9ee742.fsf@lechat.rtp-net.org \
    --to=arnaud.patard@rtp-net.org \
    --cc=laurent.desnogues@gmail.com \
    --cc=qemu-devel@nongnu.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 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.