From: Philipp Rumpf <prumpf@puffin.external.hp.com>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>, willy@thepuffingroup.com
Cc: grundler@cup.hp.com, parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] [MERGE] -pre8 merge status
Date: Sat, 27 May 2000 12:09:53 -0600 [thread overview]
Message-ID: <20000527120953.C664@puffin.external.hp.com> (raw)
In-Reply-To: <200005271531.LAA08195@hiauly1.hia.nrc.ca>; from John David Anglin on Sat, May 27, 2000 at 11:31:08AM -0400
On Sat, May 27, 2000 at 11:31:08AM -0400, John David Anglin wrote:
> > __lshrdi3. It's referenced from fs/nfs/inode.c. I'm damned if I can
> > see where though (and I went through the gcc -E output trying to spot it.)
> > Does someone want to copy that from libgcc? I'm going to lay down a tag
> > for end-of-merge now since I'm headed off for the weekend.
> __lshrdi3 should be in libgcc.a. It's in mine. If it is not there, you
> have a problem building your (cross-)compiler. If it is, check the link
> by adding "-v" to the gcc link operation to see why libgcc.a is not being
> linked into the object.
Our kernel doesn't get linked with libgcc; I don't think it's worth it to
move to using libgcc.a now, even though some architectures do use it.
Philipp Rumpf
next prev parent reply other threads:[~2000-05-27 18:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-26 23:26 [parisc-linux] [MERGE] -pre8 merge status Grant Grundler
2000-05-27 3:37 ` willy
2000-05-27 2:45 ` Philipp Rumpf
2000-05-27 2:54 ` Philipp Rumpf
2000-05-27 4:08 ` willy
2000-05-27 4:56 ` willy
2000-05-27 4:14 ` Alan Modra
2000-05-27 15:31 ` John David Anglin
2000-05-27 18:09 ` Philipp Rumpf [this message]
2000-05-27 18:00 ` Philipp Rumpf
2000-05-27 17:56 ` Philipp Rumpf
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=20000527120953.C664@puffin.external.hp.com \
--to=prumpf@puffin.external.hp.com \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=grundler@cup.hp.com \
--cc=parisc-linux@thepuffingroup.com \
--cc=willy@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