Re: linux-next: Tree for October 27 (netdev/hp-plus)

Previous thread: trace: fix printk warning for u64 by Stephen Rothwell on Sunday, October 26, 2008 - 11:43 pm. (6 messages)

Next thread: Re: 2.6.29 stuff to linux-next now? by Stephen Rothwell on Monday, October 27, 2008 - 12:19 am. (2 messages)
From: Stephen Rothwell
Date: Monday, October 27, 2008 - 12:17 am

Hi all,

A very quiet day.

Today's tree will not build for powerpc allyesconfig (libc aborts the
link due to a free() problem), sparc(32) defconfig and probably some
other configurations.

I am no longer commenting on conflicts that are clearly just caused by
slight differences in what has been merged into Linus' tree and
linux-next or conflicts caused by further changes in the linux-next after
a subset of a tree has been merged.

Changes since 20081027:

Dropped trees:
	v4l-dvb (the tree is a mess)

The vfs tree lost all its conflicts.

The rr tree gained a conflict against Linus' tree but lost one conflict
as well.

The ttydev tree lost its conflict and its build fix patch.

The creds tree lost all its conflicts.

The oprofile tree lost its conflict.

I have also applied the following patches for known problems:

	sparc: qlogicpti fallout from sbus removal
	Work around ld bug in older binutils (powerpc patch)
	ftrace: rename FTRACE to FUNCTION_TRACER more successfully. (sh patch)
	nfsctl: credentials error
	coda: credentials error

----------------------------------------------------------------------------

I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git
(patches at
http://www.kernel.org/pub/linux/kernel/people/sfr/linux-next/).  If you
are tracking the linux-next tree using git, you should not use "git pull"
to do so as that will try to merge the new linux-next release with the
old one.  You should use "git fetch" as mentioned in the FAQ on the wiki
(see below).

You can see which trees have been included by looking in the Next/Trees
file in the source.  There are also quilt-import.log and merge.log files
in the Next directory.  Between each merge, the tree was built with
a ppc64_defconfig for powerpc and an allmodconfig for x86_64. After the
final fixups, it is also built with powerpc allnoconfig,
44x_defconfig and allyesconfig and i386, sparc and sparc64 defconfig.

Below is a summary of ...
From: Randy Dunlap
Date: Monday, October 27, 2008 - 12:17 pm

On Mon, 27 Oct 2008 18:17:25 +1100

Yes, not many build problems (in randconfigs).

linux-next-20081027/drivers/staging/go7007/go7007-v4l2.c:1457: error: 'VI
D_TYPE_CAPTURE' undeclared here (not in a function)


This happens if:
CONFIG_VIDEO_DEV=m
CONFIG_VIDEO_V4L2_COMMON=m
# CONFIG_VIDEO_ALLOW_V4L1 is not set
# CONFIG_VIDEO_V4L1_COMPAT is not set <<<<<<<<<<
CONFIG_DVB_CORE=m
CONFIG_VIDEO_MEDIA=m

full config attached.
-- 
~Randy
From: Randy Dunlap
Date: Monday, October 27, 2008 - 12:19 pm

On Mon, 27 Oct 2008 18:17:25 +1100

This blasted build problem is back.
Are there any outstanding patches in this area?

build-r5284.out:hp-plus.c:(.text+0x2b99a): undefined reference to `eip_interrupt'
build-r5284.out:hp-plus.c:(.text+0x2ba0d): undefined reference to `eip_open'
build-r5284.out:hp-plus.c:(.text+0x2baef): undefined reference to `eip_close'
build-r5284.out:hp-plus.c:(.init.text+0x38ee): undefined reference to `NS8390p_init'
build-r5284.out:(.init.text+0x3948): undefined reference to `__alloc_eip_netdev'
build-r5284.out:make[1]: *** [.tmp_vmlinux1] Error 1


config attached.

-- 
~Randy
From: David Miller
Date: Monday, October 27, 2008 - 12:33 pm

From: Randy Dunlap <rdunlap@xenotime.net>

Grrr...  hp-plus.c uses the interfaces provided with 8390p.c but the Makefile
links it together with plain 8390.c

This is the most spectacular and longest standing build failure I've ever
seen to be honest :-)
--

Previous thread: trace: fix printk warning for u64 by Stephen Rothwell on Sunday, October 26, 2008 - 11:43 pm. (6 messages)

Next thread: Re: 2.6.29 stuff to linux-next now? by Stephen Rothwell on Monday, October 27, 2008 - 12:19 am. (2 messages)