public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@zembu.com>
To: dave@hiauly1.hia.nrc.ca
Cc: nickc@cygnus.com, binutils@sourceware.cygnus.com
Subject: Re: Duplicate symbols in recent cvs source
Date: Thu, 01 Jul 1999 00:00:00 -0000	[thread overview]
Message-ID: <19990604190012.9569.qmail@daffy.airs.com> (raw)
In-Reply-To: <199906041852.OAA26748@hiauly1.hia.nrc.ca>

   Date: Fri, 4 Jun 1999 14:52:23 -0400 (EDT)
   From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>

   gcc -O3 -s -o as-new app.o as.o atof-generic.o bignum-copy.o cond.o depend.o dwa
   rf2dbg.o ecoff.o ehopt.o expr.o flonum-copy.o flonum-konst.o flonum-mult.o frags
   .o hash.o input-file.o input-scrub.o listing.o literal.o macro.o messages.o outp
   ut-file.o read.o sb.o stabs.o subsegs.o symbols.o write.o tc-hppa.o obj-som.o at
   of-ieee.o ../opcodes/.libs/libopcodes.a ../bfd/.libs/libbfd.a ../libiberty/libib
   erty.a ./../intl/libintl.a
   /bin/ld: Unsatisfied symbols:
      _bfd_dwarf1_find_nearest_line (code)
   collect2: ld returned 1 exit status
   make[3]: *** [as-new] Error 1

   This routine appears to be in bfd/dwarf1.c.  It appears to be missing
   from the bfd/Makefile.

You're right, dwarf1.c was not correctly added to the BFD Makefile.  I
just checked in a patch.

Ian

  reply	other threads:[~1999-07-01  0:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-01  0:00 Nick Clifton
1999-07-01  0:00 ` John David Anglin
1999-07-01  0:00   ` Ian Lance Taylor
1999-07-01  0:00     ` John David Anglin
1999-07-01  0:00       ` Ian Lance Taylor [this message]
1999-07-01  0:00         ` John David Anglin
  -- strict thread matches above, loose matches on Subject: below --
1999-07-01  0:00 John David Anglin
     [not found] <no.id>
1999-07-01  0:00 ` John David Anglin
1999-07-01  0:00   ` John David Anglin
1999-07-01  0:00 Nick Clifton

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=19990604190012.9569.qmail@daffy.airs.com \
    --to=ian@zembu.com \
    --cc=binutils@sourceware.cygnus.com \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=nickc@cygnus.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).