This is the mail archive of the
insight@sources.redhat.com
mailing list for the Insight project.
Re: Inside 6.1 build problem
- From: Keith Seitz <keiths at redhat dot com>
- To: roland dot winistoerfer at winformatik dot ch
- Cc: "insight at sources dot redhat dot com" <insight at sources dot redhat dot com>
- Date: Tue, 20 Apr 2004 09:01:26 -0700
- Subject: Re: Inside 6.1 build problem
- References: <4084F418.8070805@winformatik.ch>
On Tue, 2004-04-20 at 02:57, Roland WinistÃrfer wrote:
> Output (make.out):
> .....
> rm -f gdb.exe
> gcc -mwin32 -g -O2 \
> -o gdb.exe gdb.o libgdb.a \
> ../bfd/libbfd.a ../readline/libreadline.a ../opcodes/libopcodes.a
> ./../intl/libintl.a ../libiberty/libiberty.a -lm -lncurses
> ../libiberty/libiberty.a -luser32
> libgdb.a(tui-win.o)(.text+0x1e5): In function `tui_update_variables':
> /src/insight-6.1/gdb/tui/tui-win.c:281: undefined reference to `_acs_map'
> libgdb.a(tui-win.o)(.text+0x1f1):/src/insight-6.1/gdb/tui/tui-win.c:281:
> undefined reference to `_acs_map'
> libgdb.a(tui-win.o)(.text+0x1f8):/src/insight-6.1/gdb/tui/tui-win.c:281:
> undefined reference to `_acs_map'
> libgdb.a(tui-win.o)(.text+0x201):/src/insight-6.1/gdb/tui/tui-win.c:281:
> undefined reference to `_acs_map'
> libgdb.a(tui-win.o)(.text+0x211):/src/insight-6.1/gdb/tui/tui-win.c:281:
> undefined reference to `_acs_map'
> libgdb.a(tui-win.o)(.text+0x221):/src/insight-6.1/gdb/tui/tui-win.c:281:
> more undefined references to `_acs_map' follow
> Info: resolving _LINES by linking to __imp__LINES (auto-import)
> Info: resolving _COLS by linking to __imp__COLS (auto-import)
> Info: resolving _stdscr by linking to __imp__stdscr (auto-import)
> Info: resolving _curscr by linking to __imp__curscr (auto-import)
> collect2: ld returned 1 exit status
> make[1]: *** [gdb.exe] Error 1
> make[1]: Leaving directory `/tmp/build/gdb/gdb'
> make: *** [all-gdb] Error 2
> make: Leaving directory `/tmp/build/gdb'
Looks like something to do with ncurses in one of gdb's subdirectories.
I know I just built HEAD on cygwin a couple of days ago. Have you tried
that? Maybe there's a fix in there. (Web search?)
If not, your best recourse is to ask on the gdb list since the
compilation failure occurs in one of gdb's directories.
Keith