This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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


On Mon, 2016-12-12 at 23:57 +0000, Joseph Myers wrote:
> On Mon, 12 Dec 2016, Steve Ellcey wrote:
> 
> > 
> > That seems reasonable.  What arch names would you suggest for the
> > ILP32
> > builds?  I would probably go with aarch64_ilp32 and
> > aarch32_be_ilp32
> > unless there was a reason to use something else.
> I'd probably use variant names rather than changing the architecture name 
> in this case.

OK, I think I see how to implement that (based on examples like armeb
and m68k).  But how do you specify a variant to build on the command
line?  I.e. if I wanted to build just the coldfire variant of m68k,
what would my build-many-glibcs.py call look like to build that one
target/variant.

'build-many-glibcs.py compilers m68k-linux-gnu' would presumably just
build the default variant and not coldfire.

Steve Ellcey
sellcey@caviumnetworks.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]