Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Randolph Chung <randolph@tausq.org>
To: Alan Modra <alan@linuxcare.com.au>
Cc: David Huggins-Daines <dhd@linuxcare.com>,
	parisc-linux@thepuffingroup.com
Subject: Re: problems with binutils and/or g++
Date: Wed, 18 Oct 2000 00:02:30 -0700	[thread overview]
Message-ID: <20001018000230.D568@tausq.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0010181628240.1579-100000@front.linuxcare.com.au>; from alan@linuxcare.com.au on Wed, Oct 18, 2000 at 05:18:12PM +1100

> After fixing a zillion bugs of the "friend foo" -> "friend class foo" type 
> and assorted protected/private/public issues, I finally managed to have apt
> compile.  Same error as you found.  It's not a linker bug as it's not a 
> case of the linker dropping some section; the undefined symbol really
> isn't defined anywhere.  I don't know enough C++ to debug the problem
> further.

Alan, for my curiosity, could you explain this particular line from g++'s 
output (from dhd's message)?

../build/obj/cmdline/apt-get.o(.gnu.linkonce.t.__tf10LogCleaner+0x1c):
cannot handle R_PARISC_PCREL17F for pkgArchiveCleaner type_info function

that seems to be causing the "undefined" symbol messages.

randolph
-- 
   @..@                                         http://www.TauSq.org/
  (----)
 ( >__< )
 ^^ ~~ ^^

  reply	other threads:[~2000-10-18  7:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-17 20:38 [parisc-linux] problems with binutils and/or g++ David Huggins-Daines
2000-10-18  0:00 ` Alan Modra
2000-10-18  6:18 ` Alan Modra
2000-10-18  7:02   ` Randolph Chung [this message]
2000-10-18  8:01     ` Alan Modra
2000-10-18 14:34     ` David Huggins-Daines
2000-10-18 16:53       ` John David Anglin

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=20001018000230.D568@tausq.org \
    --to=randolph@tausq.org \
    --cc=alan@linuxcare.com.au \
    --cc=dhd@linuxcare.com \
    --cc=parisc-linux@thepuffingroup.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