RE: [owl-users] Error in installworld

Dear Alexander,

Thank you for help! Now my kernel have built and I use it perfectly. 
According installworld - it was not critical error because all packets have installed successfully in spite of this message. 
Thanks a lot!

Oleg Malykh

-----Original Message-----
From: Solar Designer [mailto:solar_at_private] 
Sent: Tuesday, June 05, 2012 9:19 PM
To: owl-users_at_private
Subject: Re: [owl-users] Error in installworld

On Tue, May 29, 2012 at 03:58:11PM +0400, Malykh Oleg wrote:
> I've tried to install from CD but result the same.

This is not specific.  What exactly did you install from CD?  What did you try updating it to?

Anyway, a few days ago I tried updating an Owl system installed in 2009 (that is, pre-3.0) to Owl-current (i686).  "make installworld" worked just fine.  The issue that you reported did not occur.

> I've got one suggestion for install - when I install new Owl my /etc/modules.conf cleared by installation. Can you keep my version of modules.conf for example as modules.conf.rpmsave?

Thank you for reporting this.  This file will now be preserved (starting with next Owl-current snapshot).

> I cannot build new kernel. I've used wiki article according how to build own kernel but received error:
> 	  LD      drivers/scsi/built-in.o
> 	  LD      drivers/built-in.o
> 	  GEN     .version
> 	  CHK     include/linux/compile.h
> 	  UPD     include/linux/compile.h
> 	  CC      init/version.o
> 	  LD      init/built-in.o	
> 	  LD      .tmp_vmlinux1
> 	net/built-in.o:(.data+0x7a80): undefined reference to `ipv4_ping_group_range'
> 	net/built-in.o:(.data+0x8060): undefined reference to `ipv4_ping_group_range'
> 	make: *** [.tmp_vmlinux1] Error 1
> May be you know what prevent me to build new kernel

You're trying to build without CONFIG_IP_PING, and there's a bug in our patch that prevents such builds from working.  While we do need to fix the bug (thanks for reporting!), you almost certainly want to enable that option anyway.  In fact, chances are that you started with a new config rather than with our default config.  I strongly recommend that you start with the latter - that is, pick dot-config-i686 or
dot-config-x86_64 (as appropriate) out of the native tree as your .config, then customize whatever you need.

Alexander