public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Biedl <linux-kernel.bfrz@manchmal.in-ulm.de>
To: Willy Tarreau <w@1wt.eu>
Cc: Sven-Haegar Koch <haegar@sdinet.de>,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: Linux 2.6.32.61 - x86/ptrace/gcc 4.7 build error
Date: Fri, 14 Jun 2013 08:23:18 +0200	[thread overview]
Message-ID: <1371190377@msgid.manchmal.in-ulm.de> (raw)
In-Reply-To: <20130613175330.GC27760@1wt.eu>

Willy Tarreau wrote...

> I'm attaching the two patches here to be appled on top of 2.6.32.61, I would
> like it if you could try in your environment to confirm that they correctly
> fix the issue.

Confirmation: Kernel builds and runs for both Debian squeeze and
wheezy (gcc 4.4 and gcc 4.7) on i386.

There are still other issues that need investigation but they might be
older and/or related to changes on my end. virtio-net doesn't seem to
work at all (but does so in the Debian squeeze 2.6.32 kernel), and the
virtualbox guest module (4.1.18) fails to load (known issue on i386 if
build using gcc 4.7, but know this also happens with gcc 4.4).

Unfortunately my time ressources are very limited at the moment, and
there's also something in 3.4.49 which has higher priority. Stay
tuned.

    Christoph

  parent reply	other threads:[~2013-06-14  6:31 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
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 [this message]
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=1371190377@msgid.manchmal.in-ulm.de \
    --to=linux-kernel.bfrz@manchmal.in-ulm.de \
    --cc=haegar@sdinet.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=w@1wt.eu \
    /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