Linux PARISC architecture development
 help / color / mirror / Atom feed
From: "Paul J.Y. Lahaie" <pjlahaie@ottawa.com>
To: "hppa-linux@puffingroup.com" <hppa-linux@puffingroup.com>
Subject: [hppa-linux] egcs / binutils problems
Date: Mon, 08 Feb 1999 23:19:45 -0500	[thread overview]
Message-ID: <36BFB761.95F3F9D2@ottawa.com> (raw)

I've further narrowed down the problem of egcs / binutils.  It seems
like the x-compiler of egcs is not building libgcc1.a
(which also seems to infer it being built seperately anyhow).  After
building this file by hand, I no longer get the $$divI 
unresolved reference but I do get a:

$global$ unresolved reference.  Does anyone know where this symbol is
made?  Is it an egcs/ld/gas thing?  Someone mentioned earlier that it
might be a SOM convention, but the elf code makes use of it for some
reason.

									- Paul

PS:  Someone mentioned that the divI, etc.. stuff is from libmilli.a on
HP-UX/MkLinux, the egcs build makes it look like a libgcc1.a, where
should this stuff be put?

----------------------------------------------------------------------
To unsubscribe: send e-mail to hppa-linux-request@puffingroup.com with
`unsubscribe' as the subject.

                 reply	other threads:[~1999-02-09  4:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=36BFB761.95F3F9D2@ottawa.com \
    --to=pjlahaie@ottawa.com \
    --cc=hppa-linux@puffingroup.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