From: Wolfgang Denk <wd@denx.de>
To: Paul Ruhland <pruhland@rochester.rr.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: powerpc cross tools question
Date: Mon, 25 Mar 2002 23:18:22 +0100 [thread overview]
Message-ID: <20020325221827.B1CBF109F3@denx.denx.de> (raw)
In-Reply-To: Your message of "Mon, 25 Mar 2002 17:03:13 EST." <200203251703.13296.pruhland@rochester.rr.com>
In message <200203251703.13296.pruhland@rochester.rr.com> you wrote:
>
> The only thing I'm not satisfied with at this point is I still need to make a
> link on my target file system with the full path to the CDK lib directory as
> on my host...
This is simple to solve; see "Solution 2" on
http://www.denx.de/tips+tricks-en.html#libpath
You can simply add this to the compiler's "spec" file:
...
*link:
-m elf32ppclinux %{G*} %{shared:-shared} %{!shared: %{!static: -R/lib %{rdynamic:-export-dynamic} %{!dynamic-linker:-dynamic-linker /lib/ld.so.1}} %{static:-static}}
ort-dynamic} %{!dynamic-linker:-dynamic-linker /lib/ld.so.1}} %{static:-static}}
...
> required patch to glibc may be in there...or someone who knows what the fix
> is may chime in here :)
* ** *** Dongggggg *** ** *
> If you still need help I would be happy to send you my scripts ( yes, I did
> the whole thing in bash scripts...as a exercise mostly...would be just as
> easy/easier to modify the denx makefiles.
Don't waste your time on this old stuff any more; there will be a
replacement soon :-)
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
Quote from the Boss... "I didn't say it was your fault. I said I was
going to blame it on you."
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-03-25 22:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-25 19:34 powerpc cross tools question Keith Outwater
2002-03-25 22:03 ` Paul Ruhland
2002-03-25 22:18 ` Wolfgang Denk [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=20020325221827.B1CBF109F3@denx.denx.de \
--to=wd@denx.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=pruhland@rochester.rr.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 NNTP newsgroup(s).