1 |
On Friday, March 20, 2015 10:15:03 AM Michael Mair-Keimberger wrote: |
2 |
> On Thu, Mar 19, 2015 at 04:44:55PM -0400, Fernando Rodriguez wrote: |
3 |
> > On Thursday, March 19, 2015 9:11:02 PM Michael Mair-Keimberger wrote: |
4 |
> > > Hi List, |
5 |
> > > |
6 |
> > > For the last few weeks i was playing around with my newly acquired |
7 |
> > > raspberry pi 2. While it was pretty easy to setup a working gentoo |
8 |
> > > stage3 system i failed installing anything below the basic packages. |
9 |
> > > Generally my idea was building the arm packages on any system and |
10 |
> > > provide them as binary packages for other raspberry pi's (yeah, i |
11 |
> > > already bought my second rpi :D) |
12 |
> > > |
13 |
> > > At first, my idea was to build all the packages directly on the rpi. |
14 |
(with |
15 |
> > > /var/tmp & /usr/portage on a external harddisk). However, the compile |
16 |
> > > times are worse than i expected so i abandoned the idea. |
17 |
> > > |
18 |
> > > Next i've played around with crossdev. It sort of worked, but i never |
19 |
> > > could finish compiling xorg-server. (or basic system packages) Even |
20 |
> > > though i've started over and over with different settings, there were |
21 |
> > > always packages which failed to compile thus doesn't let me finish |
22 |
> > > xorg-server. I might look into it some other day but now i just wanted |
23 |
> > > something working. |
24 |
> > > |
25 |
> > > Now i'm playing with using qemu-arm [1][2] in order to compile the |
26 |
> > > packages inside a chroot. This is - so far - the most promising method |
27 |
> > > building packages, even though the compile times are worse than with |
28 |
> > > crossdev, but still better than directly on the rpi. |
29 |
> > > |
30 |
> > > So far i finally could compile xorg-server and also updated the whole |
31 |
> > > system, which, at this point, wasn't much anyway. My next goal was kde. |
32 |
> > > I've compiled about half of all packages which are required for |
33 |
> > > kdebase-meta, but now i'm stuck at kdelibs and i have no idea what's |
34 |
> > > wrong. |
35 |
> > > |
36 |
> > > The problem: |
37 |
> > > |
38 |
> > > The problem is, the compile doesn't fail - it just hangs/stops. At some |
39 |
> > > point (which seems to be random - it can stop anywhere between 1% and |
40 |
> > > 100% of the compile) the compile stops and does nothing. I've waited |
41 |
> > > hours, but nothing happened. |
42 |
> > > So far i tried lots of things, for example: |
43 |
> > > * MAKEOPTS="-j1" and/or FEATURES="-sandbox" |
44 |
> > > * also tried without building binary packages (-buildpkg) |
45 |
> > > * /var/tmp on tmpfs |
46 |
> > > * using: ebuild /usr/portage/kde-base/..../kdelibs....ebuild compile |
47 |
> > > * using python3.3 instead of default 2.7 |
48 |
> > > * moved it on a different system and tried building it there (again with |
49 |
> > > many different settings) |
50 |
> > > |
51 |
> > > Nothing worked, even though the build moved until 100% two times (-_-) |
52 |
> > > |
53 |
> > > I have no idea what the problem is. Even qtwebkit, which took way longer |
54 |
> > > to compile (about 3 hours) compiled on the first try. (which should |
55 |
> > > exclude temperate and/or resource problems) |
56 |
> > > I also don't think it's a problem with a use flag as the build stops |
57 |
> > > anywhere - i couldn't find a pattern. It seems to be completely random. |
58 |
> > > |
59 |
> > > Any ideas whats wrong or how to fix this? Any help would be much |
60 |
> > > appreciated as i'm out of ideas :( |
61 |
> > > |
62 |
> > > Thx |
63 |
> > > |
64 |
> > > [1] https://www.gentoo.org/proj/en/base/embedded/handbook/?part=1&chap=5 |
65 |
> > > [2] http://wiki.gentoo.org/wiki/Crossdev_qemu-static-user-chroot |
66 |
> > |
67 |
> > One possibility is swap trashing (running so low in RAM that every |
68 |
instruction |
69 |
> > takes several swaps to execute), especially with /var/tmp on tmpfs! This |
70 |
can |
71 |
> > happen even if you don't have a swap partition. Try with either more RAM |
72 |
or |
73 |
> > /var/tmp on a physical filesystem. |
74 |
> > |
75 |
> Usually /var/tmp is on the physical filesystem anyway. I've tried it |
76 |
> just once or twice because i though about a performance problem. RAM |
77 |
> shouldn't be a problem too as i'm having 16GB of RAM available. |
78 |
> > |
79 |
|
80 |
I would tell you to attach a debugger and see if you can tell why it's hanging |
81 |
but that may not be worth the trouble (since it'll be a child process that's |
82 |
hanging it'll be tricky to start qemu with the gdb stub just for that |
83 |
process). If you want to try it see: http://tinkering-is-fun.blogspot.com/2009/12/debugging-non-native-programs-with-qemu.html and |
84 |
search QEMU_GDB for the tricky part. |
85 |
|
86 |
Have you tried a different qemu version? |
87 |
|
88 |
-- |
89 |
Fernando Rodriguez |