From: "Zhangwen (Esan)" <zwzhangwen.zhang@huawei.com>
To: "newlib@sourceware.org" <newlib@sourceware.org>
Subject: newlib-2.2.0/libgloss/mips/crt0.S:161: undefined reference to `hardware_hazard_hook'
Date: Mon, 27 Mar 2017 07:12:00 -0000 [thread overview]
Message-ID: <F2AD730AE2E0D74BAEE20D4C1C6D02BD61D7C6E1@DGGEML504-MBS.china.huawei.com> (raw)
I found the mips compile with newlib-2.2.0 can report the error message when linking with crt0.o manually:
./install/bin/mips-sde-elf-ld: warning: cannot find entry symbol __start; defaulting to 00000000004000d4
newlib-2.2.0/libgloss/mips/crt0.S:161: undefined reference to `hardware_hazard_hook'
newlib-2.2.0/libgloss/mips/crt0.S:161: undefined reference to `hardware_hazard_hook'
newlib-2.2.0/libgloss/mips/crt0.S:195: undefined reference to `get_mem_info'
newlib-2.2.0/libgloss/mips/crt0.S:198: undefined reference to `__stack'
newlib-2.2.0/libgloss/mips/crt0.S:198: undefined reference to `__stack'
newlib-2.2.0/libgloss/mips/crt0.S:227: undefined reference to `hardware_init_hook'
newlib-2.2.0/libgloss/mips/crt0.S:227: undefined reference to `hardware_init_hook'
newlib-2.2.0/libgloss/mips/crt0.S:231: undefined reference to `software_init_hook'
newlib-2.2.0/libgloss/mips/crt0.S:231: undefined reference to `software_init_hook'
newlib-2.2.0/libgloss/mips/crt0.S:301: undefined reference to `hardware_exit_hook'
newlib-2.2.0/libgloss/mips/crt0.S:301: undefined reference to `hardware_exit_hook'
Coud you know the reason for the error and the solution? I have no change for newlib source code.
Cheers,
Zhangwen
next reply other threads:[~2017-03-27 7:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 7:12 Zhangwen (Esan) [this message]
2017-03-27 8:37 ` Matthew Fortune
2017-03-27 9:34 ` 答复: " Zhangwen (Esan)
2017-03-27 12:47 ` Matthew Fortune
2017-03-28 2:17 ` 答复: " Zhangwen (Esan)
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=F2AD730AE2E0D74BAEE20D4C1C6D02BD61D7C6E1@DGGEML504-MBS.china.huawei.com \
--to=zwzhangwen.zhang@huawei.com \
--cc=newlib@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).