cross compilation broken beyond repair about aircrack-ng-archive

[aircrack-ng]

Could you test again with current master?

[rofl0r]

it is still broken, now differently :/

~/aircrack-ng[master]$ CC="arm-linux-musleabihf-gcc -isystem /home/rofl/x-prefix/armv7hf/include -L /home/rofl/x-prefix/armv7hf/lib" PKG_CONFIG_SYSROOT_DIR=/home/rofl/x-prefix/armv7hf/ PKG_CONFIG_LIBDIR=/home/rofl/x-prefix/armv7hf/lib/pkgconfig/ ./configure --host=arm-linux-musleabihf --without-opt

...


checking for python3... no
checking for python2... /bin/python2
checking for python2-config... /bin/python2-config
checking for Python prefix... /
checking for Python site-packages directory... lib/python2.7/site-packages
checking if Python >= '2.7'... configure: error: in `/home/rofl/aircrack-ng':
configure: error: cannot run test program while cross compiling
See `config.log' for more details

there are several issues here:

• python2-config is utterly incompatible with cross-compilation, it should NOT be used
• we don't need to know python prefix or python site directories, since we don't install python libraries!
• we don't need to test if runtime dependencies like ethtool or python are installed
• and lastly, this should not break the build!

@jbenden ^

[jbenden]

I just fixed the cross-compilation problem with the configure script. You should be able to continue with your compilation. It was tested on an x86_64 machine with an arm-unknown-linux-gnuabihf compiler.

As for the other points; they are not really relevant to the cross-compilation being broken. But for clarity, Python is required as the ext-scripts are Python. Due to this, it is a requirement to know where to install them. Ethtool is detected simply to show a user that it may be desirable to have it present. It is not a hard requirement, and does not cause the build to halt.

Sorry for breaking the build. :)

[rofl0r]

thanks. how do you propose installing the python libraries into the crosscompiled rootfs, rather than into the host's filesystem ? running pyton2-config will return the host's directories! if nothing else, there should be an option to override the directories so this can be achieved. even better, if crosscompile is detected, either fail and require the user to pass these paths by hand, or just --disable-python, if those are not provided.

[rofl0r]

here's a trick: if a python script (program) depends on other modules, these can be put into the same directory as the script itself, and the script can use them via

sys.path.append(os.path.dirname(os.path.realpath(__file__)))
import foo

the files could all be installed into $PREFIX/share/aircrack-ng/python/ (including the app using them) and $PREFIX/bin/airFOO-ng could be a symlink to ../share/aircrack-ng/python/airFOO-ng.py

[jbenden]

The --with-ext-scripts option completely requires a working Python; as such, if none was found or specified (PYTHON environment variable), then the configure phase of the build will fail with an appropriate error message. For the Python programs to build and install, they all utilize distutils for these various phases. I don't think there's a quick fix for this.

In short, when cross-compiling the --with-ext-scripts option to configure should not be used, for now.