Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Gerrit van Niekerk" <gerritvn@gpvno.co.za>
To: gdb@sourceware.org
Subject: Problem building cross-debugger
Date: Wed, 16 Jan 2008 22:20:00 -0000	[thread overview]
Message-ID: <478E9F4D.24311.2EF0FE9@gerritvn.gpvno.co.za> (raw)

I am trying to use Cygwin to build a Cygwin host, DJGPP target version of GDB:
config --target=djgpp
All libraries seem to build ok (make does not stop), but the final link gives a number of undefined 
references:

`_bfd_i386_arch'
 `_cp_demangled_name_to_comp'
 `_cp_comp_to_string'
`_c_error'
`_objc_parse'
`_objc_error'
`_c_parse'
`c_emit_char'
 `_ada_parse'
`_ada_error'

What am I doing wrong?

I am using the latest CVS snapshot (2008-01-15).
Below is the full error list if it would help.

gcc -g -O2      \
                -o gdb.exe gdb.o libgdb.a \
                   ../readline/libreadline.a ../opcodes/libopcodes.a ../bfd/libb
fd.a ./../intl/libintl.a ../libiberty/libiberty.a ../libdecnumber/libdecnumber.a
     -lncurses -lm  -lexpat ../libiberty/libiberty.a -luser32
libgdb.a(exec.o): In function `legacy_register_sim_regno':
/cygdrive/c/develop/gdb20080115/src/gdb/arch-utils.c:44: undefined reference to
`_bfd_i386_arch'
libgdb.a(cp-support.o): In function `cp_canonicalize_string':
/cygdrive/c/develop/gdb20080115/src/gdb/cp-support.c:118: undefined reference to
 `_cp_demangled_name_to_comp'
/cygdrive/c/develop/gdb20080115/src/gdb/cp-support.c:123: undefined reference to
 `_cp_comp_to_string'
libgdb.a(cp-support.o): In function `mangled_name_to_comp':
/cygdrive/c/develop/gdb20080115/src/gdb/cp-support.c:166: undefined reference to
 `_cp_demangled_name_to_comp'
libgdb.a(cp-support.o): In function `cp_class_name_from_physname':
/cygdrive/c/develop/gdb20080115/src/gdb/cp-support.c:256: undefined reference to
 `_cp_comp_to_string'
libgdb.a(cp-support.o): In function `method_name_from_physname':
/cygdrive/c/develop/gdb20080115/src/gdb/cp-support.c:342: undefined reference to
 `_cp_comp_to_string'
libgdb.a(cp-support.o): In function `cp_func_name':
/cygdrive/c/develop/gdb20080115/src/gdb/cp-support.c:363: undefined reference to
 `_cp_demangled_name_to_comp'
/cygdrive/c/develop/gdb20080115/src/gdb/cp-support.c:371: undefined reference to
 `_cp_comp_to_string'
libgdb.a(cp-support.o): In function `overload_list_add_symbol':
/cygdrive/c/develop/gdb20080115/src/gdb/cp-support.c:390: undefined reference to
 `_cp_demangled_name_to_comp'
/cygdrive/c/develop/gdb20080115/src/gdb/cp-support.c:414: undefined reference to
 `_cp_comp_to_string'
libgdb.a(scm-lang.o): In function `scm_printstr':
/cygdrive/c/develop/gdb20080115/src/gdb/scm-lang.c:54: undefined reference to `_
c_error'
libgdb.a(objc-lang.o): In function `lookup_struct_typedef':
/cygdrive/c/develop/gdb20080115/src/gdb/objc-lang.c:98: undefined reference to `
_objc_parse'
/cygdrive/c/develop/gdb20080115/src/gdb/objc-lang.c:98: undefined reference to `
_objc_error'
libgdb.a(c-lang.o): In function `c_preprocess_and_parse':
/cygdrive/c/develop/gdb20080115/src/gdb/c-lang.c:298: undefined reference to `_c
_parse'
libgdb.a(c-lang.o): In function `c_emit_char':
/cygdrive/c/develop/gdb20080115/src/gdb/c-lang.c:70: undefined reference to `_c_
error'
/cygdrive/c/develop/gdb20080115/src/gdb/c-lang.c:67: undefined reference to `_c_
error'
libgdb.a(c-lang.o): In function `c_printchar':
/cygdrive/c/develop/gdb20080115/src/gdb/c-lang.c:78: undefined reference to `_c_
error'
libgdb.a(c-lang.o): In function `c_printstr':
/cygdrive/c/develop/gdb20080115/src/gdb/c-lang.c:111: undefined reference to `_c
_error'
libgdb.a(ada-lang.o): In function `parse':
/cygdrive/c/develop/gdb20080115/src/gdb/ada-lang.c:10639: undefined reference to
 `_ada_parse'
libgdb.a(ada-lang.o): In function `ada_print_array_index':
/cygdrive/c/develop/gdb20080115/src/gdb/ada-lang.c:333: undefined reference to `
_ada_error'
../bfd/libbfd.a(archures.o): In function `bfd_scan_arch':
/cygdrive/c/develop/gdb20080115/src/bfd/archures.c:622: undefined reference to `
_bfd_i386_arch'
Info: resolving _stdscr by linking to __imp__stdscr (auto-import)
Info: resolving _LINES by linking to __imp__LINES (auto-import)
Info: resolving _COLS by linking to __imp__COLS (auto-import)
Info: resolving _curscr by linking to __imp__curscr (auto-import)
collect2: ld returned 1 exit status
make[2]: *** [gdb.exe] Error 1
make[2]: Leaving directory `/cygdrive/c/develop/gdb20080115/src/CygwinDjgpp/gdb'

make[1]: *** [all-gdb] Error 2
make[1]: Leaving directory `/cygdrive/c/develop/gdb20080115/src/CygwinDjgpp'
make: *** [all] Error 2



             reply	other threads:[~2008-01-16 22:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-16 22:20 Gerrit van Niekerk [this message]
2008-01-18  9:36 ` Gerrit van Niekerk
2008-01-18 16:26   ` Gerrit van Niekerk
2008-01-18 18:53     ` Jim Blandy
2008-01-18 19:27       ` Gerrit van Niekerk
2008-02-11 20:02       ` Michael Shatz
2008-02-13 17:49         ` Michael Shatz
2008-02-13 20:21           ` Gerrit van Niekerk
2008-02-13 21:19             ` Brian Dessent
2008-02-13 20:49           ` Dave Korn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=478E9F4D.24311.2EF0FE9@gerritvn.gpvno.co.za \
    --to=gerritvn@gpvno.co.za \
    --cc=gdb@sourceware.org \
    --cc=gpvno@telkomsa.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox