>>> Emerging : portage://sys-devel/binutils-hppa64-2.37_p1-r2:run?{[]}

These are the packages that would be merged, in order:

Calculating dependencies... done!

 └─step  1─┤ unmask  portage://sys-devel/binutils-hppa64-2.37_p1-r2
             │ keyword portage://sys-devel/binutils-hppa64-2.37_p1-r2 (**)

 └─step  2─┤ download  portage://sys-devel/binutils-hppa64-2.37_p1-r2
             │           └─ file ─┤ 31.21 Kb  	 binutils-2.37_p1-patches-2.tar.xz
             │                    │ 21.93 Mb  	 binutils-2.37_p1.tar.xz

 └─step  3─┤ install   portage://sys-devel/binutils-hppa64-2.37_p1-r2 (**)
             │           └─ conf ─┤ USE = "nls pgo* plugins (-cet) (-default-gold) (-gold) -doc -multitarget -static-libs -test -vanilla"
             │                    │ SLOT = "2.37"

 └─step  4─┤ run     portage://sys-devel/binutils-hppa64-2.37_p1-r2

Total: 5 actions (1 unmask, 1 keyword, 1 download, 1 install, 1 run), grouped into 4 steps.
       21.96 Mb to be downloaded.


>>> Assumptions taken during proving & planning:

  Keyword acceptance (1 package):
  Add to /etc/portage/package.accept_keywords:
    sys-devel/binutils-hppa64 **

  Package unmask (1 package):
  Add to /etc/portage/package.unmask:
    =sys-devel/binutils-hppa64-2.37_p1-r2