[Kde-bindings] Building QtRuby on MeeGo - any advice?

Declan McGrath declan at weuseopensource.com
Sun Aug 8 22:09:01 UTC 2010


Hi Arno,

I managed to fix that issue. I saw that the /usr/lib/libm.so should be
a symlink whereas it was actually a zero bytes file. So I deleted the
borked /usr/lib/libm.so manually and then just make a symlink to the
correct target (/lib/libm.so.6) as follows

ln -s /lib/libm.so.6 /usr/lib/libm.so

So that's gotten me past that problem. Hurrah!

I've just got the cmake command successfully completing a minute ago.
Next, I'll try to get the make step working as soon as I can. Thanks a
million to everyone who helped on out this thread!

Regarding cross compiling, I'm running Meego under Xephyr. Xephyr is
described as a SDK Development Environment for MeeGo
(http://wiki.meego.com/MeeGo_SDK_with_Xephyr). I guess as I currently
intend to use QtRuby in this environment it's not cross-compiling. But
if I were to deploy it to a different device running a different
process (ie. ARM) then it would be cross-compiling? I'm not really
sure exactly what cross-compiling is...

All the best,
Declan

On Thu, Aug 5, 2010 at 10:40 PM, Arno Rehn <arno at arnorehn.de> wrote:
> On Thursday 05 August 2010 23:08:50 Declan McGrath wrote:
>> Hi Robert,
>>
>> Thanks for the tip. I actually tried to use cmake before I got your
>> email. I think I have a more fundamental problem as follows:
>>
>> * I am in a directory called qtruby_build
>> * Assuming I'm in qtruby_build, I have the qtruby source code in ../qtruby
>> * I run
>>      cmake ../qtruby
>> * And I get two important errors, which I highlight here
>> ERROR 1:
>> -- Check for working CXX compiler: /usr/bin/c++ -- broken
>> CMake Error at /usr/share/cmake/Modules/CMakeTestCXXCompiler.cmake:43
>> (MESSAGE): The C++ compiler "/usr/bin/c++" is not able to compile a simple
>> test program.
>> ERROR 2:
>>   /usr/lib/gcc/i586-meego-linux/4.4.2/../../../libm.so: file not
>> recognized: File truncated
>>
>> I think maybe my C++ compiler is borked. Though I wonder is it some
>> sort of intel vs ARM processor issue as I'm running on an Intel
>> netbook?
> It rather seems as if libm is borked. However then meego shouldn't boot at
> all, I guess. Are you cross-compiling in some way? (doesn't look like it, just
> like to check). Otherwise i'd suggest asking on some meego-related list, they
> might know more.
>
> --
> Arno Rehn
> arno at arnorehn.de
> _______________________________________________
> Kde-bindings mailing list
> Kde-bindings at kde.org
> https://mail.kde.org/mailman/listinfo/kde-bindings
>



More information about the Kde-bindings mailing list