From: mod+linuxppc-dev@MissionCriticalLinux.com
To: linuxppc-dev@lists.linuxppc.org
Subject: Link-time failures from "simple" CFLAGS changes
Date: Mon, 07 Jan 2002 17:01:51 -0500 [thread overview]
Message-ID: <200201072201.RAA05808@missioncriticallinux.com> (raw)
When I change -O2 to -O0 in my CFLAGS definition in Makefile thus:
CFLAGS := -g $(CPPFLAGS) -Wall -Wstrict-prototypes -Wno-trigraphs -O0 \
-fno-strict-aliasing -fno-common
CFLAGS := -g $(CPPFLAGS) -Wall -Wstrict-prototypes -Wno-trigraphs -O2 \
-fno-strict-aliasing -fno-common
...I am astounded to see thousands of unresolved references
at kernel link time. WTF? Any ideas? These are the
sorts of symbols that come up undefined:
after __bad_udelay before between clear_user copy_from_user copy_siginfo
copy_to_user dcacheFlushSingle dcacheInvalidateSingle dev_load down
down_interruptible down_trylock DQUOT_ALLOC_BLOCK DQUOT_FREE_BLOCK
DQUOT_PREALLOC_BLOCK eieio empty_stack fib_find_info fn_flush_list
fn_key_eq fn_key_leq frag_alloc_queue frag_free_queue frag_kfree_skb
free_pgd_fast free_pgd_slow get_native_tbl get_order get_pgd_fast
get_rtcl get_tbl get_tbu __get_user_bad htonl htons in_8 inet_getid
inet_putpeer in_le16 in_le32 ipc_buildid ipc_checkid ipc_get ipc_lock
ipc_lockall ipc_unlock ipc_unlockall ld_le32 maybe_unmark_and_push
ntohl ntohs out_8 out_be32 out_le16 out_le32 pcibios_make_OF_bus_map
pcibios_set_master phys_to_virt pmd_populate pop_stack prefetch
prefetchw pte_free_slow __put_user_bad rotate_left rtnetlink_rcv_skb SBI
__skb_cb_too_small_for_tcp sockfd_put socki_lookup strncpy_from_user
strnlen_user tb_ticks_since tcpdiag_rcv_skb tcp_need_reset
tcp_paws_discard tcp_replace_ts_recent tcp_store_ts_recent __udelay
unix_get_socket unix_release_addr up __USE_RTC verify_area virt_to_bus
virt_to_phys __xchg_called_with_bad_pointer xprt_move_iov
This isn't a showstopper problem for me but I was so surprised to see
it that I'm curious about its cause, so thanks for any enlightenment.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-01-07 22:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-07 22:01 mod+linuxppc-dev [this message]
2002-01-07 22:10 ` Link-time failures from "simple" CFLAGS changes David Edelsohn
2002-01-07 22:15 ` Tom Rini
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=200201072201.RAA05808@missioncriticallinux.com \
--to=mod+linuxppc-dev@missioncriticallinux.com \
--cc=linuxppc-dev@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