Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [arc-buildroot] [autobuild.buildroot.net] Your build results for 2017-11-15
Date: Fri, 17 Nov 2017 09:06:47 +0100	[thread overview]
Message-ID: <20171117090647.4f104447@windsurf.lan> (raw)
In-Reply-To: <1510851029.31683.28.camel@synopsys.com>

Hello,

On Thu, 16 Nov 2017 16:50:30 +0000, Alexey Brodkin wrote:

> > ?????????arc |???????????????????????qt-4.8.7 | https://urldefense.proofpoint.com/v2/url?u=http-3A__autobuild.buildroot.net_results_f92fb57954904d55
> > 839ecc7e0759f52869fb8987&d=DwICAg&c=DPL6_X_6JkXFx7AXWqB0tg&r=Z74rKOsEpOUneCxYxwKcXHwrAmW8mJhNZjcWnDDJI2U&m=PyZ3d9KImQtwJn7aAlpsgbrtVTFuIem1QqiTGlZkk
> > fE&s=YR3T_mxXLqDkCWBrYCkWPkZcIItCeTYfI8mnL3siESE&e=
> > ?????????arc |???????????????????????qt-4.8.7 | https://urldefense.proofpoint.com/v2/url?u=http-3A__autobuild.buildroot.net_results_0d14e112d5ca94cf
> > 36cbd2605d270215236ffbde&d=DwICAg&c=DPL6_X_6JkXFx7AXWqB0tg&r=Z74rKOsEpOUneCxYxwKcXHwrAmW8mJhNZjcWnDDJI2U&m=PyZ3d9KImQtwJn7aAlpsgbrtVTFuIem1QqiTGlZkk
> > fE&s=_dHTQWl51LzxdleE3rcayzRk1v03T7kC6mFmqrmLj3g&e=
> > ?????????arc |???????????????????????qt-4.8.7 | https://urldefense.proofpoint.com/v2/url?u=http-3A__autobuild.buildroot.net_results_4634366b7dfea6d6
> > f11ae4d4410e35beed80f9e7&d=DwICAg&c=DPL6_X_6JkXFx7AXWqB0tg&r=Z74rKOsEpOUneCxYxwKcXHwrAmW8mJhNZjcWnDDJI2U&m=PyZ3d9KImQtwJn7aAlpsgbrtVTFuIem1QqiTGlZkk
> > fE&s=kxc6E07u2PjhognKYoc-m1pEszYqY_uZUCAsvmnnw4c&e=  
> 
> All build above failed on your "gcc112" machine and we cannot reproduce the same problem locally
> on CentOS 7.x machines.
> 
> I remember you mentioned one of your build servers is non-x86 machine.
> Is this the one? If that's a flavour of x86 still what is its Linux distro?
> 
> BTW maybe it worth adding not only host name but its architecture and distro version in Autobuilder artifacts?

All these errors indeed occur on ppc64le. I have already started
investigating this qt-4.8.7 issue. I reproduced it on gcc112, and
started looking into it. The issue is that for some reason, qt uses the
target compiler to build qmake, and therefore later fails to run qmake.

Interestingly, this doesn't happen if the target architecture is ARM.
If the target architecture is ARM, Qt says:

====
Determining system architecture...
(Linux:3.10.0-514.10.2.el7.ppc64le:ppc64le) 64-bit PowerPC (powerpc)
    'arm' is supported
    'powerpc' is supported
System architecture: 'arm'
Host architecture: 'powerpc'
====

So, System architecture != Host architecture, and therefore it uses the
host compiler to build qmake, and everything is fine.

But with Xtensa or ARC as the target architecture, I get:

====
Determining system architecture...
(Linux:3.10.0-514.10.2.el7.ppc64le:ppc64le) 64-bit PowerPC (powerpc)
    'powerpc' is supported
System architecture: 'powerpc'
Host architecture: 'powerpc'
Symbol visibility control enabled.
====

I.e, it thinks that the target architecture is PowerPC. Of course,
building Qt4 for ARC and Xtensa does work on other build machines, so
it's not just "Qt's configure script doesn't know about ARC or Xtensa".
I haven't yet figure out what's going on here.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

      parent reply	other threads:[~2017-11-17  8:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20171116070015.DBD4B20671@mail.free-electrons.com>
2017-11-16 16:50 ` [Buildroot] [arc-buildroot] [autobuild.buildroot.net] Your build results for 2017-11-15 Alexey Brodkin
2017-11-16 18:19   ` Peter Korsgaard
2017-11-17  8:06   ` Thomas Petazzoni [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171117090647.4f104447@windsurf.lan \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox