lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 31 Dec 2009 11:07:47 -0800
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>,
	Jason Wessel <jason.wessel@...driver.com>
Cc:	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	kgdb-bugreport@...ts.sourceforge.net
Subject: Re: linux-next: Tree for December 31 (kgdb)

On Thu, 31 Dec 2009 11:23:14 +1100 Stephen Rothwell wrote:

> Hi all,
> 
> This one has also not had the build testing *between* merges, but has had
> all the normal build testing at the end.There may be more unbisectable
> points in the tree then usual.
> 
> Changes since 20091230:
> 
> My fixes tree is again empty with the equivalent of its patch being added
> to Linus' tree.


when CONFIG_PROC_FS is not enabled:

kernel/built-in.o: In function `kdb_summary':
kdb_main.c:(.text+0x6a413): undefined reference to `_meminfo_proc_show'


when CONFIG_KGDB_KDB is not enabled:

kernel/built-in.o: In function `kdb_dmesg':
kdb_main.c:(.text+0x6b5c4): undefined reference to `kdb_syslog_data'

when CONFIG_KDB_KEYBOARD is not enabled:

drivers/built-in.o: In function `cleanup_kgdboc':
kgdboc.c:(.text+0x1ee2df): undefined reference to `kdb_get_kbd_char'
drivers/built-in.o: In function `configure_kgdboc':
kgdboc.c:(.text+0x1ee463): undefined reference to `kdb_get_kbd_char'



---
~Randy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ