Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/4] Fix builds for MIPS64 N32
Date: Fri, 31 Jul 2015 11:59:21 +0100	[thread overview]
Message-ID: <1438340361.22462.22.camel@linuxfoundation.org> (raw)
In-Reply-To: <CALT56yNYwnwhV9MUSP+AXD7YcK05R=OzuJ+9-E68beWFhS8EjQ@mail.gmail.com>

On Wed, 2015-07-29 at 18:00 +0300, Dmitry Eremin-Solenikov wrote:
> > Recent check-ins have changed some things.  The compile side was working for a
> > while, but not the compilation side (using it).
> >
> > I've been working with RP on IRC, and he's come up with some additional patches.
> >  (including this set of 4..)
> >
> > So I think the set is fine, it's up to the other pieces that need to mesh with
> > this to produce the working SDK.
> 
> Ok. So what would be the plan then? If you need any additional tests
> from my side,
> I can provide them.

Sorry for the delays on this. I found several issues and ended up with
some quite subtle gcc changes to make all this work. I've put both our
changes into master-next. The local.conf testing setup I've been using
is:

MACHINE = "qemumips64"
require conf/multilib.conf
DEFAULTTUNE = "mips64-n32"
MULTILIBS = "multilib:lib64 multilib:lib32"
DEFAULTTUNE_virtclass-multilib-lib64 = "mips64"
DEFAULTTUNE_virtclass-multilib-lib32 = "mips32r2"

then the build/test commands:

bitbake core-image-minimal -c populate_sdk
bitbake core-image-minimal -c testsdk

The nice thing is the latter automated test part now passes for this
configuration (and its tests all three multilibs).

What remains is to run these changes through the autobuilder and make
sure nothing else breaks as a result of this patchset. I'm about to do
some business travel which means my ability to debug any further issues
will be limited, compiling toolchains on the laptop isn't realistic. I
may therefore need help in ironing out any further wrinkles or we'll
have to wait until I get back in a couple of weeks.

Cheers,

Richard



  reply	other threads:[~2015-07-31 10:59 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-01 14:02 [PATCH 0/4] Fix builds for MIPS64 N32 Dmitry Eremin-Solenikov
2015-07-01 14:02 ` [PATCH 1/4] arch-mips.inc: don't override TRANSLATED_TARGET_ARCH Dmitry Eremin-Solenikov
2015-07-01 14:02 ` [PATCH 2/4] packagegroups-cross-canadian: " Dmitry Eremin-Solenikov
2015-07-01 14:02 ` [PATCH 3/4] cross.bbclass: override MULTIMACH_TARGET_SYS Dmitry Eremin-Solenikov
2015-07-01 14:02 ` [PATCH 4/4] glibc: don't override TUNE_CCARGS for MIPS Dmitry Eremin-Solenikov
2015-08-15 19:34   ` Khem Raj
2015-08-15 23:15     ` Dmitry Eremin-Solenikov
2015-08-16  0:29       ` Khem Raj
2015-08-17 15:30         ` Dmitry Eremin-Solenikov
2015-08-18 15:05           ` Dmitry Eremin-Solenikov
2015-07-08 12:00 ` [PATCH 0/4] Fix builds for MIPS64 N32 Dmitry Eremin-Solenikov
2015-07-08 12:02   ` Richard Purdie
2015-07-08 12:42   ` Mark Hatle
2015-07-20 12:11     ` Dmitry Eremin-Solenikov
2015-07-20 15:47       ` Mark Hatle
2015-07-21  8:23         ` Dmitry Eremin-Solenikov
2015-07-21 14:31           ` Mark Hatle
2015-07-21 15:26             ` Mark Hatle
2015-07-22 15:48               ` Dmitry Eremin-Solenikov
2015-07-28 17:26               ` Dmitry Eremin-Solenikov
2015-07-29 14:58                 ` Mark Hatle
2015-07-29 15:00                   ` Dmitry Eremin-Solenikov
2015-07-31 10:59                     ` Richard Purdie [this message]
2015-07-31 15:47                       ` Dmitry Eremin-Solenikov

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=1438340361.22462.22.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=dbaryshkov@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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