[13:35] * ogra wonders what lool thinks about https://wiki.ubuntu.com/ARM/BuildEABIChroot :) [13:39] ogra: that's cool :) did you include debootstrap support for that or? [13:39] no, just a wrapper script that calls first and second stage separately and sets --arch armel [13:40] A patch for qemu exists at http://qemu-arm-eabi.sourceforge.net/ to enable EABI support in qemu-arm [13:40] <- thats so outdated :P [13:40] right [13:40] suihkulokki, ?? [13:40] is there a newer one ? [13:41] (that applies to 0.10.x) [13:41] EABI is supported even before 0.10.x [13:41] weird [13:42] ogra: ah, but it copies in the qemu-arm static binary into the target temporarily i presume [13:42] right [13:42] not temporarily, else you couldnt chroot :) [13:42] ah yes === cbrake_away is now known as cbrake [13:47] suihkulokki, i find it intresting that i could never use qemu-arm properly then ... given that we had 0.10 in jaunty already [14:09] ogra: not really interesting.. just different (fixed in git head) issue [14:10] ah [14:11] using git head highly recommended at the moment, as it will turn 0.11 any time now [14:29] ogra: I think that it's nice but not good enough for package builds [14:29] lool, for home use its surely good [14:29] my mesa build finished in about 2h [14:30] on my laptop [14:30] I just don't trust it [14:30] so if you want to do a pbuilder testbuild on armel before uploading etc thats surely a good way [14:30] i wouldnt use it as a buildd :) [14:30] Right [14:31] and i dont know how it will behave with neon and v7 === amitk_ is now known as amitk [14:32] That's not an issue [14:32] its surely better than cross compiling the whole dep chain of gnome to testbuild a single gnome package in a cross compiler env [14:33] syscalls don't map one to one on armel and x86; I wouldn't trust that they are all properly wrapped and you might end up building packages which assume support for stuff which isn't truly supported or vice-versa [14:33] yeah, its surely not for full production use [14:34] but its *faaaaast* :) [15:36] hello! I'm trying to build an arm-rootfs using rootstock (tried the older script from wiki, too), but it just hangs after starting qemu saying "installing core packages" [15:36] it doesnt hang [15:36] its just very slow inside the VM [15:37] really? how long does it do "nothing" (or at least saying nothing"? [15:37] I just got curious after half an hour or so [15:37] give it time ... building the base system completely usually takes about 50min [15:37] the apt stage later is faster [15:37] oh, okay. maybe on my host it will take some hours :) [15:38] I will wait. thanks a lot [15:38] the 50min are on my laptop ... core2duo 1.8GHz [15:38] slower machines will indeed take a bit longer [15:39] okay. well, another question. what's a minimal system just providing X? I am currently trying xubuntu-desktop [15:40] minimal system is really minimal ... [15:40] just enough to boot [15:41] if you only want boot and X add xorg [15:41] a lightweight desktop would be lxde [15:42] there are some examples on the RootfsFromScratch wikipage [15:44] hm, I think I'll stick with xubuntu-desktop first, and maybe remove unneeded things later [15:48] the created image should be bootable on an OMAP-board, right? [15:51] its just a tgz [15:51] yes, the packages should all run on OMAP [15:52] okay, I'll try it later when the system is fully configured [16:46] ogra: The script did not take too long, it booted the system a few minutes ago and is unpacking the packages now [16:46] ah, good [16:52] ogra: Do you know what compiler was used to build the armel packages? [16:53] gcc [16:53] depending on which release you use 4.3 or 4.4 [16:54] okay, thanks. that should fit with the other applications I plan to use [19:10] ogra: "--seed build-essential,openssh-server" took about 15 minutes to build the full rootfs on an core2@2,66GHz [19:11] sounds about right [19:12] but the system does not boot, last messages is: " * Starting OpenBSD Secure Shell server sshd [ OK ] [19:12] chown: failed to get attributes of `/var/log/dmesg': Stale NFS file handle [19:12] chmod: failed to get attributes of `/var/log/dmesg': Stale NFS file handle [19:12] /etc/rc2.d/S70bootlogs.sh: 61: cannot create /var/log/dmesg: Stale NFS file handle [19:12] chgrp: cannot access `/var/log/dmesg': Stale NFS file handle [19:12] mv: accessing `/var/log/udev': Stale NFS file handle [19:13] " [19:13] I don't understand why it seems to look for stuff on NFS at all... [19:13] * ogra points to https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/391094 [19:13] Launchpad bug 391094 in glibc "the "stale NFS file handle" error should be reworded" [Undecided,New] [19:13] when did you check out the script ? [19:14] an hour ago or so [19:14] rev17 I think [19:14] there was a bug where it was not properly unmounting the VM image [19:15] you could do an fsck ... but its worrying that you still see it [19:16] did you build for jaunty or karmic ? [19:16] I built jaunty [19:17] hrm, i checked that, thats bad [19:17] the build was absolutely fresh, first boot [19:17] yeah [19:17] and I unmounted the image to where I unpacked rootfs correctly [19:17] it didnt unmount the VM cleanly and then rolled a tarball that contained uncleared inodes [19:18] you will see stuff being mentioned in the logfile i guess [19:18] the best you can do is an fsck [19:19] it will clean up the dangling inodes [19:19] i will look deeper into that on the weekend [19:19] i'm 100% sure its fixed in karmic, but i only tested one run under jaunty [19:21] the image had wrong inodes, strange [19:21] not if you think about it :) [19:22] because qemu was killed while the fs was mounted? [19:22] the image is built in a vm ... the vm isnt shut down properly ... then the image is mounted again and a tarball is created from the content [19:22] but it still hangs with " * Starting OpenBSD Secure Shell server sshd [ OK ] [19:22] chown: failed to get attributes of `/var/log/dmesg': No such file or directory [19:22] chmod: failed to get attributes of `/var/log/dmesg': No such file or directory [19:22] " [19:23] you can create that file it shouldnt stop you from booting [19:23] -rw-r----- 1 root adm 50862 2009-07-17 13:44 /var/log/dmesg [19:24] should look like that [19:24] well, but that should not stop the boot process, right? [19:24] right [19:24] * ogra has to go soon [19:25] hmm 15 minutes? are you using amd64 or i386 on it robert__? its still around 3.5 hours for a build-essential,openssh-server karmic on a 2.4ghz turion x2 herex2 for some reason [19:26] Sarvatt_: maybe 20 minutes, but not more [19:26] debian is 20 minutes though [19:26] amd64's qemu-syste-arm might run slower [19:26] it's i386 [19:26] yeah thats what imthinking [19:26] wow, cant type today :) [19:27] anyway, i really have to go now ... i'll look into that tomorrow [19:27] ogra: strange, /var/log/dmesg exists in the image [19:27] thats a pretty crazy difference, i'll try it on i386 [19:27] all right, I'll try to get it running [19:28] if you cant get it fixed, worst case use build-arm-rootfs for jaunty [19:28] I will try that, too. just 15 minutes ;) [19:29] ah, I tried jaunty. you mean k... (forgot the name :) ) [19:32] can karmic only be run with cortex-a8 as cpu? I need to use is for an 926 [19:35] you can use it for that now but its going to change soon to be armv6+,, would need to change rootstock around a bit because i think ogra moved it over to cortex in there [19:39] yes, just a line to change. I was just wondering if the binary format changed for karmic [19:39] not yet [19:40] still armv5t arch default for gcc in karmic [19:42] by the way, what do you use ubuntu/arm for? are there tablet pcs strong enough to run ubuntu on yet? [19:43] i wish! [19:44] i'm just using it for a build environment for a future system and to check for problems in pixman from git here [19:44] so it's basically a "proof of concept" project at the moment? [19:46] qemu is running so slow on my amd64 machines that i've resorted to using karmic in a chroot on my htc dream phone for all of that :D [19:47] I'm planning to profile some applications on real hardware (OMAP developer board) [19:47] hm, I have an htc himalaya laying around here, but never managed to run linux on it [19:47] just managed to boot a kernel [19:52] debian might be a better fit for both of those, jaunty and karmic arm are using arch armv5t with cortex-a8 tune for everything and i'm just guessing that would make things slower on the older hardware [19:54] is there a list of CFLAGS used? [20:11] ogra: karmic rootfs also hangs after "* Starting OpenBSD Secure Shell server sshd [ OK ]" === bizkut-miau is now known as bizkut [20:18] I tried removing the symlinkgs in /etc/rc2.d which started services after sshd, without success [20:18] I'll continue tomorrow. see you! [20:43] ogra: holy crap, build-arm-eabi-chroot is great! thanks for packaging that! === Omegamoon is now known as Omegamoon|kraftw === Omegamoon|kraftw is now known as Omegamoon === cbrake is now known as cbrake_away === Sarvatt_ is now known as Sarvatt