[MeeGo-dev] cross-armv7l-gcc, cross-armv5tel-gcc are not installable
Hi, The meego-core repository seems to provide some ARM cross compilers, but they don't install. For example: r...@meego-netbook-sdk:/# yum install cross-armv7l-gcc Repository meego-non-oss-debuginfo is listed more than once in the configuration Repository meego-non-oss-source is listed more than once in the configuration Setting up Install Process Resolving Dependencies --> Running transaction check ---> Package cross-armv7l-gcc.i586 0:4.4.2-2.3 set to be updated --> Processing Dependency: cpp = 4.4.2-2.3 for package: cross-armv7l-gcc-4.4.2-2.3.i586 --> Processing Dependency: libgomp = 4.4.2-2.3 for package: cross-armv7l-gcc-4.4.2-2.3.i586 --> Finished Dependency Resolution Error: Package: cross-armv7l-gcc-4.4.2-2.3.i586 (meego-core) Requires: libgomp = 4.4.2-2.3 Installed: libgomp-4.4.2-12.13.i586 (installed) Error: Package: cross-armv7l-gcc-4.4.2-2.3.i586 (meego-core) Requires: cpp = 4.4.2-2.3 Installed: cpp-4.4.2-12.13.i586 (installed) You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest I found a couple of references to this problem, but no answers which address the failure of these packages to install: http://forum.meego.com/showthread.php?t=582 http://comments.gmane.org/gmane.comp.handhelds.meego.devel/2367 Did I miss something, or is this simply a bug? Is anyone successfully using these? If no-one says "yes" I'll file a bug for their removal. -- Rohan ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] cross-armv7l-gcc, cross-armv5tel-gcc are not installable
'--skip-broken' as indication works? Or you can force install to have a try (please also install those cross-glibc/binutils)? > If no-one says "yes" I'll file a bug for their removal. Yes, please go ahead, but not for removal those but correct them. -Original Message- From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On Behalf Of Rohan McGovern Sent: Monday, June 28, 2010 12:29 PM To: meego-dev@meego.com Subject: [MeeGo-dev] cross-armv7l-gcc, cross-armv5tel-gcc are not installable Hi, The meego-core repository seems to provide some ARM cross compilers, but they don't install. For example: r...@meego-netbook-sdk:/# yum install cross-armv7l-gcc Repository meego-non-oss-debuginfo is listed more than once in the configuration Repository meego-non-oss-source is listed more than once in the configuration Setting up Install Process Resolving Dependencies --> Running transaction check ---> Package cross-armv7l-gcc.i586 0:4.4.2-2.3 set to be updated --> Processing Dependency: cpp = 4.4.2-2.3 for package: cross-armv7l-gcc-4.4.2-2.3.i586 --> Processing Dependency: libgomp = 4.4.2-2.3 for package: cross-armv7l-gcc-4.4.2-2.3.i586 --> Finished Dependency Resolution Error: Package: cross-armv7l-gcc-4.4.2-2.3.i586 (meego-core) Requires: libgomp = 4.4.2-2.3 Installed: libgomp-4.4.2-12.13.i586 (installed) Error: Package: cross-armv7l-gcc-4.4.2-2.3.i586 (meego-core) Requires: cpp = 4.4.2-2.3 Installed: cpp-4.4.2-12.13.i586 (installed) You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest I found a couple of references to this problem, but no answers which address the failure of these packages to install: http://forum.meego.com/showthread.php?t=582 http://comments.gmane.org/gmane.comp.handhelds.meego.devel/2367 Did I miss something, or is this simply a bug? Is anyone successfully using these? If no-one says "yes" I'll file a bug for their removal. -- Rohan ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] cross-armv7l-gcc, cross-armv5tel-gcc are not installable
On Monday 28 June 2010, ext Zhang, Austin wrote: > '--skip-broken' as indication works? Or you can force install to > have a try (please also install those cross-glibc/binutils)? --skip-broken just skips them and doesn't actually install anything; however I was informed that using zypper instead of yum, and using the `-f' option, makes it possible to install them. So, I eventually installed them with: zypper in -f cross-armv7l-gcc cross-armv7l-binutils cross-armv7l-glibc \ cross-armv7l-glibc-devel cross-armv7l-glibc-headers \ cross-armv7l-kernel-headers However, they don't seem to work, e.g.: me...@[meego-netbook-sdk]::~$ /opt/cross/bin/armv7l-meego-linux-gnueabi-gcc -c test.c as: unrecognized option '-meabi=5' me...@[meego-netbook-sdk]::~$ /opt/cross/bin/armv7l-meego-linux-gnueabi-gcc -print-prog-name=as as Seems like the compiler is invoking the system `as' instead of the one from cross-armv7l-binutils. So it's still an open question from me if anyone is managing to use these :-) > > > If no-one says "yes" I'll file a bug for their removal. > > Yes, please go ahead, but not for removal those but correct them. > OK, will see if anyone else replies, then file a bug. -- Rohan ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] cross-armv7l-gcc, cross-armv5tel-gcc are not installable
Hi Rohan! Thanks for your report! We've 2 issues here - one being Requires: libgomp = 4.4.2-2.3 Installed: libgomp-4.4.2-12.13.i586 (installed) which means the packages in the Repository are out of sync (-2.3 vs. 12.13). I need to look if we need that _hard_ dependency also on CI_CNT.BUILD_CNT. 2nd issue is : > me...@[meego-netbook-sdk]::~$ /opt/cross/bin/armv7l-meego-linux-gnueabi-gcc > -c test.c as: unrecognized option '-meabi=5' > > me...@[meego-netbook-sdk]::~$ /opt/cross/bin/armv7l-meego-linux-gnueabi-gcc > -print-prog-name=as as ok, what happens if you do AS=/opt/cross/bin/armv7l-meego-linux-gnueabi-as LD=/opt/cross/bin/armv7l-meego-linux-gnueabi-ld gcc .. This one is worth a bugreport. Please assign it to me - jsmoel...@linuxfoundation.org. Best, Jan-Simon ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] cross-armv7l-gcc, cross-armv5tel-gcc are not installable
how to get meego bootloader ,kernel code package. /***/ ??? ? ?? ??: 3001?18#??503? 518118 ??: 0755-8988 ??: 0755-89924456 ??:18666280350 Email: tang.xin...@byd.com http://www.byd.com /***/ - Original Message - From: "Rohan McGovern" To: Cc: "Jan-Simon Möller" Sent: Monday, June 28, 2010 3:10 PM Subject: Re: [MeeGo-dev] cross-armv7l-gcc, cross-armv5tel-gcc are not installable On Monday 28 June 2010, ext Zhang, Austin wrote: > '--skip-broken' as indication works? Or you can force install to > have a try (please also install those cross-glibc/binutils)? --skip-broken just skips them and doesn't actually install anything; however I was informed that using zypper instead of yum, and using the `-f' option, makes it possible to install them. So, I eventually installed them with: zypper in -f cross-armv7l-gcc cross-armv7l-binutils cross-armv7l-glibc \ cross-armv7l-glibc-devel cross-armv7l-glibc-headers \ cross-armv7l-kernel-headers However, they don't seem to work, e.g.: me...@[meego-netbook-sdk]::~$ /opt/cross/bin/armv7l-meego-linux-gnueabi-gcc -c test.c as: unrecognized option '-meabi=5' me...@[meego-netbook-sdk]::~$ /opt/cross/bin/armv7l-meego-linux-gnueabi-gcc -print-prog-name=as as Seems like the compiler is invoking the system `as' instead of the one from cross-armv7l-binutils. So it's still an open question from me if anyone is managing to use these :-) > > > If no-one says "yes" I'll file a bug for their removal. > > Yes, please go ahead, but not for removal those but correct them. > OK, will see if anyone else replies, then file a bug. -- Rohan ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev Powered by BYD Security Gateway. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] cross-armv7l-gcc, cross-armv5tel-gcc are not installable
2010/6/28 Jan-Simon Möller : >> me...@[meego-netbook-sdk]::~$ /opt/cross/bin/armv7l-meego-linux-gnueabi-gcc >> -c test.c as: unrecognized option '-meabi=5' >> >> me...@[meego-netbook-sdk]::~$ /opt/cross/bin/armv7l-meego-linux-gnueabi-gcc >> -print-prog-name=as as > > ok, what happens if you do AS=/opt/cross/bin/armv7l-meego-linux-gnueabi-as > LD=/opt/cross/bin/armv7l-meego-linux-gnueabi-ld gcc .. I have identical output for both commands also when using those extra variables. And tested both when using cross-armv7-* packages from 1.0 and trunk in Ubuntu 10.04 i386 chroot (helped with alien) and when installing those packages inside MeeGo SDK chroot with zypper and trying to compile after that. Just trying hello world. The host system itself is 64-bit Ubuntu. > This one is worth a bugreport. Please assign it to me - > jsmoel...@linuxfoundation.org. Was this filed? Cannot find in bugs.meego.com but maybe I just don't what to search for. -Timo ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] cross-armv7l-gcc, cross-armv5tel-gcc are not installable
3.8.2010 16:51, Timo Jyrinki kirjoitti: 2010/6/28 Jan-Simon Möller: me...@[meego-netbook-sdk]::~$ /opt/cross/bin/armv7l-meego-linux-gnueabi-gcc -c test.c as: unrecognized option '-meabi=5' me...@[meego-netbook-sdk]::~$ /opt/cross/bin/armv7l-meego-linux-gnueabi-gcc -print-prog-name=as as ok, what happens if you do AS=/opt/cross/bin/armv7l-meego-linux-gnueabi-as LD=/opt/cross/bin/armv7l-meego-linux-gnueabi-ld gcc .. I have identical output for both commands also when using those extra variables. And tested both when using cross-armv7-* packages from 1.0 and trunk in Ubuntu 10.04 i386 chroot (helped with alien) and when installing those packages inside MeeGo SDK chroot with zypper and trying to compile after that. Just trying hello world. The host system itself is 64-bit Ubuntu. This problem is like having no gasoline in a normal car. The user looks inside the hood and sees the battery, tries to "start" but the engine doesn't purr long... A GCC user looks at the $prefix/bin, sees the $target- there and starts the compiler, neither it purrs long :( In both cases there is a horrible mistake! What the user sees near the engine or the GCC user sees near the "GCC binaries", really isn't what the engine or GCC requires. But both users are still expected to be able to check whether there is gasoline for the engine or binutils for GCC ! This one is worth a bugreport. Please assign it to me - jsmoel...@linuxfoundation.org. Was this filed? Cannot find in bugs.meego.com but maybe I just don't what to search for. As you can guess the answer to the question: "Where the binutils for 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 :( Furthermore there are other issues like the 'libgcc.a's being broken and the "only for i586-meego-linux host" attitude, older x86 hosts with glibc-2.3 - 2.10 cannot run the provided binaries... Therefore I myself made my own crosstoolchains from pristine FSF sources, binutils-2.20.51, gcc-4.4.4, gcc-4.5.0 and yesterday gcc-4.5.1 for the 'armv7l' variation (using '--with-cpu=cortex-a8' for a better tuning for N900). The original MeeGo/ARM glibcs, libcurses, X11-libs etc. were though used, no rebuilds for them until seen broken - "Don't fix it if it ain't broken"... The binutils and GCC components were broken, so I fixed them. Making optimized libraries for cortex-a8 may wait... The MADDE or something Scratchbox-derived crosstoolchain then seem to be quite OK, not tuned for ARM/Cortex-A8 being the default CPU target of course... Somehow one has used to see developers going up the walls if their toolchain produces not-optimized code, the prebuilt libraries are not-optimized for the target CPU etc. Weird that nobody has nagged about this yet... ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] cross-armv7l-gcc, cross-armv5tel-gcc are not installable
2010/8/3 Kai Ruottu : > 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. Continuing messing around now. Thanks for responding. -Timo ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] cross-armv7l-gcc, cross-armv5tel-gcc are not installable
4.8.2010 10:00, Timo Jyrinki kirjoitti: 2010/8/3 Kai Ruottu: 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... 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 Looking this with 'tar tvjf cross-tools-armv7l-meego.tar.bz2 | less' will tell what the install scheme is... ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] cross-armv7l-gcc, cross-armv5tel-gcc are not installable
Am Mittwoch, 4. August 2010, 12:30:02 schrieb Kai Ruottu: > 4.8.2010 10:00, Timo Jyrinki kirjoitti: > > 2010/8/3 Kai Ruottu: > >> 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
Re: [MeeGo-dev] cross-armv7l-gcc, cross-armv5tel-gcc are not installable
Am Mittwoch, 4. August 2010, 12:30:02 schrieb Kai Ruottu: > 4.8.2010 10:00, Timo Jyrinki kirjoitti: > > 2010/8/3 Kai Ruottu: > >> 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
