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: <20080229130426.GB22335@cs181133002.pp.htv.fi>
Date:	Fri, 29 Feb 2008 15:04:26 +0200
From:	Adrian Bunk <bunk@...nel.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Russell King <rmk+lkml@....linux.org.uk>,
	LKML <linux-kernel@...r.kernel.org>, linux-next@...r.kernel.org,
	linux-arch@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linus <torvalds@...ux-foundation.org>
Subject: Re: Announce: Linux-next (Or Andrew's dream  :-))

On Fri, Feb 29, 2008 at 11:45:51PM +1100, Stephen Rothwell wrote:
> Hi Russell,
> 
> On Tue, 26 Feb 2008 14:54:18 +1100 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> >
> > On Sat, 16 Feb 2008 00:09:43 +0000 Russell King <rmk+lkml@....linux.org.uk> wrote:
> > >
> > > As mentioned elsewhere, what we need for ARM is to extend the kautobuild
> > > infrastructure (see armlinux.simtec.co.uk) so that we can have more trees
> > > at least compile tested regularly - but that requires the folk there to
> > > have additional compute power (which isn't going to happen unless folk
> > > stamp up some machines _or_ funding).
> > 
> > I now have an arm cross compiler (gcc-4.0.2-glibc-2.3.6
> > arm-unknown-linux-gnu).  (See the results page at
> > http://kisskb.ellerman.id.au/kisskb/branch/9/ - I must get a better
> > name/place :-(.)  Is this sufficient to help you out?  What configs would
> > be useful to build (as Andrew said, they don't take very long each).
> > 
> > I really want as many subsystems as possible in the linux-next tree in an
> > attempt to avoid some of the merge/conflict problems we have had in the
> > past.  What can we do to help?
> 
> OK, I tried this out:  I built all 75 arm defconfigs with the cross
> compiler above (the resulting log file is at
> http://ozlabs.org/~sfr/armall.log.bz2). 17 failed (I don't know why - I
> didn't even really look).

2 errors are expected (long-standing breakages).

14 failures are due to your ancient gcc 4.0.2 not supporting -mabi=aapcs-linux:
/scratch/sfr/next/scripts/mod/empty.c:1: error: invalid ABI option: -mabi=aapcs-linux

Another one is an internal error in your ancient compiler:
/scratch/sfr/next/arch/arm/common/it8152.c:148: internal compiler error: in trunc_int_for_mode, at explow.c:53

Can you build a cross compiler using gcc 4.2.3 from ftp.gnu.org instead?
That one serves me perfectly for my cross-compile tests.

>...
> Cheers,
> Stephen Rothwell                    sfr@...b.auug.org.au
>...

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