All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eduardo Habkost <ehabkost@redhat.com>
To: Arnaud Patard <arnaud.patard@rtp-net.org>
Cc: Glauber Costa <glommer@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] check for utimensat() availability on configure
Date: Wed, 10 Jun 2009 11:12:55 -0300	[thread overview]
Message-ID: <20090610141255.GZ18045@blackpad> (raw)
In-Reply-To: <87ocsxoye4.fsf@lechat.rtp-net.org>

On Wed, Jun 10, 2009 at 12:06:27AM +0200, Arnaud Patard wrote:
> Eduardo Habkost <ehabkost@redhat.com> writes:
> 
> Hi Eduardo,
> 
> > Some glibc versions don't have utimensat() available, but have other xxxat()
> > functions. Make a separated check for utimensat() to make sure we can compile
> > linux-user against some older glibc versions.
> 
> Why didn't you take the patches available in this thread
> http://lists.gnu.org/archive/html/qemu-devel/2009-04/msg01290.html ?

Because it is not included on the qemu tree.

> 
> afaik, they can also be found in maemo's qemu git tree (and sent again
> later to the mailing list)

Why is it not included, if it is a better fix?


> 
> [...]
> 
> > +#ifdef CONFIG_UTIMENSAT
> > +
> > +#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));
> > +}
> 
> As you'll see when reading the thread I mentionned, this is broken.

I don't see why it is broken, unless current qemu code is broken too. I
just changed it to use the !CONFIG_ATFILE sys_utimensat() implementation
(that was already present on the code) if glibc doesn't provide
utimensat(). What do you suggest instead?

-- 
Eduardo

  reply	other threads:[~2009-06-10 14:13 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-09 21:26 [Qemu-devel] [PATCH 0/2] linux-user: fix build error against older glibcs Eduardo Habkost
2009-06-09 21:26 ` [Qemu-devel] [PATCH 1/2] linux-user/syscall.c: define _ATFILE_SOURCE Eduardo Habkost
2009-06-09 21:26 ` [Qemu-devel] [PATCH 2/2] check for utimensat() availability on configure Eduardo Habkost
2009-06-09 22:06   ` Arnaud Patard
2009-06-10 14:12     ` Eduardo Habkost [this message]
2009-06-10 14:39       ` Arnaud Patard
2009-06-10 19:10         ` Eduardo Habkost
2009-06-10 21:48           ` Riku Voipio
2009-06-10 22:09             ` Eduardo Habkost
2009-06-11 15:14               ` Riku Voipio
2009-06-10 16:07       ` Riku Voipio
2009-06-10 16:20         ` Glauber Costa
2009-06-10 16:30           ` Arnaud Patard
2009-06-10 16:56             ` Glauber Costa
2009-06-10 22:05               ` Riku Voipio
2009-06-11  8:33                 ` Arnaud Patard
2009-06-11 15:09                   ` Riku Voipio
2009-06-12  8:30                     ` ltp vs linux-user (was: Re: [Qemu-devel] [PATCH 2/2] check for utimensat() availability on configure) Arnaud Patard
2009-06-11 11:27                 ` [Qemu-devel] [PATCH 2/2] check for utimensat() availability on configure vibi sreenivasan
2009-06-12 13:24                 ` vibi sreenivasan
2009-06-10 15:03     ` Glauber Costa
2009-06-10 21:53       ` Riku Voipio

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=20090610141255.GZ18045@blackpad \
    --to=ehabkost@redhat.com \
    --cc=arnaud.patard@rtp-net.org \
    --cc=glommer@redhat.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.