On Thu, Nov 29, 2018 at 02:35:56AM +0100, Daniel Schwierzeck wrote:
> 
> 
> Am 21.11.18 um 09:31 schrieb Trevor Woerner:
> > On kernel.org, a newer 8.1.0 version of the toolchains is available. Also,
> > update the kernel.org version list to include some of the older versions so
> > more architectures can be supported.
> > 
> > Signed-off-by: Trevor Woerner <tre...@toganlabs.com>
> > ---
> >  tools/buildman/toolchain.py | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/tools/buildman/toolchain.py b/tools/buildman/toolchain.py
> > index 4b35f400e9..442a7f977a 100644
> > --- a/tools/buildman/toolchain.py
> > +++ b/tools/buildman/toolchain.py
> > @@ -430,7 +430,7 @@ class Toolchains:
> >          """
> >          arch = command.OutputOneLine('uname', '-m')
> >          base = 'https://www.kernel.org/pub/tools/crosstool/files/bin'
> > -        versions = ['7.3.0', '6.4.0', '4.9.4']
> > +        versions = ['8.1.0', '7.3.0', '6.4.0', '5.5.0', '4.9.4', '4.9.0', 
> > '4.8.5', '4.8.0', '4.7.3', '4.6.3', '4.6.2', '4.6.1', '4.5.1', '4.2.4']
> 
> with 4c58d273e0f2cc21821c1de32494abd5de411d9b we removed the older and
> unneeded versions. So it doesn't make sense to add them again.
> 
> Also did you a test run on Travis CI to verify that all archs still
> compile where a 8.1.0 toolchain is available? Travis CI will
> automatically use the latest avaiable toolchain for each arch. Possible
> new warnings or errors need to be fixed before doing the switch to 8.1.0.

Agreed.  Are you using buildman outside of U-Boot where you have a
usecase for adding in old versions / other architectures? I do want to
move up to 8.1.0 but I'm sure we have warnings to fix before we can do
that.  I _think_ I even posted a link to what was failing a while ago
and fixed a few things, but there's some harder to solve problems left.

-- 
Tom

Attachment: signature.asc
Description: PGP signature

_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot

Reply via email to