How to cross-compile POP3Lite ============================= Cross-compiling POP3Lite is pretty easy, although, not as simple as a native compile. First of all, you'll require a cross-compiler (eg gcc-i386-gnu on Debian), building one is not really a big deal. When you've got everything in place: the cross-compiler, the host system's libraries and headers, then get the POP3Lite sources from anonymous CVS. It has some files that can make your life *much* easier. Probably you'll only have to twiddle a little with rebuild.mk. o Run `configure', with special parameters: ./configure --host=[host-system] --build=[build-system] The [host-system] is the target of the compile (eg i386-gnu), the [build-system] is your native system (eg i386-linux-gnu). You MAY require additional tweaking, by setting CFLAGS and LDFALGS, so the C compiler won't use the build system's libraries. If you have GLib installed on the build system, pass the following options to configure: --disable-glib-test --with-glib-prefix=[prefix] Where [prefix] is something like `/gnu/usr/local'. You MIGHT have to twiddle with other libraries, however, setting CFLAGS, LDFLAGS and passing some options to configure should do the job. o After a successful configuration, type `make' to compile the package. o When make finished, you can even install POP3Lite to the host system, by passing a DESTDIR=[dir] parameter to make install. For example: make install DESTDIR=[dir] o Bug reports go to 8@free.bsd.hu. Please include as much information as possible. Cross-compile notes =================== FreeBSD 4.0 ----------- When you cross-compile to i386-freebsdelf4.0, ltconfig does not detect that the host system is ELF, therefore it generates a pretty buggy libtool script. You have the following choices: o Look at the ltconfig script, and fix it o Look at the ltconfig script, and figure out how it detects your system, and change your build system accordingly (fool libtool) o After configuring, apply the patch found in dist/ (called libtool-freebsd-cross.diff)