From: "Mahadev K Cholachagudda" <kcmahadev@zilogindia.com>
To: <crossgcc@sources.redhat.com>
Subject: RE: gcc-m68k cross compiler problem gcc2.95.2
Date: Sun, 01 Apr 2001 00:00:00 -0000 [thread overview]
Message-ID: <NEBBJIKLHKODECFJDDFGIEHECDAA.kcmahadev@zilogindia.com> (raw)
Message-ID: <20010401000000.SrZ29W7AUs3FLqZP8WfNkM1vn0lznusrOX0GBm56EJE@z> (raw)
In-Reply-To: <3A5F0A02.9BFD6B54@motorola.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1813 bytes --]
Thanks
a lot pierre.
mahadev
Â
-----Original Message----- From:
crossgcc-owner@sources.redhat.com
[mailto:crossgcc-owner@sources.redhat.com] On Behalf Of Pierre
Saucourt-Harmel (r54698) Sent: Friday, January 12, 2001 1:44
PM To: Mahadev K Cholachagudda Cc:
crossgcc@sources.redhat.com Subject: Re: gcc-m68k cross compiler
problem gcc2.95.2 Hello,
Mahadev K Cholachagudda wrote: ...
I think if i execute gcc to get me the final
executable file, the gcc will intern call pre-processor, c-compiler,
assembler and then linker. I think the linker may not be getting correct
linker script or the above definitions such as (hardware_init_hook etc)
are not there in the linker script which ld is looking for.
Am i correct ? Yes, you are.
Just look at the ld.info documentation (part of binutils package) to study
how the linker takes your script and which commands you can use to write this
script. Your command line to compile should look like that (if your linker
script is named "hello.ld"): m68k-coff-gcc -Wl,--script=hello.ld
hello.c
Moreover, as your gcc compiler do not link with a default C standard
library, I think you did not generate and install correctly the newlib
package. That's why reference to atexit, printf, _exit and _cleanup
symbols are unresolved.
Your gcc compiler should automatically (without adding any option to the
m68k-coff-gcc invocation) link your executable file with the libc.a or libg.a.
Check the presence of these libraries under:
<your-installation-directory>/m68k-coff/lib
For __FINI_SECTION__ and __INIT_SECTION__ sections, you should have defined
them into your linker script. For software_init_hook and harware_init_hook
symbols, I don't know.
Regards, Pierre. Â Â
next prev parent reply other threads:[~2001-04-01 0:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-11 21:46 FW: Mahadev K Cholachagudda
2001-01-11 23:09 ` mike
2001-01-12 4:04 ` gcc-m68k cross compiler problem gcc2.95.2 Mahadev K Cholachagudda
2001-01-12 5:38 ` Pierre Saucourt-Harmel (r54698)
2001-01-12 22:54 ` Mahadev K Cholachagudda [this message]
2001-04-01 0:00 ` Mahadev K Cholachagudda
2001-04-01 0:00 ` Pierre Saucourt-Harmel (r54698)
2001-04-01 0:00 ` Mahadev K Cholachagudda
2001-04-01 0:00 ` mike
2001-04-01 0:00 ` FW: Mahadev K Cholachagudda
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=NEBBJIKLHKODECFJDDFGIEHECDAA.kcmahadev@zilogindia.com \
--to=kcmahadev@zilogindia.com \
--cc=crossgcc@sources.redhat.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).