You are not logged in.
Hi all,
I'm trying to compile kernel 2.6.38.3 using this method. I uncommented and changed $pkgname to the name I want. I uncommented `make nconfig' and commented `yes "" | make config' (EDIT: also tried without modifying the `make config' line). So now my build() looks like this
build() {
cd ${srcdir}/linux-$_basekernel
# Add -ARCH patches
# See http://projects.archlinux.org/linux-2.6-ARCH.git/
patch -Np1 -i ${srcdir}/${_patchname}
if [ "$CARCH" = "x86_64" ]; then
cat ../config.x86_64 >./.config
else
cat ../config >./.config
fi
if [ "${_kernelname}" != "" ]; then
sed -i "s|CONFIG_LOCALVERSION=.*|CONFIG_LOCALVERSION=\"${_kernelname}\"|g" ./.config
fi
# get kernel version
make prepare
# load configuration
# Configure the kernel. Replace the line below with one of your choice.
# make menuconfig # CLI menu for configuration
make nconfig # new CLI menu for configuration
# make xconfig # X-based configuration
#make oldconfig # using old config from previous kernel version
# ... or manually edit .config
####################
# stop here
# this is useful to configure the kernel
#msg "Stopping build"
#return 1
####################
# yes "" | make config
# build!
make ${MAKEFLAGS} bzImage modules
}
Then I ran makepkg and wait. Nconfig showed up, but I was unable to manipulate anything with keyboard. When I pressed a key, it just displayed the letter in the bottom of my terminal (and displayed stuff like "^[OB" when I pressed the arrow keys). I did another run with menuconfig, the same thing happened.
I then extracted the kernel src tarball and did the compilation manually without makepkg. And both nconfig and menuconfig were fine. I also noticed that when I run nconfig manually, the window will fill up my terminal nicely, but not if I run it through makepkg.
Any suggestions?
Last edited by Corsair (2011-04-23 18:01:45)
Fear is the path to the darkside.
{My Config}
Offline
I uncommented `make nconfig' and commented `yes "" | make config'. So now my build() looks like this
I can't see where on that guide it says to comment 'yes "" | make config", I use the same method and I certainly don't do that.
EDIT/ Here is PKGBUILD I use - http://paste.pocoo.org/show/376935/
Last edited by Meyithi (2011-04-23 17:33:28)
Offline
Corsair wrote:I uncommented `make nconfig' and commented `yes "" | make config'. So now my build() looks like this
I can't see where on that guide it says to comment 'yes "" | make config", I use the same method and I certainly don't do that.
EDIT/ Here is PKGBUILD I use - http://paste.pocoo.org/show/376935/
I also tried to not comment that line. But as expected, that did not change the behavior of nconfig. Still did not work...
Fear is the path to the darkside.
{My Config}
Offline
I also tried to not comment that line. But as expected, that did not change the behavior of nconfig. Still did not work...
I don't understand, how was it expected? What is different from your PKGBUILD to mine because mine works? Where did you even get the idea to comment that line?
Last edited by Meyithi (2011-04-23 18:13:57)
Offline
I don't understand, how was it expected? What is different from your PKGBUILD to mine because mine works? Where did you even get the idea to comment that line?
You do aware that nconfig runs earlier than `make config' right? That means nconfig does not know the presence (or lack of it) of the `make config' line. You also assume that the same PKGBUILD will always yield the same result, which is not the case. Computer systems are not stateless.
Fear is the path to the darkside.
{My Config}
Offline
Ok. I got it. I was using a zsh alias that added color to the output of makepkg. Apparently, it messed with nconfig. Both nconfig and menuconfig are normal after I removed that alias.
This thread can be considered closed.
Last edited by Corsair (2011-04-23 22:27:25)
Fear is the path to the darkside.
{My Config}
Offline