PKGBUILD error message(solved)

lilsirecho · 2005-01-10 02:31:24

Attempting to add a change to kernel 2.6.10 using ABS and receive this abort message.

What am I doing wrong?
____________________________________________________________
[root@n6re ~]# cd /var/abs/local
[root@n6re local]# makepkg PKGBUILD
==> Making package: kernel26-custom (Sun Jan 9 18:18:57 PST 2005)
==> Checking Runtime Dependencies...
==> Checking Buildtime Dependencies...
==> Retrieving Sources...
==> Using local copy of linux-2.6.10.tar.bz2
==> Found config in build dir
==> ERROR: logo_linux_clut224.ppm was not found in the build directory and is not a proper URL.
==> Aborting...
[root@n6re local]#

cactus · 2005-01-10 04:52:22

cd /var/abs/local
mkdir kernel26-custom
mv * kernel26-custom
cd kernel26-custom
makepkg

lilsirecho · 2005-01-10 05:15:39

Cactus; The following happens;
------------------------------------------------------------------------------------[root@n6re ~]# cd /var/abs/local
[root@n6re local]# mkdir kernel26-custom
[root@n6re local]# mv * kernel26-custom
mv: cannot move `kernel26-custom' to a subdirectory of itself, `kernel26-custom/kernel26-custom'
[root@n6re local]#

I'm wrong somewhere!! I am now using the wiki PKGBUILD with the....... make menuconfig....... option.

I am not sure what is to be entered for the default config which is entered at the beginning by the "source" entry.

No examples are given to help the un-initiated.....

Why aren't the entries you mention in the wiki?

The original error in the post came from using the downloaded PKGBUILD through ...abs. This introduced the logo statement which is adjacent to the "source" statement in the PKGBUILD and that represents an error.

I am trying to add one module to the kernel by enabling it as a module and I have a config file with that enabled. It resides in /var/abs/local along with the PKGBUILD.

I tried the makepkg with the wiki PKGBUILD and get an error that the loadable modules are not enabled.

What next?

lilsirecho · 2005-01-10 05:29:11

Ran ...makepkg PKGBUILD ....from Directory ...kernel26-custom... in /var/abs/local and received the following error;
------------------------------------------------------------------------------------Kernel: arch/i386/boot/bzImage is ready

The present kernel configuration has modules disabled.
Type 'make config' and enable loadable module support.
Then build a kernel with module support enabled.

make: *** [modules] Error 1
==> ERROR: Build Failed. Aborting...
[root@n6re kernel26-custom]#
[root@n6re kernel26-custom]#
[root@n6re kernel26-custom]#
[root@n6re kernel26-custom]#
[root@n6re kernel26-custom]#
[root@n6re kernel26-custom]#
[root@n6re kernel26-custom]#
[root@n6re kernel26-custom]#
[root@n6re kernel26-custom]#
[root@n6re kernel26-custom]#
[root@n6re kernel26-custom]#
[root@n6re kernel26-custom]#
[root@n6re kernel26-custom]#
[root@n6re kernel26-custom]#
[root@n6re kernel26-custom]#
[root@n6re kernel26-custom]#

lilsirecho · 2005-01-10 05:37:31

PKGBUILD:
------------------------------------------------------------------------------------###### Give the kernel a unique name (for multiple builds - can be empty)
_kerrev=custom

###### Choose generic name, version, and release. updated later for $_kerrev
pkgname=kernel26
pkgver=2.6.10
pkgrel=1
pkgdesc="Custom Linux Kernel and modules"
url="http://www.kernel.org"
depends=('module-init-tools')
###### Add a default config file and any patches to be applied to source array
source=(ftp://ftp.kernel.org/pub/linux/kernel/v2.6/linux-$pkgver.tar.bz2)
config= /var/abs/local
###### Add md5 checksums here:
#md5sums=()

getvar() {
old=$(cat Makefile | grep "^$1")
echo $(echo ${old/"$1 ="/} | sed -e "s/[ ]*(.*)[ ]*/1/g")
return 0
}

build() {
cd $startdir/src/linux-$pkgver

###### apply patches here
# patch -p1 < ../patch1 #model

#get rid of i in i686 in default config
carch=`echo $CARCH | sed 's|i||'`
cat ../config | sed "s|#CARCH#|$carch|g" >./.config

###### Choose one of the following configuration types
###### Use first option for config in source array
#yes "" | make config
#make oldconfig || return 1
make menuconfig
#make xconfig
#make gconfig

##### No user changes below here
# save the configuration with today's date
cp ./.config ../../NEWCONFIG-$(date +%b%d)

# set EXTRAVERSION to create unique /lib/modules/ subdirectories
_ker_extraversion=$(getvar "EXTRAVERSION")

# update EXTRAVERSION in the Makefile by adding our _kerrev
_oldline=$(cat Makefile | grep "^EXTRAVERSION")
if [ $_kerrev != "" ]; then
_ker_extraversion="$_ker_extraversion-$_kerrev"
cat Makefile | sed "s|$_oldline|EXTRAVERSION = $_ker_extraversion|" > tmpMake
mv tmpMake Makefile
fi

_kerrev=$_ker_extraversion
kerver=$(getvar "VERSION").$(getvar "PATCHLEVEL").$(getvar "SUBLEVEL")

# update the package information from the kernel Makefile
# (just in case the Makefile changed during a patch)
pkgver=$kerver$(echo $_kerrev | sed -e 's/-/./g')
pkgdesc="Custom Linux Kernel and modules version: $kerver revision: $_kerrev / package ver: $pkgver build: $pkgrel"

# changing the package name
# removing patches versions from the revision string
_t=$(echo $_kerrev | sed -e "s/^..[0-9]*//g")
# _t=$(echo $_t | sed -e "s/^-rc[0-9]?*//g")
# _suf contains the suffix identifying the kernel (it has the versions removed from it)
_suf=$(echo $_t | sed -e "s/[0-9]*-/-/g")
pkgname=kernel26$_suf

echo "Package name: $pkgname"
echo "Package ver: $pkgver"
echo "Package desc: $pkgdesc"
sleep 5

make clean bzImage modules || return 1
mkdir -p $startdir/pkg/{lib/modules,boot}
make INSTALL_MOD_PATH=$startdir/pkg modules_install || return 1
# create unique names in /boot/
cp System.map $startdir/pkg/boot/System.map26$_suf
cp arch/i386/boot/bzImage $startdir/pkg/boot/vmlinuz26$_suf

install -D -m644 Makefile $startdir/pkg/usr/src/linux-$kerver/Makefile
install -D -m644 .config $startdir/pkg/usr/src/linux-$kerver/.config
install -D -m644 .config $startdir/pkg/boot/kconfig26$_suf
mkdir -p $startdir/pkg/usr/src/linux-$kerver/include
mkdir -p $startdir/pkg/usr/src/linux-$kerver/arch/i386/kernel
for i in acpi asm-generic asm-i386 config linux math-emu net pcmcia scsi video; do
cp -a include/$i $startdir/pkg/usr/src/linux-$kerver/include/
done
# copy files necessary for later builds, like nvidia and vmware
cp -a scripts $startdir/pkg/usr/src/linux-$kerver/
mkdir -p $startdir/pkg/usr/src/linux-$kerver/.tmp_versions
cp arch/i386/Makefile $startdir/pkg/usr/src/linux-$kerver/arch/i386/
cp arch/i386/kernel/asm-offsets.s $startdir/pkg/usr/src/linux-$kerver/arch/i386/kernel/
# copy in Kconfig files
for i in `find . -name "Kconfig*"`; do
mkdir -p $startdir/pkg/usr/src/linux-$kerver/`echo $i | sed 's|/Kconfig.*||'`
cp $i $startdir/pkg/usr/src/linux-$kerver/$i
done
cd $startdir/pkg/usr/src/linux-$kerver/include && ln -s asm-i386 asm
chown -R root.root $startdir/pkg/usr/src/linux-$kerver
# create a unique subdirectory under /usr/src/
cd $startdir/pkg/usr/src
mv linux-$kerver linux-$kerver$_kerrev
cd $startdir/pkg/lib/modules/$kerver$_kerrev &&
(rm -f build; ln -sf /usr/src/linux-$kerver$_kerrev build)
}

dp · 2005-01-10 05:43:54

lilsirecho wrote:

==> ERROR: logo_linux_clut224.ppm was not found in the build directory and is not a proper URL.
==> Aborting...
[root@n6re local]#

this file is either in kernel26 or kernel26mm available:

http://cvs.archlinux.org/cgi-bin/viewcv … ag=CURRENT

lilsirecho · 2005-01-10 06:00:01

dp:

I do not understand the message in the code you posted..cryptic but not-informative.

The comment about kernel26 doesn't help me understand what I am supposed to do.

The wiki has a note about adding a... default config... or add a patch but no example as to how to do so in the pkgbuild...or isn't it needed?

I do not know the function supplied by the entry in the abs pkgbuild as is stated in the code you posted nor do I think I need it to change one module enable in the kernel config and build a custom kernel.

The wiki PKGBUILD does not have such coding.

Whazzup?

dp · 2005-01-10 06:23:21

lilsirecho wrote:

dp:
I do not understand the message in the code you posted..cryptic but not-informative.
The comment about kernel26 doesn't help me understand what I am supposed to do.
The wiki has a note about adding a... default config... or add a patch but no example as to how to do so in the pkgbuild...or isn't it needed?
I do not know the function supplied by the entry in the abs pkgbuild as is stated in the code you posted nor do I think I need it to change one module enable in the kernel config and build a custom kernel.
The wiki PKGBUILD does not have such coding.
Whazzup?

source=(ftp://ftp.kernel.org/pub/linux/kernel/v2.6/linux-$pkgver.tar.bz2 
  config logo_linux_clut224.ppm)

means, that you have one file downloading from the internet and 2 that are already available in the main dir you start makepkg

[root@Asteraceae kernel26]# pwd
/var/abs/kernels/kernel26
[root@Asteraceae kernel26]# ls
PKGBUILD      cdburning.patch  filelist          logo_linux_clut224.ppm
System.map26  config           kernel26.install

if you take the PKGBUILD of CURRENT or EXTRA to build a kernel pkg, you need not only PKGBUILD but also kernel26.install, config and logo_linux_clut224.ppm in the same directory ... and maybe also a patch

the link i posted is the link to the web-cvs where you can find the file if you do not use abs ... if you use abs, copy logo_linux_clut224.ppm and config to the dir you build your custom kernel, or modify the PKGBUILD so that does not need these files

good starting points:
http://cvs.archlinux.org/cgi-bin/viewcv … ag=CURRENT
or
http://cvs.archlinux.org/cgi-bin/viewcv … ag=CURRENT

good luck

lilsirecho · 2005-01-10 06:42:15

I am further confused since the wiki doesn't do the job it is designed to do.

I have to pass on this project , altho I have built a kernel nicely in the past with abs with no special downloads and patches.

Maybe things will clear up (or get more confusing) later this year.

Thanks for the try.

dp · 2005-01-10 09:23:26

lilsirecho wrote:

I am further confused since the wiki doesn't do the job it is designed to do.
I have to pass on this project , altho I have built a kernel nicely in the past with abs with no special downloads and patches.
Maybe things will clear up (or get more confusing) later this year.
Thanks for the try.

if you want to build a kernel in abs, then this is the way:

[root@Asteraceae /]# abs
Connected to cvs.archlinux.org
Updating collection arch/cvs
Finished successfully
Connected to cvs.archlinux.org
Updating collection extra/cvs
 Edit extra/gnome/gnome-system-monitor/PKGBUILD
 Checkout extra/gnome/gnome-system-monitor/gsm-2.8.1.patch
Finished successfully
[root@Asteraceae /]# cd var/abs/kernels/kernel26

then edit PKGBUILD to use menuconfig

[root@Asteraceae kernel26]# makepkg

... and if you want a custom kernel, then copy the contents of /var/abs/kernels/kernel26 to /var/abs/local/kernel26custom and edit also the $pkgname to prevent conflicts with the default

also i recommend always having more than one kernel installed, as it can save you time (or knoppix)

lilsirecho · 2005-01-10 16:00:22

As I said, I pass, no more chasing.

lilsirecho · 2005-01-10 16:00:56

As I said, I pass, no more chasing.

lilsirecho · 2005-01-10 16:00:56

As I said, I pass, no more chasing.

lilsirecho · 2005-01-11 22:17:39

Solution involved transferring all of the Kernel26 files in the abs download of /var/abs/kernels/kernel26 to the work-up fileof /var/abs/local/kernel26-custom.

The erroneous assumption that only the config and PKGBUILD were necessary in the /var/abs/local/kernel26-custom file as the wiki only refers to those two as necessary to make changes. That led to dismal failure because all of the files need be present to.... makepkg.

As the gal says on TV...."never mind"!!!

sarah31 · 2005-01-11 23:01:37

just so you know the wiki and other such howtos will always be rather generic. Normally this would not be a problem because the generic thing for an arch kernel is to be pretty much vanilla with no patches applied.

The best thing to do would be to log on and edit the wiki to mention that ALL files existing in the current kernel build directory you are going to be working on should be copied over. This ensures that any current arch applied modifications will be carried over as well.

(However, this may be a bit too obvious to anyone who has messed around with PKGBUILDs before. When you deal with building stuff all the time you are not usually the best person for writing a wiki howto since you commonly forget the obvious (in this case copying over all files).)

Arch Linux

#1 2005-01-10 02:31:24

PKGBUILD error message(solved)

#2 2005-01-10 04:52:22

Re: PKGBUILD error message(solved)

#3 2005-01-10 05:15:39

Re: PKGBUILD error message(solved)

#4 2005-01-10 05:29:11

Re: PKGBUILD error message(solved)

#5 2005-01-10 05:37:31

Re: PKGBUILD error message(solved)

#6 2005-01-10 05:43:54

Re: PKGBUILD error message(solved)

#7 2005-01-10 06:00:01

Re: PKGBUILD error message(solved)

#8 2005-01-10 06:23:21

Re: PKGBUILD error message(solved)

#9 2005-01-10 06:42:15

Re: PKGBUILD error message(solved)

#10 2005-01-10 09:23:26

Re: PKGBUILD error message(solved)

#11 2005-01-10 16:00:22

Re: PKGBUILD error message(solved)

#12 2005-01-10 16:00:56

Re: PKGBUILD error message(solved)

#13 2005-01-10 16:00:56

Re: PKGBUILD error message(solved)

#14 2005-01-11 22:17:39

Re: PKGBUILD error message(solved)

#15 2005-01-11 23:01:37

Re: PKGBUILD error message(solved)

Board footer