public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Hutchings <ben@decadent.org.uk>
To: Rob Landley <rob@landley.net>
Cc: kernel list <linux-kernel@vger.kernel.org>,
	David Miller <davem@davemloft.net>
Subject: Re: git 9c501935a3cd broke the strace build.
Date: Thu, 14 Jan 2010 14:06:45 +0000	[thread overview]
Message-ID: <1263478005.17815.19.camel@localhost> (raw)
In-Reply-To: <201001140457.00696.rob@landley.net>

[-- Attachment #1: Type: text/plain, Size: 1621 bytes --]

On Thu, 2010-01-14 at 04:57 -0600, Rob Landley wrote:
> >    net: Support inclusion of <linux/socket.h> before <sys/socket.h>
> >   
> >    The following user-space program fails to compile:
> >    
> >        #include <linux/socket.h>
> >        #include <sys/socket.h>
> 
> Did it ever?  Isn't #including both sys/thingy and a linux/thingy in the same 
> program considered bad form?

I don't see why.

Even if a source file doesn't include both of them directly, they may
both be included indirectly.

[...]
> Now under 2.6.32 it dies with:
> 
>   linux/netlink.h:35: error: expected specifier-qualifier-list before
>   'sa_family_t'

I did actually ask for this to be reverted when I saw that it causes
breakage elsewhere, but David Miller insisted that my change was
correct.

> And later on the strace build breaks because it doesn't #include 
> linux/netlink.h when it needs to.  (Why yes, autoconf _is_ brittle and near-
> useless, thanks for noticing.)
> 
> *shrug*  I can patch the strace ./configure to include bits/socket.h instead of 
> linux/socket.h,

Including libc headers under 'bits' is a bad idea.

> but what I can't understand is why _you_ couldn't.  (What use 
> case did this patch actually fix?  Would reversing the order of those two 
> headers have helped?)

I think that reversing the order of the two headers should work for
kernel headers before and after this change.

Ben.

-- 
Ben Hutchings
The generation of random numbers is too important to be left to chance.
                                                            - Robert Coveyou

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

      reply	other threads:[~2010-01-14 14:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-14 10:57 git 9c501935a3cd broke the strace build Rob Landley
2010-01-14 14:06 ` Ben Hutchings [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=1263478005.17815.19.camel@localhost \
    --to=ben@decadent.org.uk \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob@landley.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