Bastian Blank a écrit :
> Hi folks
>
> 2.6.23 still does not build on hppa. One possible seems gcc 4.2, but
> someone needs to check it.

The problems also occurs with gcc-4.2. One solution is to build this
file with -O1.


--
.''`. Aurelien Jarno | GPG: 1024D/F1BCDB73
: :' : Debian developer | Electrical Engineer
`. `' aurel32@debian.org | aurelien@aurel32.net
`- people.debian.org/~aurel32 | www.aurel32.net


--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Sun, Dec 16, 2007 at 12:05:35AM +0100, Bastian Blank wrote:
>
> 2.6.23 still does not build on hppa. One possible seems gcc 4.2, but
> someone needs to check it.

it builds with 4.2 and disabled ocfs2.

checked on paer, but as i didn't boot the corresponding image
i left that for kyle. in urgency i can commit.


--
maks


--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Sun, Dec 16, 2007 at 12:34:55AM +0100, Aurelien Jarno wrote:
> Bastian Blank a écrit :
> > 2.6.23 still does not build on hppa. One possible seems gcc 4.2, but
> > someone needs to check it.
> The problems also occurs with gcc-4.2.

Okay, so I missunderstood it.

> One solution is to build this
> file with -O1.

Not really possible without nasty patches which are "forbidden" by
policy. So ocfs2 needs to be disabled.

Bastian

--
First study the enemy. Seek weakness.
-- Romulan Commander, "Balance of Terror", stardate 1709.2


--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Sun, Dec 16, 2007 at 12:17:04PM +0100, Bastian Blank wrote:
> On Sun, Dec 16, 2007 at 12:34:55AM +0100, Aurelien Jarno wrote:
> > Bastian Blank a écrit :
> > > 2.6.23 still does not build on hppa. One possible seems gcc 4.2, but
> > > someone needs to check it.
> > The problems also occurs with gcc-4.2.
>
> Okay, so I missunderstood it.
>
> > One solution is to build this
> > file with -O1.
>
> Not really possible without nasty patches which are "forbidden" by
> policy. So ocfs2 needs to be disabled.
>

that's fine, it's rather unlikely people are using it.

cheers, kyle