 d1526e2cda
			
		
	
	
	d1526e2cda
	
	
	
		
			
			It has caused more problems than it ever really solved, and is apparently not getting cleaned up and fixed. We can put it back when it's stable and isn't likely to make warning or bug events worse. In the meantime, enable frame pointers for more readable stack traces. Signed-off-by: Linus Torvalds <torvalds@osdl.org>
		
			
				
	
	
		
			75 lines
		
	
	
	
		
			2.8 KiB
			
		
	
	
	
		
			Makefile
		
	
	
	
	
	
			
		
		
	
	
			75 lines
		
	
	
	
		
			2.8 KiB
			
		
	
	
	
		
			Makefile
		
	
	
	
	
	
| #
 | |
| # Makefile for the linux kernel.
 | |
| #
 | |
| 
 | |
| obj-y     = sched.o fork.o exec_domain.o panic.o printk.o profile.o \
 | |
| 	    exit.o itimer.o time.o softirq.o resource.o \
 | |
| 	    sysctl.o capability.o ptrace.o timer.o user.o \
 | |
| 	    signal.o sys.o kmod.o workqueue.o pid.o \
 | |
| 	    rcupdate.o extable.o params.o posix-timers.o \
 | |
| 	    kthread.o wait.o kfifo.o sys_ni.o posix-cpu-timers.o mutex.o \
 | |
| 	    hrtimer.o rwsem.o latency.o nsproxy.o srcu.o
 | |
| 
 | |
| obj-$(CONFIG_STACKTRACE) += stacktrace.o
 | |
| obj-y += time/
 | |
| obj-$(CONFIG_DEBUG_MUTEXES) += mutex-debug.o
 | |
| obj-$(CONFIG_LOCKDEP) += lockdep.o
 | |
| ifeq ($(CONFIG_PROC_FS),y)
 | |
| obj-$(CONFIG_LOCKDEP) += lockdep_proc.o
 | |
| endif
 | |
| obj-$(CONFIG_FUTEX) += futex.o
 | |
| ifeq ($(CONFIG_COMPAT),y)
 | |
| obj-$(CONFIG_FUTEX) += futex_compat.o
 | |
| endif
 | |
| obj-$(CONFIG_RT_MUTEXES) += rtmutex.o
 | |
| obj-$(CONFIG_DEBUG_RT_MUTEXES) += rtmutex-debug.o
 | |
| obj-$(CONFIG_RT_MUTEX_TESTER) += rtmutex-tester.o
 | |
| obj-$(CONFIG_GENERIC_ISA_DMA) += dma.o
 | |
| obj-$(CONFIG_SMP) += cpu.o spinlock.o
 | |
| obj-$(CONFIG_DEBUG_SPINLOCK) += spinlock.o
 | |
| obj-$(CONFIG_PROVE_LOCKING) += spinlock.o
 | |
| obj-$(CONFIG_UID16) += uid16.o
 | |
| obj-$(CONFIG_MODULES) += module.o
 | |
| obj-$(CONFIG_KALLSYMS) += kallsyms.o
 | |
| obj-$(CONFIG_PM) += power/
 | |
| obj-$(CONFIG_BSD_PROCESS_ACCT) += acct.o
 | |
| obj-$(CONFIG_KEXEC) += kexec.o
 | |
| obj-$(CONFIG_COMPAT) += compat.o
 | |
| obj-$(CONFIG_CPUSETS) += cpuset.o
 | |
| obj-$(CONFIG_IKCONFIG) += configs.o
 | |
| obj-$(CONFIG_STOP_MACHINE) += stop_machine.o
 | |
| obj-$(CONFIG_AUDIT) += audit.o auditfilter.o
 | |
| obj-$(CONFIG_AUDITSYSCALL) += auditsc.o
 | |
| obj-$(CONFIG_KPROBES) += kprobes.o
 | |
| obj-$(CONFIG_SYSFS) += ksysfs.o
 | |
| obj-$(CONFIG_DETECT_SOFTLOCKUP) += softlockup.o
 | |
| obj-$(CONFIG_GENERIC_HARDIRQS) += irq/
 | |
| obj-$(CONFIG_SECCOMP) += seccomp.o
 | |
| obj-$(CONFIG_RCU_TORTURE_TEST) += rcutorture.o
 | |
| obj-$(CONFIG_RELAY) += relay.o
 | |
| obj-$(CONFIG_UTS_NS) += utsname.o
 | |
| obj-$(CONFIG_TASK_DELAY_ACCT) += delayacct.o
 | |
| obj-$(CONFIG_TASKSTATS) += taskstats.o tsacct.o
 | |
| 
 | |
| ifneq ($(CONFIG_SCHED_NO_NO_OMIT_FRAME_POINTER),y)
 | |
| # According to Alan Modra <alan@linuxcare.com.au>, the -fno-omit-frame-pointer is
 | |
| # needed for x86 only.  Why this used to be enabled for all architectures is beyond
 | |
| # me.  I suspect most platforms don't need this, but until we know that for sure
 | |
| # I turn this off for IA-64 only.  Andreas Schwab says it's also needed on m68k
 | |
| # to get a correct value for the wait-channel (WCHAN in ps). --davidm
 | |
| CFLAGS_sched.o := $(PROFILING) -fno-omit-frame-pointer
 | |
| endif
 | |
| 
 | |
| $(obj)/configs.o: $(obj)/config_data.h
 | |
| 
 | |
| # config_data.h contains the same information as ikconfig.h but gzipped.
 | |
| # Info from config_data can be extracted from /proc/config*
 | |
| targets += config_data.gz
 | |
| $(obj)/config_data.gz: .config FORCE
 | |
| 	$(call if_changed,gzip)
 | |
| 
 | |
| quiet_cmd_ikconfiggz = IKCFG   $@
 | |
|       cmd_ikconfiggz = (echo "static const char kernel_config_data[] = MAGIC_START"; cat $< | scripts/bin2c; echo "MAGIC_END;") > $@
 | |
| targets += config_data.h
 | |
| $(obj)/config_data.h: $(obj)/config_data.gz FORCE
 | |
| 	$(call if_changed,ikconfiggz)
 |