Re: sbuild crosscompiler not searching /usr/include/arm-linux-gnueabihf
I've made some slight progress.
> After solving initial problems (had to install qemu in the schroot, so
> that python2.7-minimal:armhf can be configured)...
> there's a problem during actual cross-compiling:
In the schroot (entering via: sudo sbuild-shell stretch-amd64-sbuild), I did
apt-get install qemu-user-static qemu-system-arm
> I should perhaps quote a bit more of the (failed) build-output:
>
> dpkg-buildpackage: source package mosquitto
> dpkg-buildpackage: source version 1.4.3-1
> dpkg-buildpackage: source distribution unstable
> dpkg-buildpackage: source changed by Roger A. Light <roger@atchoo.org>
> dpkg-architecture: warning: specified GNU system type
> arm-linux-gnueabihf does not match gcc system type x86_64-linux-gnu,
> try setting a correct CC environment variable
> dpkg-source --before-build mosquitto-1.4.3
> dpkg-buildpackage: host architecture armhf
Adding this to ~/.sbuildrc brought the build much further:
$build_environment = {
'CC' => 'arm-linux-gnueabihf-gcc',
'CXX' => 'arm-linux-gnueabihf-g++'
};
This makes the build goes much further. The c and c++ files get
compiled in the sbuild schroot!
But I now get an error at the end:
make[1]: Leaving directory '/«PKGBUILDDIR»'
dh_makeshlibs -a
dh_shlibdeps -a
dpkg-shlibdeps: error: couldn't find library libstdc++.so.6 needed by
debian/libmosquittopp1/usr/lib/arm-linux-gnueabihf/libmosquittopp.so.1
(ELF format: 'elf32-littlearm'; RPATH: '')
dpkg-shlibdeps: error: cannot continue due to the error above
Note: libraries are not searched in other binary packages that do not
have any shlibs or symbols file.
To help dpkg-shlibdeps find private libraries, you might need to use -l.
dh_shlibdeps: dpkg-shlibdeps -Tdebian/libmosquittopp1.substvars
debian/libmosquittopp1/usr/lib/arm-linux-gnueabihf/libmosquittopp.so.1
returned exit code 2
make: *** [binary-arch] Error 2
debian/rules:9: recipe for target 'binary-arch' failed
dpkg-buildpackage: error: fakeroot debian/rules binary-arch gave error
exit status 2
Any suggestions?
Thanks
n.
Reply to: