On Mon, Mar 25, 2013 at 10:23:32AM +0100, Michal Suchanek wrote:
On 25 March 2013 08:24, Michal Suchanek <address@hidden> wrote:
and this without:
i686-w64-mingw32-gcc -I../progs -I. -DHAVE_CONFIG_H -I. -I../include
-I/mingw/include/ncurses
[SNIP]
../lib/libncurses.a(lib_driver.o):lib_driver.c:(.data+0x4): undefined
reference to `__nc_WIN_DRIVER'
../lib/libncurses.a(tinfo_driver.o):tinfo_driver.c:(.text+0xe0a):
undefined reference to `__nc_mingw_ioctl'
../lib/libncurses.a(tinfo_driver.o):tinfo_driver.c:(.text+0xe63):
undefined reference to `__nc_mingw_ioctl'
../lib/libncurses.a(lib_twait.o):lib_twait.c:(.text+0x16): undefined
reference to `__nc_gettimeofday'
collect2: ld returned 1 exit status
make[1]: *** [clear.exe] Error 1
make[1]: *** Waiting for unfinished jobs....
make[1]: Leaving directory `/home/hramrach/ncurses-5.9-20130323/progs'
Obvoiusly the ioctl bit is something from the win32 driver which is
not built at all.
I have no idea how the makefiles are generated but they don't
reference the win32 directory so this cannot ever work, obviously.
Do you have some more details about the build system?
Are there .am files not include in tarballs? Or do you hand-edit .in files?
I don't modify anything in the sources - everything in the build-log
that I sent is from setting configure options (no environment variables
for instance).
Basically, I run a script which looks for the cross-compiler, and passes
the options that I listed in prior email to another script which
performs the configure, make, make-install, other steps (so that I can
check the important parts of the makefiles). The script by the way
prints the options at the top of the log.
I use the same script framework for the other programs which I've got
workable cross-compiles, e.g., mawk, vile.