From: Andrew Cagney <ac131313@cygnus.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb@sources.redhat.com
Subject: Re: S/390 Linux doesn't link on trunk
Date: Mon, 08 Apr 2002 20:50:00 -0000 [thread overview]
Message-ID: <3CB264FB.7080100@cygnus.com> (raw)
In-Reply-To: <20020407173859.A31836@nevyn.them.org>
> Just FYI; I didn't try the branch. The error is:
>
> gcc -O2 -g -Wl,-rpath,/usr/lib -o gdb \
> main.o libgdb.a cli-dump.o cli-decode.o cli-script.o cli-cmds.o cli-setshow.o cli-utils.o mi-out.o mi-console.o mi-cmds.o mi-cmd-var.o mi-cmd-break.o mi-cmd-stack.o mi-cmd-disas.o mi-main.o mi-parse.o mi-getopt.o tui-file.o tui.o tuiData.o tuiSource.o tuiStack.o tuiIO.o tuiGeneralWin.o tuiLayout.o tuiWin.o tuiCommand.o tuiDisassem.o tuiSourceWin.o tuiRegs.o tuiDataWin.o tui-out.o tui-hooks.o ../bfd/libbfd.a -lreadline ../opcodes/libopcodes.a ../libiberty/libiberty.a -lncurses -lm ../libiberty/libiberty.a \
> -ldl -rdynamic
> libgdb.a(inftarg.o): In function `init_child_ops':
> /home/buildd/build/gdb-5.2.cvs20020401/objdir/gdb/../../gdb/inftarg.c:754: undefined reference to `child_pid_to_exec_file'
> collect2: ld returned 1 exit status
> make[2]: *** [gdb] Error 1
> make[2]: Leaving directory `/home/buildd/build/gdb-5.2.cvs20020401/objdir/gdb'
> make[1]: *** [all-gdb] Error 2
> make[1]: Leaving directory `/home/buildd/build/gdb-5.2.cvs20020401/objdir'
> make: *** [build-stamp] Error 2
I take it this is native? The cross appears to build fine.
Andrew
next prev parent reply other threads:[~2002-04-09 3:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-07 14:39 Daniel Jacobowitz
2002-04-08 20:50 ` Andrew Cagney [this message]
2002-04-08 21:36 ` Daniel Jacobowitz
2002-04-10 10:36 ` Jim Blandy
2002-04-15 10:06 ` Dr. Jochen Röhrig
2002-04-15 10:11 ` Daniel Jacobowitz
2002-04-15 11:28 ` Michael Snyder
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=3CB264FB.7080100@cygnus.com \
--to=ac131313@cygnus.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
/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