From: Paul Schutte <sjpschutte@gmail.com>
To: musl@lists.openwall.com
Subject: Re: stat.h
Date: Tue, 4 Mar 2014 07:33:49 +0200 [thread overview]
Message-ID: <CAKHv7pgEHosjvXoxmwoiwjNA5aqXRT7eXaD04JW+_UV=dXhY1w@mail.gmail.com> (raw)
In-Reply-To: <20140304053116.GH184@brightrain.aerifal.cx>
[-- Attachment #1: Type: text/plain, Size: 1011 bytes --]
Thanks
On Tue, Mar 4, 2014 at 7:31 AM, Rich Felker <dalias@aerifal.cx> wrote:
> On Tue, Mar 04, 2014 at 07:18:05AM +0200, Paul Schutte wrote:
> > Hi
> >
> > Hope I am not too anoying ... ;-)
> >
> > I have tried both _GNU_SOURCE and _LARGEFILE64_SOURCE and in neither case
> > do I get a definition for 'struct stat64'
> >
> > If I understand correctly then source using 'struct stat64' should be
> fixed
> > to use 'struct stat' instead ?
> > If this is not correct, then 'struct stat64' should probably be added to
> > <sys/stat.h> as only the following are defined there:
> >
> > #if defined(_LARGEFILE64_SOURCE) || defined(_GNU_SOURCE)
> > #define stat64 stat
>
> This defines "struct stat64", which the preprocessor replaces with
> "struct stat". If that's not working it's because the source file is
> doing something bogus (like #undef stat64, perhaps).
>
> In any case, just fixing the source to use "stat" instead of "stat64"
> (and likewise for any other *64 mess) is the best approach.
>
> Rich
>
[-- Attachment #2: Type: text/html, Size: 1542 bytes --]
next prev parent reply other threads:[~2014-03-04 5:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 18:36 stat.h Paul Schutte
2014-03-03 19:42 ` stat.h Szabolcs Nagy
2014-03-04 4:15 ` stat.h Paul Schutte
2014-03-04 4:20 ` stat.h Rich Felker
2014-03-04 5:18 ` stat.h Paul Schutte
2014-03-04 5:31 ` stat.h Rich Felker
2014-03-04 5:33 ` Paul Schutte [this message]
2014-03-04 4:18 ` stat.h Rich Felker
2014-03-04 4:31 ` stat.h Paul Schutte
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='CAKHv7pgEHosjvXoxmwoiwjNA5aqXRT7eXaD04JW+_UV=dXhY1w@mail.gmail.com' \
--to=sjpschutte@gmail.com \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).