Re: build-many-glibcs.py question (updating for multilibs on aarch64)

[Joseph Myers <joseph at codesourcery dot com>]

On Mon, 12 Dec 2016, Steve Ellcey wrote:

> @@ -126,9 +126,15 @@ class Context(object):
>          no_isolate = ('-fno-isolate-erroneous-paths-dereference'
>                        ' -fno-isolate-erroneous-paths-attribute')
>          self.add_config(arch='aarch64',
> -                        os_name='linux-gnu')
> +                        os_name='linux-gnu',
> +                        gcc_cfg=['--with-multilib-list=lp64,ilp32'],
> +                        glibcs=[{},
> +                                {'variant': 'ilp32', 'ccopts': '-mabi=ilp32'}])
>          self.add_config(arch='aarch64_be',
> -                        os_name='linux-gnu')
> +                        os_name='linux-gnu',
> +                        gcc_cfg=['--with-multilib-list=lp64,ilp32'],
> +                        glibcs=[{},
> +                                {'variant': 'ilp32', 'ccopts': '-mabi=ilp32'}])

Although building a multilib GCC is logically correct, it's probably not a 
good idea until the stable GCC, binutils and Linux kernel versions used in 
build-many-glibcs.py all have the required support for ILP32, as including 
ILP32 glibc in the same GCC build as LP64 would lose LP64 testing if 
missing kernel headers support for ILP32 results in the ILP32 build 
failing.

Thus, if missing kernel headers support makes the ILP32 build fail, the 
compiler builds for ILP32 should be kept separate until the ILP32 kernel 
headers support is in an actual kernel release, which is used by 
build-many-glibcs.py.

-- 
Joseph S. Myers
joseph@codesourcery.com