From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: Leno Hou <lenohou@gmail.com>,
gentoo-powerpc@lists.gentoo.org,
"Anthony G. Basile" <blueness@gentoo.org>
Subject: Re: [gentoo-dev] Introduce ppc64le architecture into gentoo ! please share your comments
Date: Wed, 12 Aug 2015 23:19:11 -0400 [thread overview]
Message-ID: <20150813031911.GD8277@vapier> (raw)
In-Reply-To: <CANRgnN1E2KM75gtgeOggZt9tTj=Hn=3ZsNyKeu=k=OVysbf7dA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1346 bytes --]
On 13 Aug 2015 07:58, 姜渠 wrote:
> 2015-08-12 15:47 GMT+08:00 Mike Frysinger:
> > On 12 Aug 2015 15:20, Leno Hou wrote:
> > >> 2. How to control endian difference via profiles ? i.e. *How to get
> > >> ppc64le as a full stage/profile along side ppc64* ?
> > >> Could you give me in detail ?
> >
> > >you probably want to create a new profile dir:
> > > profiles/arch/powerpc/ppc64/little-endian/
> > >then add a make.defaults file with the right CHOST defaults. as we find
> > >packages that have problems on little endian, that provides you a safe
> > >space to mask features too.
> >
> > >then create a new target for linux users:
> > >
> > profiles/default/linux/powerpc/ppc64/13.0/64bit-userland/little-endian/
> > >that'll inherit the arch/powerpc/ppc64/little-endian parent
>
> I tried this way and could merge some packages quite well, that's great
> and really helpful.
> But I still quite confused about the CHOST, such as if I couldn't compile
> "sandbox" successfully in this method, however when I tried to use ppc32's
> profile, it builds well without any errors (similar situation of other
> packages on ppc64's profile as well). What's that mean? how to fix this?
> Could you give me some details ?
w/out error messages it's hard to guess at what the problem is you're seeing.
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-08-13 3:19 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-11 9:22 [gentoo-dev] Introduce ppc64le architecture into gentoo ! please share your comments Leno Hou
2015-08-11 9:49 ` James Le Cuirot
2015-08-11 10:11 ` Leno Hou
2015-08-11 14:33 ` Ian Stakenvicius
2015-08-11 14:44 ` James Le Cuirot
2015-08-11 14:45 ` Anthony G. Basile
2015-08-12 3:50 ` Mike Frysinger
2015-08-12 7:20 ` Leno Hou
2015-08-12 7:47 ` Mike Frysinger
2015-08-12 8:30 ` Anthony G. Basile
2015-09-11 12:01 ` Leno Hou
2015-09-11 14:18 ` Ian Stakenvicius
2015-09-13 18:36 ` Mike Gilbert
2015-09-17 6:53 ` Leno Hou
2015-09-24 12:23 ` Leno Hou
2015-09-25 18:27 ` [gentoo-powerpc] " Luca Barbato
2015-09-26 19:16 ` Anthony G. Basile
2015-10-21 8:55 ` Kevin Zhao
2015-11-23 19:54 ` Richard Yao
2015-09-17 7:06 ` Leno Hou
2015-08-12 9:46 ` Shuai Zhao
2015-08-12 9:50 ` [gentoo-powerpc] " Luca Barbato
2015-08-12 23:58 ` 姜渠
2015-08-13 3:19 ` Mike Frysinger [this message]
2015-08-14 7:52 ` Leno Hou
2015-09-24 15:07 ` Mike Frysinger
2015-09-25 2:32 ` Leno Hou
2015-09-25 5:05 ` Mike Frysinger
2015-09-25 7:34 ` Anthony G. Basile
2015-09-25 9:09 ` Leno Hou
2015-09-25 10:59 ` Anthony G. Basile
2015-09-25 17:21 ` Anthony G. Basile
2015-08-12 3:50 ` Mike Frysinger
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=20150813031911.GD8277@vapier \
--to=vapier@gentoo.org \
--cc=blueness@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=gentoo-powerpc@lists.gentoo.org \
--cc=lenohou@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox