From: Hongxu Jia <hongxu.jia@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
Zhenhua Luo <zhenhua.luo@nxp.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: Status of M3
Date: Tue, 8 Mar 2016 16:09:17 +0800 [thread overview]
Message-ID: <56DE88AD.7090902@windriver.com> (raw)
In-Reply-To: <1457086698.2804.9.camel@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 1917 bytes --]
On 03/04/2016 06:18 PM, Richard Purdie wrote:
> On Fri, 2016-03-04 at 09:41 +0000, Zhenhua Luo wrote:
>>> * meta-fsl-ppc breaks on eudev change (patch pending)
>>> * meta-fsl-ppc breakage blocks AB artefact publishing
>> [Luo Zhenhua-B19537] The eudev patch is merged, http://git.yoctoproje
>> ct.org/cgit/cgit.cgi/meta-fsl
>> -ppc/commit/?id=2642cf5e8a6f8d11603acf016b8c075ebce00ec0, is there
>> any other blocker issue?
> Thanks, I appreciate getting that sorted!
>
> Unfortunately there is something else not quite right with meta-fsl
> -ppc:
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-fsl-ppc/buil
> ds/667
Hi Richard,
In the log, we have do_configure failed on python3:
...
| checking for the platform triplet based on compiler characteristics...
powerpc-linux-gnuspe
| configure: error: internal configure error for the platform triplet,
please file a bug report
| NOTE: The following config.log files may provide further information.
...
vim configure.ac in python3 source
...
852 if test x$PLATFORM_TRIPLET != x && test x$MULTIARCH != x; then
853 if test x$PLATFORM_TRIPLET != x$MULTIARCH; then
854 AC_MSG_ERROR([internal configure error for the platform
triplet, please file a bug report])
855 fi
856 fi
...
In this case, PLATFORM_TRIPLET is powerpc-linux-gnuspe, and MULTIARCH is
MULTIARCH=$($CC --print-multiarch 2>/dev/null), and both of them are not
equivalent.
On my local build with MACHINE = "qemux86-64", the MULTIARCH is empty.
On my local build with MACHINE = "p1022ds", $CC --print-multiarch
powerpc-linux-gnuspev1
Extra 'v1' casued the failure.
I am going to see what happen on 'v1', file [YOCTO #9226] to trace it
//Hongxu
> Seems something is not working in python3 do_configure? Everything else
> is building python3 fine so not sure what is wrong there.
>
> Cheers,
>
> Richard
[-- Attachment #2: Type: text/html, Size: 3179 bytes --]
next prev parent reply other threads:[~2016-03-08 8:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 14:23 Status of M3 Richard Purdie
2016-03-03 15:54 ` Flanagan, Elizabeth
2016-03-04 9:41 ` Zhenhua Luo
2016-03-04 10:18 ` Richard Purdie
2016-03-08 8:09 ` Hongxu Jia [this message]
2016-03-14 6:12 ` Zhenhua Luo
2016-03-14 6:46 ` Zhenhua Luo
2016-03-04 22:51 ` Richard Purdie
2016-03-04 23:34 ` Burton, Ross
2016-03-04 23:47 ` Burton, Ross
2016-03-05 0:09 ` Burton, Ross
2016-03-05 1:10 ` Burton, Ross
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=56DE88AD.7090902@windriver.com \
--to=hongxu.jia@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=zhenhua.luo@nxp.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.