From: Hua Ji <hji@netscreen.com>
To: "'karuottu@freenet.hut.fi'" <karuottu@freenet.hut.fi>,
Hua Ji <hji@netscreen.com>
Cc: "'crossgcc@sources.redhat.com'" <crossgcc@sources.redhat.com>
Subject: RE: Help needed
Date: Sun, 01 Apr 2001 00:00:00 -0000 [thread overview]
Message-ID: <A33AEFDC2EC0D411851900D0B73EBEF7063E5C@NAPA> (raw)
Message-ID: <20010401000000.hnl0f0UDi8QWxeTZz6uymBgPztibRklyry-ENj1NLLk@z> (raw)
Thanks a lot. Please read in side.
>And your real target is what ?
Hua: I have no Operating System target. What I need to do is to write codes
for the raw ppc 405GP board from IBM.
-msim
-mmvme
-mads
-myellowknife
For 'Hello World' the '-msim' could be suitable. Then you can run the
executable
with the 'powerpc-elf-run' stand-alone-simulator coming with GDB (the
'psim', made
by Andrew Cagney...), and get your "Hello World" visible...
Hua: Thanks a lot. I tried with -msim. All done perfectly, after libc.a and
__start symbol being linked from sim-crt0.o! This is exactly what I got
stuck yesterday--the linker can't go **automatically** link my libc.a and
__start codes. I guess the story behind my case is:
When I did the cross compiler, I didn't(or couldnot?) specify Operating
System target, but only specify a powerp elf target, so the gcc and the
corresponding linker(ld) can't know how to look for which libc and __start
symbols(or codes)? Am I right? Please continuly educate me. Thanks in
advance.
Hua
------
Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com
next reply other threads:[~2001-04-01 0:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-18 9:39 Hua Ji [this message]
2001-01-19 3:13 ` Kai Ruottu
2001-04-01 0:00 ` Kai Ruottu
2001-04-01 0:00 ` Hua Ji
-- strict thread matches above, loose matches on Subject: below --
2002-06-13 10:02 Help Needed rejip
2002-06-14 2:35 ` Yves Rutschle
2002-06-14 5:35 ` William A. Gatliff
2002-06-14 5:43 ` Yves Rutschle
2002-06-14 6:03 ` William A. Gatliff
2001-05-10 2:50 Help needed Prasad RSV
2001-01-17 11:16 Hua Ji
2001-01-18 3:11 ` Kai Ruottu
2001-04-01 0:00 ` Kai Ruottu
2001-04-01 0:00 ` Hua Ji
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=A33AEFDC2EC0D411851900D0B73EBEF7063E5C@NAPA \
--to=hji@netscreen.com \
--cc=crossgcc@sources.redhat.com \
--cc=karuottu@freenet.hut.fi \
/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).