public inbox for gentoo-mips@lists.gentoo.org
 help / color / mirror / Atom feed
From: Stuart Longland <stuartl@longlandclan.id.au>
To: gentoo-mips@lists.gentoo.org
Subject: Re: [gentoo-mips] n64 stages for mipsel… any interest?
Date: Fri, 26 May 2017 17:28:52 +1000	[thread overview]
Message-ID: <4f1735b3-3615-ff62-a28f-1f92c71cc2f3@longlandclan.id.au> (raw)
In-Reply-To: <c722544e-bced-33cb-50a6-cd5957d8e026@longlandclan.id.au>


[-- Attachment #1.1: Type: text/plain, Size: 2936 bytes --]

On 14/05/17 15:56, Stuart Longland wrote:
> On 14/05/17 14:23, Joshua Kinard wrote:
>> On 05/13/2017 23:54, Stuart Longland wrote:
>>> Hi all,
>>>
>>> I've decided to dust off the old Lemote Yeeloong that I have kicking
>>> around for use as a throw-around netbook for on-the-road use.
>>>
>>> The aim is to have a machine that can do some basic web browsing (using
>>> a decent browser, dillo won't cut it), image editing, and maybe some
>>> amateur radio stuff (yes, done PSK31 with this beast before, operating
>>> as VK4MM, so it does work).

Well, a progress update… I have stage 1 and 2 tarballs built.  Yes,
that's after nearly a fortnight of compiling… with me putting the build
host into hibernate mode since the machine emulates a vacuum cleaner in
more ways than one!

It has just started the stage 3, then coughed up the following:
> Total: 30 packages (28 new, 2 reinstalls), Size of downloads: 8974 KiB
> 
>  * Error: circular dependencies:
> 
> (sys-libs/libcap-2.25:0/0::gentoo, ebuild scheduled for merge) depends on
>  (virtual/pam-0-r1:0/0::gentoo, ebuild scheduled for merge) (buildtime)
>   (sys-libs/pam-1.3.0:0/0::gentoo, ebuild scheduled for merge) (runtime)
>    (sys-libs/libcap-2.25:0/0::gentoo, ebuild scheduled for merge) (buildtime)
> 
> It might be possible to break this cycle
> by applying the following change:
> - sys-libs/pam-1.3.0 (Change USE: -filecaps)
> 
> Note that this change can be reverted, once the package has been installed.
> 
> !!! catalyst: run script failed.
> 
> 
> Traceback (most recent call last):
>   File "modules/generic_stage_target.py", line 1244, in run_local
>     "run script failed.",env=self.env)
>   File "/usr/lib64/catalyst/modules/catalyst_support.py", line 541, in cmd
>     raise CatalystError,myexc
> CatalystError
> None
> 
> !!! catalyst: Stage build aborting due to error.

Not sure if anyone else doing stage builds has struck that (haven't seen
it on x86 and AMD64).  I've just re-started Catalyst, hit ^Z at the
appropriate point and chrooted in myself to temporarily merge
sys-libs/pam (with USE=-filecaps as suggested) to see if I can work it
past that first blocker.

(You'd think portage would be smart enough to figure this out itself?
Ahh well.)

Seems strange though… maybe something is up with the n64 profiles, or
maybe something got missed at stage 2.  If that's all that goes wrong
though, I should have shiny new experimental n64 little-endian stages
for people in a week or so.

I might also see what's up with SMP support on this VM so I can throw a
bit more CPU muscle at the problem.  Seems a waste to have 5 host CPU
cores doing practically nothing and one getting flogged by a VM when the
same host will churn out x86 and AMD64 stages within a day.
-- 
Stuart Longland (aka Redhatter, VK4MSL)

I haven't lost my mind...
  ...it's backed up on a tape somewhere.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 321 bytes --]

  reply	other threads:[~2017-05-26  7:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-14  3:54 [gentoo-mips] n64 stages for mipsel… any interest? Stuart Longland
2017-05-14  4:23 ` Joshua Kinard
2017-05-14  5:56   ` Stuart Longland
2017-05-26  7:28     ` Stuart Longland [this message]
2017-06-06 13:10 ` Stuart Longland
2017-06-09  7:15   ` Stuart Longland

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=4f1735b3-3615-ff62-a28f-1f92c71cc2f3@longlandclan.id.au \
    --to=stuartl@longlandclan.id.au \
    --cc=gentoo-mips@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