From: Ian Lance Taylor <ian@airs.com>
To: Bob Rossi <bob@brasko.net>
Cc: GDB <gdb@sources.redhat.com>
Subject: Re: CVS link error
Date: Tue, 27 Sep 2005 00:32:00 -0000 [thread overview]
Message-ID: <m3hdc7bbbb.fsf@gossamer.airs.com> (raw)
In-Reply-To: <20050927002836.GA10821@white>
Bob Rossi <bob@brasko.net> writes:
> I did updated a fairly recent tree like this,
> cvs -d ':ext:bobbybrasko@sources.redhat.com:/cvs/src' co gdb+dejagnu
> from the directory that contains the src/ directory.
>
> When I do a build, I get this link error now,
>
> gcc -g -O2 \
> -o gdb gdb.o libgdb.a \
> ../readline/libreadline.a ../opcodes/libopcodes.a ../bfd/libbfd.a ../libiberty/libiberty.a -lncurses -lm ../libiberty/libiberty.a -ldl -rdynamic
> ../libiberty/libiberty.a(xmalloc.o): In function `xmalloc':
> ../../src/libiberty/xmalloc.c:142: multiple definition of `xmalloc'
> libgdb.a(utils.o):../../src/gdb/utils.c:968: first defined here
> ../libiberty/libiberty.a(xmalloc.o): In function `xcalloc':
> ../../src/libiberty/xmalloc.c:156: multiple definition of `xcalloc'
> libgdb.a(utils.o):../../src/gdb/utils.c:1011: first defined here
> ../libiberty/libiberty.a(xmalloc.o): In function `xrealloc':
> ../../src/libiberty/xmalloc.c:171: multiple definition of `xrealloc'
> libgdb.a(utils.o):../../src/gdb/utils.c:991: first defined here
> collect2: ld returned 1 exit status
> make[1]: *** [gdb] Error 1
> make[1]: Leaving directory `/home/bob/cvs/gdb/original/objdir/gdb'
> make: *** [all-gdb] Error 2
I think this is happening because expandargv in libiberty/argv.c now
calls xmalloc_failed. That is provided by libiberty/xmalloc.c but not
by gdb/utils.c.
Is there any reason for gdb/utils.c to continue to define xmalloc and
friends?
Ian
next prev parent reply other threads:[~2005-09-27 0:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-27 0:28 Bob Rossi
2005-09-27 0:32 ` Ian Lance Taylor [this message]
2005-09-27 2:42 ` Daniel Jacobowitz
2005-09-27 3:11 ` Ian Lance Taylor
2005-09-27 14:32 ` Mark Mitchell
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=m3hdc7bbbb.fsf@gossamer.airs.com \
--to=ian@airs.com \
--cc=bob@brasko.net \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).