Errors when building a kernel

[Tom H]

On Fri, Aug 21, 2015 at 5:05 AM, Ralf Mardorf
<ralf.mardorf at alice-dsl.net> wrote:
>
> I try to build a kernel for Wily, that is as close as possible to a
> kernel I use for Arch Linux. The reason is, that for the Arch install
> Green drives don't run berserk and I anyway need a 3.x-rt.
>
> Then I tried to build the kernel [1] for Ubuntu Wily
> Werewolf(development branch):
>
> I used the Arch Linux config and edited
>
> CONFIG_LOCALVERSION "-1-rt-lts" to "-1-moonstudio"
>
> Since building the kernel failed, I also edited
>
> CONFIG_DRM_I915=m and CONFIG_DRM_I915_KMS=y to "is not set"
> CONFIG_R8187SE=m to "is not set"
> CONFIG_RTL8192E=m to "is not set"
> CONFIG_R8712U=m to "is not set"
> CONFIG_WLAGS49_H2 to "is not set"
> CONFIG_WLAGS49_H25=m to "is not set"
>
> now I run into an issue. Building MPILIB fails, but I don't know what to
> do, to disable or to build it.
>
> I already tried to disable it by editing
>
> CONFIG_MPILIB=m to "# CONFIG_MPILIB is not set" and CONFIG_KEYS‏=y to "is not set"
>
> but after running "make oldconfig" it's back to CONFIG_MPILIB=m.
>
> I tried with "CONFIG_MPILIB=n" and "CONFIG_KEYS=y".
>
> Unfortunately it could take 1.5 hours before the next error occurs.
>
> Is there a faster way to verify what modules will fail to build, instead
> of compiling the kernel?
>
> Fortunately "grep MPILIB .config" helps with the current issue.
> It's still "CONFIG_MPILIB=m" after running "make oldconfig". How can I
> find out what settings I need to edit?
>
> The Internet wasn't helpful :(.
>
> [1]
> [root at moonstudio src]# export CONCURRENCY_LEVEL=2;wget https://www.kernel.org/pub/linux/kernel/v3.x/linux-3.10.61.tar.gz https://www.kernel.org/pub/linux/kernel/projects/rt/3.10/older/patch-3.10.61-rt65.patch.gz && tar zxf linux-3.10.61.tar.gz && mv linux-3.10.61 linux-3.10.61-rt65 && cd linux-3.10.61-rt65 && gzip -dc ../patch-3.10.61-rt65.patch.gz | patch -p1 && cp ../config-3.10.61-rt65-1-rt-lts_x86_64.Arch .config && make oldconfig && make oldconfig && date && make-kpkg clean && make-kpkg --initrd kernel-image kernel-headers && make-kpkg clean && date

Are you editing ".config" manually? if yes, why don't you use "make
menuconfig" (or another config target) because there are dependencies
that you can't account for when using vi/nano/emacs/whatever.

I run the rc kernels on my laptop and about a year decided to stop
fiddling around with kernel configs so I use the Arch, Fedora, and
Ubuntu configs in rotation for each rc series; and my kernels compile
without a hitch.

(You're running "make oldconfig" twice in [1], not that it should
really matter.)