public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Sven-Haegar Koch <haegar@sdinet.de>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	Christoph Biedl <linux-kernel.bfrz@manchmal.in-ulm.de>
Subject: Re: Linux 2.6.32.61
Date: Mon, 10 Jun 2013 18:04:05 +0200	[thread overview]
Message-ID: <20130610160405.GI2685@1wt.eu> (raw)
In-Reply-To: <alpine.DEB.2.10.1306101708360.1713@aurora64.sdinet.de>

Hi Sven-Haegar,

On Mon, Jun 10, 2013 at 05:11:49PM +0200, Sven-Haegar Koch wrote:
> On Mon, 10 Jun 2013, Willy Tarreau wrote:
> 
> > Willy Tarreau (2):
> >       x86, ptrace: fix build breakage with gcc 4.7
> 
> This change breaks "make headers_install":
> 
>   CHECK   include (0 files)
>   CHECK   include/asm (54 files)
> /home/haegar/src/2.6.32/linux/usr/include/asm/ptrace.h:5: included file 'linux/linkage.h' is not exported
> make[3]: *** [/home/haegar/src/2.6.32/linux/usr/include/asm/.check] Error 123
> make[2]: *** [headers_check] Error 2
> make[1]: *** [deb-pkg] Error 2
> make: *** [deb-pkg] Error 2

Grrr... seems like we'll need to fix the gcc 4.7 build issue differently
because we probably don't want to export linux/linkage.h just to make
the __attribute__((regparm=3)) appear in one arch-specific file.

I'll check if the definition in the include is really needed after I
install a gcc 4.7 cross-compiler.

Thanks for your report, and sorry for the mess.

Willy


  reply	other threads:[~2013-06-10 16:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-10 10:15 Linux 2.6.32.61 Willy Tarreau
2013-06-10 15:11 ` Sven-Haegar Koch
2013-06-10 16:04   ` Willy Tarreau [this message]
2013-06-13 17:53   ` Linux 2.6.32.61 - x86/ptrace/gcc 4.7 build error Willy Tarreau
2013-06-13 18:31     ` Sven-Haegar Koch
2013-06-13 18:41       ` Willy Tarreau
2013-06-14  6:23     ` Christoph Biedl
2013-06-14  6:36       ` Willy Tarreau
2013-06-14  4:11 ` Linux 2.6.32.61 Ben Hutchings
2013-06-14  5:54   ` Willy Tarreau

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=20130610160405.GI2685@1wt.eu \
    --to=w@1wt.eu \
    --cc=haegar@sdinet.de \
    --cc=linux-kernel.bfrz@manchmal.in-ulm.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    /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