From: Paul Schutte <sjpschutte@gmail.com>
To: musl@lists.openwall.com
Subject: Re: stat.h
Date: Tue, 4 Mar 2014 06:15:01 +0200 [thread overview]
Message-ID: <CAKHv7pgF74MsdXk3+gxtg-Bt5ZGKeMWu506PLm1ixrkJr69GQg@mail.gmail.com> (raw)
In-Reply-To: <20140303194214.GC7372@port70.net>
[-- Attachment #1: Type: text/plain, Size: 963 bytes --]
Thanks and I agree with padsp being messy.
My question really boils down to
Should 'struct stat64' be used from within a program and if so, which
header file should I include ?
Regards
Paul
On Mon, Mar 3, 2014 at 9:42 PM, Szabolcs Nagy <nsz@port70.net> wrote:
> * Paul Schutte <sjpschutte@gmail.com> [2014-03-03 20:36:24 +0200]:
> > I am trying to compile pulseaudio5 against musl, but it fails with an
> error
> > indicating that struct stat64 is not defined:
> >
> > utils/padsp.c:133:44: warning: 'struct stat64' declared inside parameter
> > list [enabled by default]
> > utils/padsp.c:133:44: warning: its scope is only this definition or
> > declaration, which is probably not what you want [enabled by default]
> >
>
> last time i checked padsp was hopelessly broken
> (it tries to emulate /dev/dsp etc by overriding
> internal glibc functions with code that is not
> even compatible with the glibc api requirements)
>
> alsa-oss has a similar mess
>
[-- Attachment #2: Type: text/html, Size: 1441 bytes --]
next prev parent reply other threads:[~2014-03-04 4:15 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 ` Paul Schutte [this message]
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 ` stat.h Paul Schutte
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=CAKHv7pgF74MsdXk3+gxtg-Bt5ZGKeMWu506PLm1ixrkJr69GQg@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).