lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080209105344.GH6505@cs181133002.pp.htv.fi>
Date:	Sat, 9 Feb 2008 12:53:44 +0200
From:	Adrian Bunk <bunk@...nel.org>
To:	Martin Schwidefsky <schwidefsky@...ibm.com>
Cc:	gerg@...inux.org, linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: m68knommu compile error

On Sat, Feb 09, 2008 at 11:21:12AM +0100, Martin Schwidefsky wrote:
> On Sat, 2008-02-09 at 00:25 +0200, Adrian Bunk wrote:
> > Commit 2f569afd9ced9ebec9a6eb3dbf6f83429be0a7b4 breaks m68knommu:
> 
> Does the patch below fixes the problem?

Thanks, it fixes it.

> I tried to cross compile for
> m68knommu but it seems like you need a special m68k compiler to get it
> compile all the way through.

I'm using one from upstream svn head (= tree that will become gcc 4.3).

> With the patch it did fail with a different
> error, so I assume it is fixed.

That's Matt's "break all no-MMU architectures in swapops.h" regression 
for which a patch is already floating around.

> The problem is that the pgtable_t is
> simply missing for m68knommu, I must have overlooked a reject for one of
> the constant regenerations of the patch to keep up with upstream. Sorry
> about that.
> 
> blue skies,
>   Martin.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ