error during make install with kernel 2.4.23

Bruce Hill · 12-23-2003, 08:20 PM

Can someone tell me what I've done that caused this error? I installed Slack 9.1 on this comp with the 2.4.22 kernel. Then I recompiled with 2.4.23. This happened at the make install step.

Code:

root@john:/usr/src/linux# make install
<snip>
inode.c: In function `smb_show_options':
inode.c:379: syntax error before "iso8859"
inode.c: In function `smb_read_super':
inode.c:473: syntax error before "iso8859"
make[3]: *** [inode.o] Error 1
make[3]: Leaving directory `/usr/src/linux-2.4.23/fs/smbfs'
make[2]: *** [first_rule] Error 2
make[2]: Leaving directory `/usr/src/linux-2.4.23/fs/smbfs'
make[1]: *** [_subdir_smbfs] Error 2
make[1]: Leaving directory `/usr/src/linux-2.4.23/fs'
make: *** [_dir_fs] Error 2
root@john:/usr/src/linux#

I put this under NFS

Code:

# Network File Systems
#
# CONFIG_CODA_FS is not set
# CONFIG_INTERMEZZO_FS is not set
CONFIG_NFS_FS=y
# CONFIG_NFS_V3 is not set
# CONFIG_NFS_DIRECTIO is not set
CONFIG_NFSD=y
# CONFIG_NFSD_V3 is not set
CONFIG_NFSD_TCP=y
CONFIG_SUNRPC=y
CONFIG_LOCKD=y
CONFIG_SMB_FS=y
CONFIG_SMB_NLS_DEFAULT=y
CONFIG_SMB_NLS_REMOTE=""iso8859-15""
# CONFIG_NCP_FS is not set
CONFIG_ZISOFS_FS=y

Is the problem the two sets of " marks around iso-8859-15 instead of one set? I've looked at my .config on my other comp, and that's all that's different between the two. If so, what is the easiest way for me to fix that and continue?

fancypiper · 12-23-2003, 11:06 PM

It sounds like a bug in your kernel config tool that you used. What kernel config tool did you run to get this?

I like make menuconfig myself and it always writes a good .config file.

I would be tempted to hand edit .config and try again.

Bruce Hill · 12-24-2003, 01:41 AM

Quote:

Originally posted by fancypiper
It sounds like a bug in your kernel config tool that you used. What kernel config tool did you run to get this?

I like make menuconfig myself and it always writes a good .config file.

I would be tempted to hand edit .config and try again.

I used make xconfig for the first time since the first time, if you catch my drift. Other than that one other time, I've always used make menuconfig. This box, my wife and daughter's comp, has an AMD and other significantly different hardware than my box - and I thought make xconfig was going to give me more info at the help prompts. Wrong!

I'm pretty sure this is what I messed up. When I came to the Native Language Support section for CONFIG_NLS_DEFAULT I put "iso8859-15" with the quotes, because I was looking at the config from my other box. It wouldn't have let me make that mistake if I'd used make menuconfig or make config (I don't think), but it apparently did with xconfig.

So, when I edit those extra set of quote marks out by hand, do I go back and start over and run from here? ->
make dep
make clean
make bzImage
make
make install (this is where I stopped)
make modules
make modules_install

or do I start with make oldconfig, or what?

At the moment I'm just confused at what I've got to do to get this kernel built properly.

gnashley · 12-24-2003, 08:49 AM

After manually editing the .config save it under another name. Then do
mrproper to get rid of all the old compile files. Then start over
make menuconfig
> load an alternate config file, type in the path to your config-some-name file
then:
make dep etc...

Bruce Hill · 12-24-2003, 09:00 AM

Thanks! It will probably be another day or so, seeing as how it's Christmas in the morning and past my bedtime now, but that's what I'll do.

Merry Christmas!!!

Jesus Christ, the reason for the celebration!!!

dfowensby · 12-24-2003, 11:13 PM

this may be easier: go to your unpacked kernel file (i use /usr/src/linux-2.x.x) check the /arch/i386/boot file, for defconfig.
as root, go to the new source, and do make mrproper.
copy your old defconfig from your 2.4.22 or whatever, or if you're REALLY lazy, copy the /boot/config-ide-2.4.22 file, paste it into the ~/linux-2.4.23/arch/i386/boot, delete the old resident defconfig and rename the new to defconfig. do make config, when it sets up, hold your Enter key down till the prompt comes back up for your root, and then do make dep && make bzImage && make modules && make modules_install && make install, edit/add your new lilo.conf boot entry, do /sbin/lilo, reboot, and enjoy your new kernel. if you have no particular kernel caressing needed, this is a cracker-jack way to pop in the new 2.6.0 kernel, too! Luck -O.

dfowensby · 12-24-2003, 11:27 PM

ooops.
forgot one crucial step: before you edit your lilo.conf (depending on where your unpacked source is), do:
cp /usr/src/linux-2.4.23/arch/i386/boot/bzImage /boot/vmlinuz-2.4.23. you might need an image to boot to, eh? sorry....
luck -O.

rypatros · 12-26-2003, 12:48 PM

Hey John:

Is this the correct directory /usr/src/linux where you untarred your new kernel source for the 2.4.23......because once you untar it, it should be something like linux-2.4.23 and in order to run the "make install" command, you have to be in the same directory where your kernel is compiled.

Also you need to be root when you run the "make install" command.

Bruce Hill · 12-26-2003, 05:28 PM

To conclude this thread ->

There wasn't a bug in my kernel config tool, but an error in my input. I was looking at a config file from my other comp, and when I entered the default NLS I put quotes around iso8859-15 just like in the config file that I was looking at. When you compile the kernel, it puts quote marks around this entry, so my quote marks were not necessary, and therefore created a second set which caused the syntax error before "iso8859" that you see in my post.

To fix this, I did edit the .config file I'd created by hand, as fancypiper suggested (thanks for the confirmation), removing the extra set of quote marks. Then I saved the file in my /home/anna directory as .config. Then I did make mrproper and after it removed all the previous config files, I did make menuconfig, and instead of configuring again, I chose Load an Alternate Config file as suggested by gnashley (thanks). However, I didn't save it with a different name, because I felt this may cause problems in the kernel, since it's looking for the name .config. Then I continued with the steps to build and install the new kernel ->
make dep
make clean
make bzImage
make
make install
make modules
make modules_install

and then I rebooted.

Thanks all for the helpful replies!

LQ is awesome!

dfowensby · 12-26-2003, 07:47 PM

hurrah! don't you just love it when everything works all at the same time?
luck -O