From: "Steve Schmidtke" <steve_schmidtke@hotmail.com>
To: jdike@addtoit.com, blaisorblade_spam@yahoo.it
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] compile error ...(now tracked down)
Date: Wed, 17 Sep 2003 22:48:58 +0000 [thread overview]
Message-ID: <BAY7-F115B33UKyM25I00015854@hotmail.com> (raw)
>blaisorblade_spam@yahoo.it said:
> > # define st_atime st_atim.tv_sec /* Backward compatibility. */
> ...
> > .st_atime = src->st_atime, /* time of last access */
>
>This is just because of the names of the struct uml_stat. Changing those
>field names should fix the compile problem.
Yup, there are a few ways sub-second file timestamps are handled:
http://mail.gnu.org/archive/html/bug-gnulib/2003-08/msg00183.html
I'm not going to pick one at this time. :) I'll send Jeff another
patch that renames the entries and references to ust_*. I also see a few
stat() references in the code I can stomp right now.
Steve
_________________________________________________________________
Protect your PC - get McAfee.com VirusScan Online
http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next reply other threads:[~2003-09-17 22:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-17 22:48 Steve Schmidtke [this message]
2003-09-18 0:25 ` [uml-devel] compile error ...(now tracked down) Jeff Dike
-- strict thread matches above, loose matches on Subject: below --
2003-09-16 18:29 [uml-devel] compile error with 2.4.22-uml4 and 2.4.23-pre4-djc2-4um Matthew R. Scott
2003-09-17 11:29 ` [uml-devel] compile error ...(now tracked down) BlaisorBlade
2003-09-17 22:20 ` Jeff Dike
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=BAY7-F115B33UKyM25I00015854@hotmail.com \
--to=steve_schmidtke@hotmail.com \
--cc=blaisorblade_spam@yahoo.it \
--cc=jdike@addtoit.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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