| View previous topic :: View next topic |
| Author |
Message |
ZappingLinux
Tux's lil' helper
Joined: 13 Oct 2017
Posts: 117
Location: Delft, Netherlands
|
 Posted: Mon Oct 30, 2017 1:50 pm Post subject: First Time Gentoo Linux On Raspberry Pi |
 |
|
Update:
I read as much as I could on crossdev and I think I get the most general lines. Still wouldn't call myself an expert on it though. Also I accepted the fact that I can't know everything in the world and added
| Code: | | =sys-libs/binutils-libs-2.29.1-r1 ~amd64 |
to my /etc/portage/package.accept_keywords file. If someone could tell me why this is necessary I would love to know because I had to do this before but never quite grasped the process and what it does.
Hey Guys!
So I really wanted to install gentoo linux on a raspberry pi because I love the distribution and why not right? So I am following this page:
https://wiki.gentoo.org/wiki/Raspberry_Pi_3_64_bit_Install#Installation_Overview
But I feel like I am missing some information and I was wondering if anyone knew.
So when I run:
| Code: | | crossdev -t aarch64-unknown-linux-gnu |
It tells me binutils have failed. I'd like to know why so I add a bunch of flags in order to figure out where it halts:
| Code: | | crossdev -t -v aarch64-unknown-linux-gnu --genv |
This tells me:
| Code: |
udo crossdev -v -t aarch64-unknown-linux-gnu --genv
-----------------------------------------------------------------------------------------------
* crossdev version: 20151026
* Host Portage ARCH: amd64
* Target Portage ARCH: arm64
* Target System: aarch64-unknown-linux-gnu
* Stage: 4 (C/C++ compiler)
* ABIs: arm64
* binutils: binutils-[latest]
* gcc: gcc-[latest]
* headers: linux-headers-[latest]
* libc: glibc-[latest]
* CROSSDEV_OVERLAY: /var/lib/layman/dantrell-gnome-3-24
* PORT_LOGDIR: /var/log/portage
* PORTAGE_CONFIGROOT:
* Portage flags: -v
_ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~
* leaving sys-devel/binutils in /var/lib/layman/dantrell-gnome-3-24
* leaving sys-devel/gcc in /var/lib/layman/dantrell-gnome-3-24
* leaving sys-kernel/linux-headers in /var/lib/layman/dantrell-gnome-3-24
* leaving sys-libs/glibc in /var/lib/layman/dantrell-gnome-3-24
* leaving sys-devel/gdb in /var/lib/layman/dantrell-gnome-3-24
* leaving metadata/layout.conf alone in /var/lib/layman/dantrell-gnome-3-24
_ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~
* Log: /var/log/portage/cross-aarch64-unknown-linux-gnu-binutils.log
* Emerging cross-binutils ...
* IMPORTANT: 2 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
These are the packages that would be merged, in order:
Calculating dependencies . .... done!
[ebuild U ~] sys-libs/binutils-libs-2.29.1-r1:0/2.29.1::gentoo [2.28.1:0/2.28.1::gentoo] USE="nls -64-bit-bfd -multitarget -static-libs" ABI_X86="(64) -32 (-x32)" 28,459 KiB
[ebuild N ~] cross-aarch64-unknown-linux-gnu/binutils-2.29.1-r1:2.29.1::dantrell-gnome-3-24 USE="cxx nls -multitarget -static-libs {-test} -vanilla" 21 KiB
Total: 2 packages (1 upgrade, 1 new), Size of downloads: 28,480 KiB
!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:
sys-libs/binutils-libs:0
(sys-libs/binutils-libs-2.29.1-r1:0/2.29.1::gentoo, ebuild scheduled for merge) pulled in by
>=sys-libs/binutils-libs-2.29.1 required by (cross-aarch64-unknown-linux-gnu/binutils-2.29.1-r1:2.29.1/2.29.1::dantrell-gnome-3-24, ebuild scheduled for merge)
^^ ^^^^^^
(sys-libs/binutils-libs-2.28.1:0/2.28.1::gentoo, installed) pulled in by
sys-libs/binutils-libs:0/2.28.1=[abi_x86_64(-)] required by (x11-libs/cairo-1.14.8:0/0::gentoo, installed)
^^^^^^^^^^
It may be possible to solve this problem by using package.mask to
prevent one of those packages from being selected. However, it is also
possible that conflicting dependencies exist such that they are
impossible to satisfy simultaneously. If such a conflict exists in
the dependencies of two different packages, then those packages can
not be installed simultaneously.
For more information, see MASKED PACKAGES section in the emerge man
page or refer to the Gentoo Handbook.
The following keyword changes are necessary to proceed:
(see "package.accept_keywords" in the portage(5) man page for more details)
# required by x11-libs/cairo-1.14.8::gentoo
# required by @selected
# required by @world (argument)
Use --autounmask-write to write changes to config files (honoring
CONFIG_PROTECT). Carefully examine the list of proposed changes,
paying special attention to mask or keyword changes that may expose
experimental or unstable packages.
* In order to avoid wasting time, backtracking has terminated early
* due to the above autounmask change(s). The --autounmask-backtrack=y
* option can be used to force further backtracking, but there is no
* guarantee that it will produce a solution.
* binutils failed :(
*
* If you file a bug, please attach the following logfiles:
* /var/log/portage/cross-aarch64-unknown-linux-gnu-info.log
* /var/log/portage/cross-aarch64-unknown-linux-gnu-binutils.log.xz
* /var/tmp/portage/cross-aarch64-unknown-linux-gnu/binutils*/temp/binutils-config.logs.tar.xz
|
So I know that I am an idiot and that I should read the page on crossdev to figure out how it works exactly which I will do but I just wanted to leave this here first. So it basically tells me I need to add
| Code: | | =sys-libs/binutils-libs-2.29.1-r1 ~amd64 |
to the /etc/portage/package.accept_keywords file. But why? How can I extract the answer to "why" out of this list?
Last edited by ZappingLinux on Mon Oct 30, 2017 4:31 pm; edited 2 times in total |
|
| Back to top |
|
 |
xaviermiller
Bodhisattva
Joined: 23 Jul 2004
Posts: 8723
Location: ~Brussels - Belgique
|
| Posted: Mon Oct 30, 2017 1:58 pm Post subject: |
|
|
Moved from Other Things Gentoo to Gentoo on ARM.
_________________
Kind regards,
Xavier Miller |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54673
Location: 56N 3W
|
| Posted: Mon Oct 30, 2017 6:03 pm Post subject: |
|
|
ZappingLinux,
Do not confuse | Code: | | sys-libs/binutils-libs |
and | Code: | | cross-aarch64-unknown-linux-gnu/binutils |
The former runs on your build host and is used for building things that will run on the build host.
The latter is used to build things on the build host that will run on the aarrch64 target.
The versions are not linked and can be keyworded separately.
| Code: | | * crossdev version: 20151026 |
is an old version of crossdev. Try the testing version.
Pastebin | Code: | | * Log: /var/log/portage/cross-aarch64-unknown-linux-gnu-binutils.log |
so we can see what broke.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
ZappingLinux
Tux's lil' helper
Joined: 13 Oct 2017
Posts: 117
Location: Delft, Netherlands
|
| Posted: Mon Oct 30, 2017 6:08 pm Post subject: |
|
|
The pastebin of /var/log/portage/cross-aarch64-unknown-linux-gnu-binutils.log is 1.4 MB. So I can't post it there or here. After I added the keywords to package.accept_keywords I ran crossdev -t aarch64-unknown-linux-gnu again and it went on its merry way. But to be honest I have no clue what I did :S
Last edited by ZappingLinux on Mon Oct 30, 2017 6:23 pm; edited 1 time in total |
|
| Back to top |
|
|
ZappingLinux
Tux's lil' helper
Joined: 13 Oct 2017
Posts: 117
Location: Delft, Netherlands
|
| Posted: Mon Oct 30, 2017 6:20 pm Post subject: |
|
|
| NeddySeagoon wrote: | ZappingLinux,
Do not confuse | Code: | | sys-libs/binutils-libs |
and | Code: | | cross-aarch64-unknown-linux-gnu/binutils |
The former runs on your build host and is used for building things that will run on the build host.
The latter is used to build things on the build host that will run on the aarrch64 target.
The versions are not linked and can be keyworded separately.
| Code: | | * crossdev version: 20151026 |
is an old version of crossdev. Try the testing version.
Pastebin | Code: | | * Log: /var/log/portage/cross-aarch64-unknown-linux-gnu-binutils.log |
so we can see what broke. |
Okay so I have had this problem before where I just don't know how to try out a testing version of a package (or a driver, im the nvidia guy) and I kind of got lost along the way so I thought I shouldnt break something even more than it might be already. So what have I done by adding those keywords?
Update:
I sent you a pm with a link to the github repo which I will post here too I guess. https://raw.githubusercontent.com/CryCic4da/GentooLogs/master/cross-aarch64-unknown-linux-gnu-binutils.log |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54673
Location: 56N 3W
|
| Posted: Mon Oct 30, 2017 6:44 pm Post subject: |
|
|
ZappingLinux,
The link works but it shows that both binutils worked.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
ZappingLinux
Tux's lil' helper
Joined: 13 Oct 2017
Posts: 117
Location: Delft, Netherlands
|
| Posted: Mon Oct 30, 2017 6:52 pm Post subject: |
|
|
| NeddySeagoon wrote: | ZappingLinux,
The link works but it shows that both binutils worked. |
In that case I am extremely confused as to why it failed when i first ran it. :S |
|
| Back to top |
|
|
|
Gentoo on ARM
