Re: Issues with cross compilation

I finally managed to get execline to compile - turns out there was an error in the options I had passed to configure: I'm relieved. If it had been a bug, it would have been quite nasty to solve. ;) Thanks for the info. -- Laurent

Re: Issues with cross compilation

I finally managed to get execline to compile - turns out there was an error in the options I had passed to configure: > ./configure --host=armeb-linux-musleabi --prefix=/usr/local --disable-shared \ > --with-sysdeps=/path/to/sysdeps.cfg/ \ > --with-include=/path/to/staging/usr/local/in

Re: Issues with cross compilation

On Tue, May 02, 2017 at 03:19:22PM +, Laurent Bercot wrote: > > > However, when I tried to build execline the compiler tried to include > > libskarnet.a from the host machine when linking the programs: > > (...) > > > > exec armeb-linux-musleabi-gcc -L/path/to/staging/usr/local/lib \ > > -

Re: Issues with cross compilation

./configure: error: target armeb-linux-musleabi does not match the \ contents of /usr/local/lib/skalibs/sysdeps/target The configure script is displaying the default path to the sysdeps directory (based on the --prefix flag) instead of displaying the provided path to the sysdeps directory; i.e

Issues with cross compilation

Hi all, I've recently tried to cross compile some skarnet.org packages and I'm having some issues. I'm compiling on x86_64 Debian Linux (glibc) for big-endian ARMv5 LEDE (musl) (LEDE is a fork of OpenWrt for those who don't know). I'm using a cross-compiler toolchain built from here: