On Thu, Aug 01, 2013 at 12:37:33PM -0400, Jonathan Bagg wrote: > I've been cross compiling compat-wireless and now I'm trying > backports. It looks like conf.c and zconf.tab.c are being compiled > as arm and then the build process is trying to run conf on my x86 > host. Results using the below make parameters I was using for > compat-wireless...... Howdy. :) (btw, I'm CC'ing the backports mailing list, which is a better place to ask these sorts of questions) I found that the backports cross-compile process worked much the same way as building compat-wireless. This is what I'm doing currently in my build script: (This is using a backports package generated last night using the backports git HEAD code with the cw1200 driver integrated) set -a CROSS_COMPILE=${CROSS_COMPILE} ARCH=${TARGET_CPU} KLIB_BUILD=${DEV_PATH}/${LINUX_DIR} KLIB=${TARGET_ROOT_ON_HOST} set +a make oldconfig # menuconfig worked here too make make install That said, the 'make install' target isn't currently sane for cross-builds due to the bacport_firmware_install script not respecting prefixes. I just commented that script (and a few others like initrd updates) out of the Makefiles, and I had a successful build/install. - Solomon -- Solomon Peachy pizza at shaftnet dot org Delray Beach, FL ^^ (email/xmpp) ^^ Quidquid latine dictum sit, altum viditur.
Attachment:
pgprrKYHsj54R.pgp
Description: PGP signature