Am Mittwoch, 4. August 2010, 12:30:02 schrieb Kai Ruottu: > 4.8.2010 10:00, Timo Jyrinki kirjoitti: > > 2010/8/3 Kai Ruottu<kai.ruo...@wippies.com>: > >> a cross GCC should be?" tells what is wrong... There aren't any binutils > >> installed for the the cross GCC in the i586-meego-linux hosted > >> crosstoolchains! The binutils like 'armv7l-meego-linux-gnueabi-as' and > >> 'armv7l-meego-linux-gnueabi-ld' for the human user is there but no bare > >> name copies/links/symlinks, 'as' and 'ld', of them for the GCC where > >> GCC expects them to be :( > > > > Yep. I was now able to fill up enough gasoline to do the compilation. > > I was just side-tracked by the fact that the error message was > > reported around here and not dismissed directly a month back. > > Ok, the place where the binutils 'make install' puts the bare-name > binutils is the '$prefix/$target/bin', so they should be in the > '/opt/cross/armv7l-meego-linux-gnueabi/bin' after the original > install. When making a RPM including them was somehow forgotten...
This is probably a packaging bug. These packages need some review. > When there was that broken 'libgcc.a' and maybe other bugs too, a > replacement and a model of "normal" - somehow like the MADDE one - > install scheme where $prefix (for cross host stuff) and $sysroot > (for native target stuff) are separate places, is downloadable as: > > http://karuottu.wippiespace.com/public/cross-tools-armv7l-meego.tar.bz2 How do your ./configure look like for binutils and gcc ? Best, Jan-Simon _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
