bug-ncurses
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ncurses-5.9-20130316.patch.gz


From: Thomas Dickey
Subject: Re: ncurses-5.9-20130316.patch.gz
Date: Mon, 25 Mar 2013 19:42:39 -0400
User-agent: Mutt/1.5.20 (2009-06-14)

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   -D_XOPEN_SOURCE=500 -D_FILE_OFFSET_BITS=64
> > -DXTSTRINGDEFINES -m32  --param max-inline-insns-single=1200  -W -Wall
> > -Wbad-function-cast -Wcast-align -Wcast-qual -Wmissing-declarations
> > -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wshadow
> > -Wstrict-prototypes -Wundef -Wdeclaration-after-statement -Wextra
> > -Wno-unknown-pragmas -Wswitch-enum -c ../progs/dump_entry.c -o
> > ../objects/dump_entry.o
> > echo "#endif /* __TRANSFORM_H */"                               
> > >>transform.h
> > ../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.

-- 
Thomas E. Dickey <address@hidden>
http://invisible-island.net
ftp://invisible-island.net

Attachment: signature.asc
Description: Digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]