Re: [RFC][PATCH 22/22] Add Infinity notes implementing td_ta_map_lwp2thr

[Szabolcs Nagy <szabolcs dot nagy at arm dot com>]

On 22/10/15 09:56, Gary Benson wrote:
> Adhemerval Zanella wrote:
> > > Em 21 de out de 2015, às 19:28, Gary Benson <gbenson@redhat.com> escreveu:
> > > Adhemerval Zanella wrote:
> > > > > On 21-10-2015 17:09, Gary Benson wrote:
> > > > > Adhemerval Zanella wrote:
> > > > > > AFAIK the only non-trivial build dependency for testing
> > > > > > is perl and I do not see a way forward to add another
> > > > > > interpreter dependency.  It will be even harder on
> > > > > > cross-compiling environment to do native testing with such
> > > > > > dependency.
> > > > >
> > > > > I8C and I8X run on the host, not the target.  You only need
> > > > > Python on the host.  It's probably already there :)
> > > > >
> > > > > And on the host, if you have Python and pip installed then you
> > > > > can install I8C and I8X with a single shell command.  It takes
> > > > > about 20 seconds on my <5Mbit connection and you don't need
> > > > > root access.
> > > >
> > > > That is not the case where you are bootstrapping on a platform
> > > > that does not have python enabled.
> > >
> > > Don't people usually cross-build to bootstrap new platforms?
> >
> > So the testing itself does not require to run Python natively? If it
> > is the case where you can the i8x tests in the build machine I agree
> > that it is not an impending reason.
>
> Neither the compile step nor the test step require Python to run
> natively.  I8C and I8X both run only on the build host.

the easiest way to run the glibc tests is to build it natively
(because the test system has assumptions about the host env that
is hard to match with the ssh+nfs cross test setup).

currently the test system depends on perl (for header conformance
tests and memory leak tests) which is already a pain.

python is another hard to build dependency and you have to make
sure that python language changes don't affect the behaviour.

i think this is not a critical issue since the build can succeed
without i8*, but it is worth noting.