linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: dony <dony.he@huawei.com.cn>
To: karuottu@freenet.hut.fi
Cc: Brendan.Simon@ctam.com.au,
	linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>,
	crossgcc@sourceware.cygnus.com
Subject: Re: cross-compiling & debugging embedded-linux apps
Date: Fri, 14 Jan 2000 17:27:59 +0800	[thread overview]
Message-ID: <387EEC1E.DEE0BFB6@huawei.com.cn> (raw)
In-Reply-To: 38725315.A8F89547@freenet.hut.fi


Kai Ruottu wrote:

> Brendan J Simon wrote:
> >
> > Kai Ruottu wrote:
> >
> > > 1. Using 'strings' to see the 'hard-wired' name of the dynamic linker in
> > >    the executable:
> > >
> > >         E:\usr\local\samples>strings tst_ppc-linux.x | more
> > >         /lib/ld.so.1    <------- !!!
> > >         __gmon_start__
> > >         libc.so.6
> >
> > The output of "powerpc-linux-strings bjs1-shared" looks OK to me.
> > $ powerpc-linux-strings bjs1-shared
> > _DYNAMIC
> > _GLOBAL_OFFSET_TABLE_
> > __gmon_start__
>
>  When your output from 'strings' didn't show the 'ld.so.1' (didn't it really?)
> I tried removing the '--dynamic-linker xxxxx' from my specs, and got then :

Now I have a similar problem with the dynamic linker "ld.so.1". Can you tell me
how can I remove the "--dynamic-linker XXXX" and set the default dynamic-linker to other
directories ,ie, /syslib/ld.so.1, instead of /lib/ld.so.1?

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2000-01-14  9:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-31  4:50 cross-compiling & debugging embedded-linux apps Brendan J Simon
1999-12-31  6:58 ` Alan Mimms
1999-12-31 16:07   ` Jim Lewis
2000-01-04  0:30     ` Brendan J Simon
2000-01-04  3:16       ` Alan Mimms
1999-12-31 16:28 ` Jim Lewis
2000-01-01  5:59   ` Jeff Millar
2000-01-01 22:17   ` Alan Mimms
2000-01-03 12:23 ` Kai Ruottu
     [not found]   ` <3871A78E.F18B0161@ctam.com.au>
2000-01-04 20:07     ` Kai Ruottu
2000-01-14  9:27       ` dony [this message]

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=387EEC1E.DEE0BFB6@huawei.com.cn \
    --to=dony.he@huawei.com.cn \
    --cc=Brendan.Simon@ctam.com.au \
    --cc=crossgcc@sourceware.cygnus.com \
    --cc=karuottu@freenet.hut.fi \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    /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 NNTP newsgroup(s).