User talk:Hiciu
From Openmoko
m |
|||
Line 24: | Line 24: | ||
--[[User:Hiciu|Hiciu]] 16:53, 23 March 2009 (UTC) | --[[User:Hiciu|Hiciu]] 16:53, 23 March 2009 (UTC) | ||
</blockquote> | </blockquote> | ||
+ | |||
+ | |||
+ | |||
+ | I thought I should give you a little status update, in case you're wondering what am I doing :). So, You were right, gcc-* glibc* etc. refuse to compile under sbox2/makepkg. But I suspect this is a problem with sbox2/cross-compiling. I have succesfully cross-compiled manually some packages which refuse to compile under sbox2 (I think it was gmp... or mpfr). I followed the PKGBUILD but with cross-compiler, and made the package with makepkg -R. This should be close to what you get with compiling in sbox2 and makepkg, I think. At least close enough for our needs because we're going recompile everything under the host/qemu. | ||
+ | |||
+ | But I have ran into an another problem, our toolchain seems to be missing some stuff to cross compile gcc-*. I think the easiest solution would be using another toolchain. But that would require recompiling everything. | ||
+ | |||
+ | I could provide the config for crosstool-ng to build the toolchain. So what's your opinion about using new toolchain and about the manually packaging some packages? --[[User:Beini|Beini]] 12:49, 27 March 2009 (UTC) |
Revision as of 14:49, 27 March 2009
Maybe we should start listing people involved what they can do to help.
I can probably help with building packages, but maybe it's best to wait for the qemu image for that.
I can also help with providing PKGBUILDs for openmoko specific stuff ( fso, shr apps, zhone etc..).
I also started looking at patches etc. what we probably need (soft float etc.) and editing the PKGBUILDs for them. Is someone already doing this or is there a reason I shouldn't do it? :) I see if I can get the toolchain setup for them. --Beini 22:20, 17 March 2009 (UTC)
I agree. But first of all we should find someone who can lead this thing, someone with leadership capacity. I think I'm not good person for this :). Maybe you? Or we could take someone from Openmoko community, or find someone on Arch forums: http://bbs.archlinux.org/viewtopic.php?pid=461139.
For now I'm missing few important packages (gcc, glibc and other "big" things). After them I will make qemu image and everything should move on. --Hiciu 17:22, 18 March 2009 (UTC)
I did make a new thread on Arch forums : http://bbs.archlinux.org/viewtopic.php?id=67836. --Beini 19:45, 18 March 2009 (UTC)
ok.. I've made qemu image with Arch x86, scratchbox2, crosscompiler and all other stuff needed to build packages. 992Mb, bzipped, md5: 53314cdef85b1754c7fedd5dc572b221, md5 after bzip -d: e56c1a3dc5f2ad19003f37c62a1207ad.
wget http://hiciu.rootnode.net/download/ArchArmDev.img.bz2
bzip -d ArchArmDev.img
qemu -m 512 -hda ArchArmDev.img -redir tcp:5555::22
I'm stuck on gcc-* and glibc packages...
--Hiciu 16:53, 23 March 2009 (UTC)
I thought I should give you a little status update, in case you're wondering what am I doing :). So, You were right, gcc-* glibc* etc. refuse to compile under sbox2/makepkg. But I suspect this is a problem with sbox2/cross-compiling. I have succesfully cross-compiled manually some packages which refuse to compile under sbox2 (I think it was gmp... or mpfr). I followed the PKGBUILD but with cross-compiler, and made the package with makepkg -R. This should be close to what you get with compiling in sbox2 and makepkg, I think. At least close enough for our needs because we're going recompile everything under the host/qemu.
But I have ran into an another problem, our toolchain seems to be missing some stuff to cross compile gcc-*. I think the easiest solution would be using another toolchain. But that would require recompiling everything.
I could provide the config for crosstool-ng to build the toolchain. So what's your opinion about using new toolchain and about the manually packaging some packages? --Beini 12:49, 27 March 2009 (UTC)