public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: R0b0t1 <r030t1@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] cross compiling arm with 17 profiles.
Date: Sun, 17 Dec 2017 13:20:58 -0600	[thread overview]
Message-ID: <CAAD4mYifJ4qX3+sXvk_NgzTCLMa4yH_M75qiYzBqU+AWw3O0aw@mail.gmail.com> (raw)
In-Reply-To: <1513520087.1654.3.camel@gentoo.org>

Hello,

On Sun, Dec 17, 2017 at 8:14 AM, Mart Raudsepp <leio@gentoo.org> wrote:
> On P, 2017-12-17 at 16:50 +0800, Bill Kenworthy wrote:
>> Something I cant figure out:
>>
>> ARM is still on the 13 profiles - should an amd64 system used to
>> cross
>> compile for arm (Raspberry Pi's) be left on the 13 profiles or 17
>> will
>> work fine?
>
> ARM profiles are delayed to potentially fix CHOSTs together with the
> profile update. Though no-one is actively doing the work to my
> knowledge right now.
>
> I guess it could cause trouble from default PIE vs no PIE from native
> compiler, but I don't know enough about that field to know for sure.
>

If you know anything at all that is more than myself, so can you link
to past discussions that you are aware of?

> If you pay attention to any future CHOST changes and handle them
> yourself at the right time, you could manually choose the appropriate
> 17.0 arm profile as your symlink (it doesn't show up in eselect profile
> due to no profiles.desc entry, but should be there in profiles/). If
> changes are done, you might be caught a bit off-guard though at the
> time they are done though and I'm not sure what the effects of that
> would be either (probably not too bad).
>

My experience with ARM(64) is that it is mature enough that you can
expect @system to work unless proven otherwise. Lots of other packages
have failures.

Cheers,
     R0b0t1


      reply	other threads:[~2017-12-17 19:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-17  8:50 [gentoo-user] cross compiling arm with 17 profiles Bill Kenworthy
2017-12-17 14:14 ` Mart Raudsepp
2017-12-17 19:20   ` R0b0t1 [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=CAAD4mYifJ4qX3+sXvk_NgzTCLMa4yH_M75qiYzBqU+AWw3O0aw@mail.gmail.com \
    --to=r030t1@gmail.com \
    --cc=gentoo-user@lists.gentoo.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