Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Jeff Bailey <jbailey@raspberryginger.com>
To: Carlos O'Donell <carlos@systemhalted.org>
Cc: Andreas Schwab <schwab@suse.de>,
	libc-ports@sources.redhat.com,
	parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] Re: Duplicate ustat structure
Date: Mon, 24 Jul 2006 20:47:52 -0400	[thread overview]
Message-ID: <1153788472.7679.2.camel@localhost.localdomain> (raw)
In-Reply-To: <119aab440607161313h4c196882gab171b4614957b7c@mail.gmail.com>

On dim, 2006-07-16 at 16:13 -0400, Carlos O'Donell wrote:
> On 7/16/06, Jeff Bailey <jbailey@raspberryginger.com> wrote:
> > On Sun, Jul 16, 2006 at 06:39:15PM +0200, Andreas Schwab wrote:
> >
> > > > The problem is that bits/ustat.h includes the definition of struct
> > > > ustat.  However, sys/types.h eventually winds up pulling in
> > > > linux/types.h which also defines struct ustat.
> > >
> > > <sys/types.h> should not include <linux/types.h> in the first place.
> >
> > It seems like it ought to now that the kernel is exporting a set of
> > headers that are intended to be used by userspace.  struct ustat is
> > defined in linux/types.h.
> 
> In which case this patch should go upstream to libc-alpha, where the
> generic version of ustat.h should be changed.

Certainly, but could you apply the second patch in the meantime?  That's
what all the other arch's do right now, and it will at least make
current glibc buildable with current kernel headers.  I'll try and pitch
the concept of using kernel headers instead of copying values into glibc
when I have enough time and energy to fight that battle.

Tks,
Jeff Bailey

-- 
Although when you're in the situation that RMS is telling you that
you're being too ideological about freedom, maybe, just maybe, it's
true.
- Matthew Wilcox

_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

      reply	other threads:[~2006-07-25  0:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-16 16:03 [parisc-linux] Duplicate ustat structure Jeff Bailey
     [not found] ` <jeodvpbj2k.fsf@sykes.suse.de>
2006-07-16 17:07   ` [parisc-linux] " Jeff Bailey
2006-07-16 20:13     ` Carlos O'Donell
2006-07-25  0:47       ` Jeff Bailey [this message]

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=1153788472.7679.2.camel@localhost.localdomain \
    --to=jbailey@raspberryginger.com \
    --cc=carlos@systemhalted.org \
    --cc=libc-ports@sources.redhat.com \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=schwab@suse.de \
    /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