public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Elliot Lee <sopwith@cuc.edu>
To: Brett Dikeman <brett@arthur.malebolge.com>
Cc: Richard Henderson <rth@cygnus.com>, egcs@cygnus.com
Subject: Re: as problem, PPC
Date: Mon, 03 Nov 1997 16:27:00 -0000	[thread overview]
Message-ID: <Pine.LNX.3.95.971103165845.3584A-100000@helix.cs.cuc.edu> (raw)
In-Reply-To: <v03102804b083bc158ed0@[144.89.161.9]>

On Mon, 3 Nov 1997, Brett Dikeman wrote:

> At 1:40 AM -0600 on 11/3/97, Richard Henderson wrote:
> 
> 
> > On Sun, Nov 02, 1997 at 11:02:33PM -0600, Brett Dikeman wrote:
> > > $/usr/bin/as
> > > bash: /usr/bin/as: no such file or directory
> >
> > Looks like you've misplaced ld.so.  I wonder if the RPM upgraded your
> > binutils too?  And the distributer is using glibc2 and you aren't?
> That was in a seperate RPM.  binutils-2.8.1.0.11.
> 
> > What does "objdump -s -j .interp /usr/bin/as" report, if you can?
> "bash:/usr/bin/objdump: no such file or directory"
> :\
> (with or without command arg's.)

It's because of the dynamic linker name.

I compiled that package to use /lib/ld-linux.so.2

The traditional glibc setup is /lib/ld.so.1

Do:
	ln -s ld.so.1 /lib/ld-linux.so.2

-- Elliot					http://www.redhat.com/
"They don't let my code go into shipping products," Gates said. "They
 haven't done that for eight years." (at the 1997 PDC)


  reply	other threads:[~1997-11-03 16:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-11-02 22:27 Brett Dikeman
1997-11-02 22:44 ` Jeffrey A Law
1997-11-03  2:06   ` Brett Dikeman
1997-11-03  3:21   ` Franz Sirl
1997-11-03  1:33 ` Richard Henderson
1997-11-03  9:43   ` Brett Dikeman
1997-11-03 16:27     ` Elliot Lee [this message]
     [not found] ` <199711031351.KAA04460@pincoya.inf.utfsm.cl>
1997-11-03  9:43   ` Brett Dikeman
1997-11-03 13:37     ` H.J. Lu

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=Pine.LNX.3.95.971103165845.3584A-100000@helix.cs.cuc.edu \
    --to=sopwith@cuc.edu \
    --cc=brett@arthur.malebolge.com \
    --cc=egcs@cygnus.com \
    --cc=rth@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).