[SailfishDevel] Where is the source code for the Sailfish OS version of fingerterm (and other GPL applications)

Kalle Vahlman kalle.vahlman at movial.com
Wed Apr 16 05:03:21 UTC 2014


2014-04-16 2:14 GMT+03:00 Mehdi El Gueddari <mehdi at tickmeet.com>:
> --- Problem 2 ---
> Once shadow build had been disabled, I was able to build the arm version
> fine and run it on my device. But when I tried to build the i486 version,
> the build failed with:
>
> /opt/cross/bin/i486-meego-linux-gnu-ld: terminal.o: Relocations in generic
> ELF (EM: 40)
> terminal.o: could not read symbols: File in wrong format
> collect2: ld returned 1 exit status
> make: *** [fingerterm] Error 1
>
> error: Bad exit status from /var/tmp/rpm-tmp.2kusms (%build)
>     Bad exit status from /var/tmp/rpm-tmp.2kusms (%build)
>
> If you'd done it the other way around (built the i486 version first and then
> tried to build the arm version), the error would have been this instead:
>
> /opt/cross/bin/armv7hl-meego-linux-gnueabi-ld: i386 architecture of input
> file `moc_dbusadaptor.o' is incompatible with arm output
> make: *** [fingerterm] Error 1
>
> error: Bad exit status from /var/tmp/rpm-tmp.Rqvpgd (%build)
>     Bad exit status from /var/tmp/rpm-tmp.Rqvpgd (%build)
>
> In either case, the problem is caused by the fact that since we've disabled
> Shadow build, both the arm and the i486 builds are run in the same folder.
> They therefore generate their object files (.o) in the same place. And when
> the linker comes along, it ends up trying to link object files build with
> two different architectures together. Which leads to an avalanche of cryptic
> error messages followed by another miserable failure.
>
> So you need to clean your source folder before switching architectures. I
> tried to add a "make clean" step to the build settings in Qt Creator to try
> and clean things up to no avail.

By my experience cleaning should work fine, but as you said it needs
to be run for the architecture that produced the build files. So
"Build->Clean project" first and after that switch the build target.

-- 
Kalle Vahlman, Movial Creative Technologies Inc.
Porkkalankatu 20, FI-00180 Helsinki
Tel +358 9 8567 6400
Fax +358 9 8567 6401
www.movial.com


More information about the Devel mailing list