Re: kernel compile error in wheezy [solved!]
On Tue, 19 Jul 2011 00:29:49 -0400 (EDT), Frank Miles wrote: > > Thanks to everyone who helped - yes, it was indeed something about > my environment. In /etc/profile, I've long exported an environment > variable of the form: > > export LIBRARY_PATH="/home/myname/devel/lib:." > > I have a dim memory that when compiling cross-compilers that the > '.' directory is a problem. Commenting this out allows the kernel > compile to proceed. What's strange is that I've had this for many > years without any kernel-compile problem. No longer! > > There may be some gcc docs that warn of this, not sure exactly where, > but it might shed more light on this situation. > > Thanks again, everyone- Glad you got it working. Thanks for the follow-up. -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1196455862.778722.137811653.javamail.r...@md01.wow.synacor.com
Re: kernel compile error in wheezy [solved!]
Thanks to everyone who helped - yes, it was indeed something about my environment. In /etc/profile, I've long exported an environment variable of the form: export LIBRARY_PATH="/home/myname/devel/lib:." I have a dim memory that when compiling cross-compilers that the '.' directory is a problem. Commenting this out allows the kernel compile to proceed. What's strange is that I've had this for many years without any kernel-compile problem. No longer! There may be some gcc docs that warn of this, not sure exactly where, but it might shed more light on this situation. Thanks again, everyone- Frank -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/alpine.lrh.2.01.1107182120300.6...@homer01.u.washington.edu
Re: kernel compile error in wheezy
On Sun, 17 Jul 2011 13:35:00 -0400 (EDT), Frank Miles wrote: > Stephen wrote: >> ... >> I'm guessing that elks-libc is what is needed. Is that package installed >> on your system? >> ... > > No, it's not installed. Sure seems strange, requiring a 16-bit library > for the build of a 64-bit system. I have stdarg.h from gcc versions 4.3, > 4.4, and 4.6, and libstdc++ of the same versions. But it would be an > easy solution, so... (installing,.. retrying...): > -> still fails :( Hmm. Well, I'm not sure what to suggest. It's obviously something strange in your environment, since many others have been able to successfully compile the kernel. You might try deleting the kernel source code directory and unpack the tar file again. Maybe something got hosed up somehow. The only other thing I might suggest is to delete older versions of the C compiler and libraries until you have only the newest one or until you find an installed package that requires an older library. Then try again. -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/542932932.734934.1310945631739.javamail.r...@md01.wow.synacor.com
Re: kernel compile error in wheezy
Thanks to Stan, Stephen, and Maderios! - Stan wrote: Do you get the same error using the (new) Debian kernel method? $ make KDEB_PKGVERSION=custom.1.0 deb-pkg I'll have to learn more about the new method for the future. For right now, unfortunately the answer is yes, I get the same error. - Stephen wrote: ... I'm guessing that elks-libc is what is needed. Is that package installed on your system? ... No, it's not installed. Sure seems strange, requiring a 16-bit library for the build of a 64-bit system. I have stdarg.h from gcc versions 4.3, 4.4, and 4.6, and libstdc++ of the same versions. But it would be an easy solution, so... (installing,.. retrying...): -> still fails :( - Maderios wrote: For my part: make-kpkg kernel_image --initrd and it works. Same error - it bombs on compiling arch/x86/kernel/asm-offsets.c, in each case looking for included file stdarg.h [again, I have at least 6 versions of this file depending on compiler]. Thanks for trying! I'm mystified, having compiled many kernels over the years on a various computers without difficulty. Is there any way that I could have mangled the include search path? I'm using bash as the shell interpreter, that's still ok isn't it? -Frank -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/alpine.lrh.2.01.1107171013290.13...@homer01.u.washington.edu
Re: kernel compile error in wheezy
$ uname -a Linux debian 2.6.39.1 #1 SMP PREEMPT Tue Jun 7 01:40:05 CEST 2011 x86_64 GNU/Linux is a self-build (rt patch emu kernel) with source from kernel.org and at least 2.6.39-2 from the repositories was ok too, didn't tested the upgrade to 2.6.39-3 until now, which btw. still is named 2.6.39-2. I build by running make-kpkg --rootcmd fakeroot --initrd kernel-image kernel-headers of cause I don't add staging (or what ever it is named, that couldn't be used with real rt-patches) and some other thingies, that are unimportant for my usage. Hm, yes, my architecture is amd64. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1310920578.8771.6.camel@debian
Re: kernel compile error in wheezy
On 07/16/2011 08:19 PM, Frank Miles wrote: I just tried compiling the kernel for My 'wheezy' system (2.6.39) [amd64]. As I've done many times - using make-kpkg --revision N kernel_image Hi For my part: make-kpkg kernel_image --initrd and it works. greetings Maderios -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e22afd4.4010...@gmail.com
Re: kernel compile error in wheezy
On 7/16/2011 1:19 PM, Frank Miles wrote: > I just tried compiling the kernel for My 'wheezy' system (2.6.39) [amd64]. > As I've done many times - using > make-kpkg --revision N kernel_image > But with the recent linux-source update - shortly after starting I get: Do you get the same error using the (new) Debian kernel method? $ make KDEB_PKGVERSION=custom.1.0 deb-pkg -- Stan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e226a84.50...@hardwarefreak.com
Re: kernel compile error in wheezy
On Sat, 16 Jul 2011 14:19:17 -0400 (EDT), Frank Miles wrote: > > I just tried compiling the kernel for My 'wheezy' system (2.6.39) [amd64]. > As I've done many times - using > make-kpkg --revision N kernel_image > But with the recent linux-source update - shortly after starting I get: > > CC arch/x86/kernel/asm-offsets.s > In file included from > /usr/src/linux-source-2.6.39/arch/x86/include/asm/percpu.h:44:0, > from > /usr/src/linux-source-2.6.39/arch/x86/include/asm/current.h:5, > from > /usr/src/linux-source-2.6.39/arch/x86/include/asm/processor.h:15, > from > /usr/src/linux-source-2.6.39/arch/x86/include/asm/atomic.h:6, > from ./include/linux/crypto.h:20, > from arch/x86/kernel/asm-offsets.c:8: > ./include/linux/kernel.h:12:20: fatal error: stdarg.h: No such file or > directory > compilation terminated. > make[3]: *** [arch/x86/kernel/asm-offsets.s] Error 1 > make[2]: *** [prepare0] Error 2 > > There don't seem to be any current bugs like this. A previous 2.6.39 > compiler was uneventful. > > Any ideas would be appreciated! Using the procedures found at http://users.wowway.com/~zlinuxman/Kernel.htm I cannot reproduce your error. I am using package linux-source-2.6.39, version 2.6.39-3. I have tried two machine architectures: s390 and i386, but not amd64. On my i386 system, there are four files ending in stdarg.h. They are as follows: /usr/lib/bcc/include/stdarg.h /usr/lib/i386-linux-gnu/gcc/i486-linux-gnu/4.5/include/stdarg.h /usr/lib/i386-linux-gnu/gcc/i486-linux-gnu/4.6/include/stdarg.h /usr/include/c++/4.6/tr1/stdarg.h These files belong to the elks-libc, gcc-4.5, gcc-4.6, and libstdc++6-4.6-dev packages, respectively. Since libstdc++6-4.6-dev is for c++, and obviously either gcc-4.5 or gcc-4.6, or both, must be already installed (or you wouldn't be able to compile anything), I'm guessing that elks-libc is what is needed. Is that package installed on your system? elks-libc is a recommendation (and not a dependency) of bcc; so you may not have it installed on your system if you are in the habit of installing only dependencies and skipping recommendations. But it looks like it may be a requirement for compiling the kernel. -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/755477887.725131.1310868477179.javamail.r...@md01.wow.synacor.com
Re: kernel compile error
that worked, strange, did some stuff change in the config file? -JSS [EMAIL PROTECTED] wrote: Jule The /usr/include/version.h in general does not match the /usr/src/linux/include/linux/version.h which will be created during a kernel configureation Try # make mrproper before # make bzImage MarvS Original Message: - From: Jule Slootbeek [EMAIL PROTECTED] Date: Fri, 22 Oct 2004 15:32:25 -0400 To: [EMAIL PROTECTED] Subject: kernel compile error Hey all I'm just trying to install 2.6.9 and am getting this error, i have no idea why dolphy:/usr/src/linux# make bzImage /bin/sh: Syntax error: Unterminated quoted string make: *** [include/linux/version.h] Error 2 the only include/linux/version.h i can find is in /usr/include/linux/ which looks like this #define UTS_RELEASE "2.6.0-test7" #define LINUX_VERSION_CODE 132608 #define KERNEL_VERSION(a,b,c) (((a) << 16) + ((b) << 8) + (c)) I'm not sure why it says 2.6.0-test7, but for the rest i don't see anything wrong with this. anybody ahve an idea? thanks -JSS -- Jule Slootbeek [EMAIL PROTECTED] http://www.thesloot.com 617 901 6958 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: kernel compile error
Jule The /usr/include/version.h in general does not match the /usr/src/linux/include/linux/version.h which will be created during a kernel configureation Try # make mrproper before # make bzImage MarvS Original Message: - From: Jule Slootbeek [EMAIL PROTECTED] Date: Fri, 22 Oct 2004 15:32:25 -0400 To: [EMAIL PROTECTED] Subject: kernel compile error Hey all I'm just trying to install 2.6.9 and am getting this error, i have no idea why dolphy:/usr/src/linux# make bzImage /bin/sh: Syntax error: Unterminated quoted string make: *** [include/linux/version.h] Error 2 the only include/linux/version.h i can find is in /usr/include/linux/ which looks like this #define UTS_RELEASE "2.6.0-test7" #define LINUX_VERSION_CODE 132608 #define KERNEL_VERSION(a,b,c) (((a) << 16) + ((b) << 8) + (c)) I'm not sure why it says 2.6.0-test7, but for the rest i don't see anything wrong with this. anybody ahve an idea? thanks -JSS -- Jule Slootbeek [EMAIL PROTECTED] http://www.thesloot.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] mail2web - Check your email from the web at http://mail2web.com/ .
Re: kernel compile error
> I had this, but no Modules (like I siad before). I tried to Compile > 2.4.22 from kernel.org and get now the same Errors. > It's confusing, I remove the directory, decompress it again, do an > make oldconfig && make dep && make and get the same Error on another > file. The Error is sometimes here and sometimes anywhere. Now I try > to do a module an all that I don't really need to be compiled in. > Seems that we have to try until it works, because noone seems to care > on this Thread or Problem. You and I not counted :-). As far as I can remember, I couldn't run the 2.4.20 kernel image on that computer. It hangs somewhere at disk checking (not fs, before that). Same with the Knoppix CD, which also uses that kernel. This is an old computer where I have a 120 and 60 GB disk in. If I enter the bios setup and I go to the disk page, the bios cannot recognize the disk and hangs. Nevertheless the woody CD could be started and installed. So maybe it has something to do with the bios setup. I have to check the exact error messages. Maybe someone else on this list gets an idea what could be wrong. The problem is, that this computer is not local. So, I have to get there to do this. I should do this soon. How old is your computer? Similar situation? Florian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kernel compile error
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Mittwoch, 17. September 2003 17:00 schrieb Florian Sukup: > Is that what you mean? It's y at my configuration. But it does > compile correctly. Any other ideas? I had this, but no Modules (like I siad before). I tried to Compile 2.4.22 from kernel.org and get now the same Errors. It's confusing, I remove the directory, decompress it again, do an make oldconfig && make dep && make and get the same Error on another file. The Error is sometimes here and sometimes anywhere. Now I try to do a module an all that I don't really need to be compiled in. Seems that we have to try until it works, because noone seems to care on this Thread or Problem. You and I not counted :-). - -- MfG usw Werner Mahr GPG-Key-ID 9CCBC2B0 Registered-Linux-User: 303822 (http://counter.li.org) ICQ-Nr. 317910541 -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE/aH85OUGIhpzLwrARAi/eAKCu0fURGbVP27Lz/mKE1utZdf5gKQCcCG8P 8qgzUO1HrrVfLiInrJNBrCY= =A2fA -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kernel compile error
On Tue, Sep 16, 2003 at 04:44:57PM +0200, Werner Mahr wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Am Dienstag, 16. September 2003 16:13 schrieb Florian Sukup: > > What do you mean with 'Kernelconfig'? Is it > > /usr/src/kernel-source-2.4.20/.config? Or a tool which I don't > > know? > I mean .config, sorry. # # Loadable module support # CONFIG_MODULES=y CONFIG_MODVERSIONS=y CONFIG_KMOD=y Is that what you mean? It's y at my configuration. But it does compile correctly. Any other ideas? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kernel compile error
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Dienstag, 16. September 2003 16:13 schrieb Florian Sukup: > What do you mean with 'Kernelconfig'? Is it > /usr/src/kernel-source-2.4.20/.config? Or a tool which I don't > know? I mean .config, sorry. - -- MfG usw Werner Mahr GPG-Key-ID 9CCBC2B0 Registered-Linux-User: 303822 (http://counter.li.org) ICQ-Nr. 317910541 -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE/ZyHsOUGIhpzLwrARAk3vAJ91wj2DAObM52xZAtDs2dRDXnbcAQCeM/3b tfPtRSyTjBM1LxVVZiImbJI= =lqoo -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kernel compile error
Thank you for your reply. > > I had the same Problem when I tried to compile my Kernel. I had in > Kernelconfig no Modules configured, moduleloader was included (nvidia > etc.). 2 Minutes before I got your Mail I tried it with Modules and > it worked. I don't know if this was the Error but its the only thing > I changed. What do you mean with 'Kernelconfig'? Is it /usr/src/kernel-source-2.4.20/.config? Or a tool which I don't know? > Maybe you have not gcc-2.95, I had a newer one and deinstalled it, > but I don't know if I tried it after that before today. I have gcc 2.95.4-14 installed Thanks in advance further info. Florian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kernel compile error
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Dienstag, 16. September 2003 14:16 schrieb Florian Sukup: [Many things with many output] I had the same Problem when I tried to compile my Kernel. I had in Kernelconfig no Modules configured, moduleloader was included (nvidia etc.). 2 Minutes before I got your Mail I tried it with Modules and it worked. I don't know if this was the Error but its the only thing I changed. Maybe you have not gcc-2.95, I had a newer one and deinstalled it, but I don't know if I tried it after that before today. - -- MfG usw Werner Mahr GPG-Key-ID 9CCBC2B0 Registered-Linux-User: 303822 (http://counter.li.org) ICQ-Nr. 317910541 -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE/Zwx0OUGIhpzLwrARAp2nAJ9gxClrLAPQjH20XzepdVyg90IdgwCfffU+ A2NCXaI1ZDqFox0sJ4FA26U= =T3Hs -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kernel compile error with make-kpkg
On Sat, 12 Jul 2003 17:15:13 +0200 "Esben Laursen" <[EMAIL PROTECTED]> wrote: > [ past traffic trimmed ] > > The funny part is that if I do a "make dep && make && make modules" > there is no error message and it compile correct. why is that? Read your original error messages again. You're not running into compile problems; you're running into problems with depmod. It *compiled* correctly for you under make-kpkg, just as it does for you with "make dep && make && make modules". But make-kpkg does more than just those things; it also verifies that your module set will work through depmod, and in your case it runs into trouble. If after "make dep && make && make modules" you tried to *install and run* that kernel/module set, you'd have run into the same trouble, I'd bet. Right about when it ran depmod in order to build the dependency file for modprobe to use. So what about all the rest of the stuff I typed; was it helpful? -c -- Chris Metzler [EMAIL PROTECTED] (remove "snip-me." to email) "As a child I understood how to give; I have forgotten this grace since I have become civilized." - Chief Luther Standing Bear -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kernel compile error with make-kpkg
On Sat, 12 Jul 2003 17:15:13 +0200 "Esben Laursen" <[EMAIL PROTECTED]> wrote: Please trim replies. > The funny part is that if I do a "make dep && make && make modules" there > is no error message and it compile correct. why is that? > > Could it be possible that I are missing some kind of lib to the > kernel-package where make-kpkg is in?? How do you know it compiles correctly? Have you installed and run the kernel that results? make-kpkg is a script; it requires no libraries so that's not the issue. Kevin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kernel compile error with make-kpkg
On Sat, 12 Jul 2003 13:39:35 +0200 "JZidar" <[EMAIL PROTECTED]> wrote: > Isn't the correct syntax something like: > make-kpkg --append-to-version=.something kernel_image (note the = and .)? The period isn't required; I used it to separate the kernel version from the rest of the append-to-version value. I thought the = was required but apparently it isn't. Many people report using "--append-to-version " and it works. Kevin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kernel compile error with make-kpkg
- Original Message -
From: "Chris Metzler" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: "Esben Laursen" <[EMAIL PROTECTED]>
Sent: Saturday, July 12, 2003 3:18 PM
Subject: Re: Kernel compile error with make-kpkg
> On Sat, 12 Jul 2003 13:08:39 +0200
> "Esben Laursen" <[EMAIL PROTECTED]> wrote:
> > From: "Chris Metzler" <[EMAIL PROTECTED]>
> > >On Fri, 11 Jul 2003 23:50:06 +0200
> > >"Esben Laursen" <[EMAIL PROTECTED]> wrote:
> >>>
> >>> Here is the error I get:
> >>>
> >>> cd /usr/src/linux/debian/tmp-image/lib/modules/2.4.21-test; \
> >>> mkdir -p pcmcia; \
> >>> find kernel -path '*/pcmcia/*' -name '*.o' | xargs -i -r ln -sf
> >>> ../{} pcmcia if [ -r System.map ]; then /sbin/depmod -ae -F
> >>> System.map -b/usr/src/linux/debian/tmp-image -r 2.4.21-test; fi
> >>> depmod: *** Unresolved symbols in
> >>> /usr/src/linux/debian/tmp-image/lib/modules/2.4.21-test/kernel/driv
> >>> ers/ media/radio/miropcm20.o depmod:
> >>> aci_rw_cmd_Rsmp_cc7c4cd8 depmod: aci_port_Rsmp_0d82adb6
> >>> depmod: aci_version_Rsmp_93350c87
> >>> depmod: *** Unresolved symbols in
> >>> /usr/src/linux/debian/tmp-image/lib/modules/2.4.21-test/kernel/driv
> >>> ers/ net/wan/comx.o depmod: proc_get_inode
> >>> make[2]: *** [_modinst_post] Error 1
> >>> make[2]: Leaving directory `/usr/src/linux-2.4.21'
> >>> make[1]: *** [real_stamp_image] Error 2
> >>> make[1]: Leaving directory `/usr/src/linux-2.4.21'
> >>>
> >>> Can anyone help me with what's wrong??
> >>
> >> You need to provide more information than you've given. Specifically,
> >> what version of gcc did you use (the output of linux/scripts/ver_linux
> >> would provide lots of info, but the gcc version you're using is
> >> probably enough). Also, and especially, what architecture are you on,
> >> and did you specify that architecture in your kernel config?
> >
> > Here is the output from a gcc -v
> > Reading specs from /usr/lib/gcc-lib/i386-linux/2.95.4/specs
> > gcc version 2.95.4 20011002 (Debian prerelease)
> >
> > Im trying to compile a kernel with support for the PII CPU, and my
> > kernel now is a standart Debain kernel-image-2.4.18-bf2.4 with the 386
> > architecture. Im also importing the /boot/config-2.4.18-bf2.4 from the
> > "make menuconfig" so that I get all the things I need and only have to
> > change a few things like the architecture. I've attached the
> > /usr/src/linux/scripts/var_linux file so you can see it.
>
> Heh, OK, but as I wrote above, what I was interested in was the *output*
> from var_linux, not the contents of the script itself. But you gave me
> the most important thing that output would have told me, which was your
> gcc version.
>
> The reason I was interested in gcc version is because there have been
> numerous and various problems lately compiling kernels with gcc 3.3.
> In some cases, for reasons I don't understand and other people here
> probably do, this has resulted in unresolved symbols issues, akin to
> what you ran into (mistakes in parsing the text of files, maybe?). But
> no probs have been reported with 2.95 -- in fact, that's what most
> people who've experienced problems with 3.3 have dropped back to -- and
> 2.95 is what you're using. So that probably isn't it.
>
> I was also curious about architecture because I was wondering if you
> were trying to make a kernel for an architecture other than x86. The
> reason: the errors you're getting are for drivers for some old ISA
> bus hardware from the mid-90's; and in Googling, I found instances of
> people getting errors like this when compiling on architectures that
> didn't even support the ISA bus in the first place. But, you're
> compiling for a PII, so that isn't it either.
>
> In the meantime, though, until someone with more clue than I jumps
> in, the below may help.
>
> The first error:
>
> } depmod: *** Unresolved symbols in
> /usr/src/linux/debian/tmp-image/lib/modules/2.4.21-test/kernel/drivers/media/radio/miropcm20.o
> } depmod: aci_rw_cmd_Rsmp_cc7c4cd8
> } depmod: aci_port_Rsmp_0d82adb6
> } depmod: aci_version_Rsmp_93350c87
>
> This is coming from miropcm20.o, which is the driver for the MiroSOUND
> PCM20 radio card. Do you need that driver? If not, you could turn it
> off, and
Re: Kernel compile error with make-kpkg
On Sat, 12 Jul 2003 13:08:39 +0200
"Esben Laursen" <[EMAIL PROTECTED]> wrote:
> From: "Chris Metzler" <[EMAIL PROTECTED]>
> >On Fri, 11 Jul 2003 23:50:06 +0200
> >"Esben Laursen" <[EMAIL PROTECTED]> wrote:
>>>
>>> Here is the error I get:
>>>
>>> cd /usr/src/linux/debian/tmp-image/lib/modules/2.4.21-test; \
>>> mkdir -p pcmcia; \
>>> find kernel -path '*/pcmcia/*' -name '*.o' | xargs -i -r ln -sf
>>> ../{} pcmcia if [ -r System.map ]; then /sbin/depmod -ae -F
>>> System.map -b/usr/src/linux/debian/tmp-image -r 2.4.21-test; fi
>>> depmod: *** Unresolved symbols in
>>> /usr/src/linux/debian/tmp-image/lib/modules/2.4.21-test/kernel/driv
>>> ers/ media/radio/miropcm20.o depmod:
>>> aci_rw_cmd_Rsmp_cc7c4cd8 depmod: aci_port_Rsmp_0d82adb6
>>> depmod: aci_version_Rsmp_93350c87
>>> depmod: *** Unresolved symbols in
>>> /usr/src/linux/debian/tmp-image/lib/modules/2.4.21-test/kernel/driv
>>> ers/ net/wan/comx.o depmod: proc_get_inode
>>> make[2]: *** [_modinst_post] Error 1
>>> make[2]: Leaving directory `/usr/src/linux-2.4.21'
>>> make[1]: *** [real_stamp_image] Error 2
>>> make[1]: Leaving directory `/usr/src/linux-2.4.21'
>>>
>>> Can anyone help me with what's wrong??
>>
>> You need to provide more information than you've given. Specifically,
>> what version of gcc did you use (the output of linux/scripts/ver_linux
>> would provide lots of info, but the gcc version you're using is
>> probably enough). Also, and especially, what architecture are you on,
>> and did you specify that architecture in your kernel config?
>
> Here is the output from a gcc -v
> Reading specs from /usr/lib/gcc-lib/i386-linux/2.95.4/specs
> gcc version 2.95.4 20011002 (Debian prerelease)
>
> Im trying to compile a kernel with support for the PII CPU, and my
> kernel now is a standart Debain kernel-image-2.4.18-bf2.4 with the 386
> architecture. Im also importing the /boot/config-2.4.18-bf2.4 from the
> "make menuconfig" so that I get all the things I need and only have to
> change a few things like the architecture. I've attached the
> /usr/src/linux/scripts/var_linux file so you can see it.
Heh, OK, but as I wrote above, what I was interested in was the *output*
from var_linux, not the contents of the script itself. But you gave me
the most important thing that output would have told me, which was your
gcc version.
The reason I was interested in gcc version is because there have been
numerous and various problems lately compiling kernels with gcc 3.3.
In some cases, for reasons I don't understand and other people here
probably do, this has resulted in unresolved symbols issues, akin to
what you ran into (mistakes in parsing the text of files, maybe?). But
no probs have been reported with 2.95 -- in fact, that's what most
people who've experienced problems with 3.3 have dropped back to -- and
2.95 is what you're using. So that probably isn't it.
I was also curious about architecture because I was wondering if you
were trying to make a kernel for an architecture other than x86. The
reason: the errors you're getting are for drivers for some old ISA
bus hardware from the mid-90's; and in Googling, I found instances of
people getting errors like this when compiling on architectures that
didn't even support the ISA bus in the first place. But, you're
compiling for a PII, so that isn't it either.
In the meantime, though, until someone with more clue than I jumps
in, the below may help.
The first error:
} depmod: *** Unresolved symbols in
/usr/src/linux/debian/tmp-image/lib/modules/2.4.21-test/kernel/drivers/media/radio/miropcm20.o
} depmod: aci_rw_cmd_Rsmp_cc7c4cd8
} depmod: aci_port_Rsmp_0d82adb6
} depmod: aci_version_Rsmp_93350c87
This is coming from miropcm20.o, which is the driver for the MiroSOUND
PCM20 radio card. Do you need that driver? If not, you could turn it
off, and this problem may very well go away. But in the meantime, when
I read about this driver in linux/Documentation/Configure.help, I see:
} miroSOUND PCM20 radio
} CONFIG_RADIO_MIROPCM20
} Choose Y here if you have this FM radio card. You also need to say Y
} to "ACI mixer (miroSOUND PCM1-pro/PCM12/PCM20 radio)" (in "Sound")
} for this to work.
Note that last sentence. The unresolved symbols you're getting are all
defined in linux/drivers/sound/aci.c or aci.h (hence the "aci_" prefix).
If you need support for this card (the MiroSOUND PCM20), then you also
need to turn on CONFIG_SOUND_ACI_MIXER under the sound section. I'm
betting you don't have that turned on when you should, and that's the
reasons for these unresolved symbol messages. If I'm right, then you
need to either have them both on, or both off, as per that last sentence
quoted above.
Incidentally, normally, there should be code in the miropcm20-radio.c
driver that prevents the compile of that driver if you haven't set the
config options it depends on (in this case, CONFIG_SOUND_ACI_MIXER); it
doesn't look like that code is t
Re: Kernel compile error with make-kpkg
- Original Message -
From: "Esben Laursen" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, July 12, 2003 1:08 PM
Subject: Re: Kernel compile error with make-kpkg
- Original Message -
From: "Chris Metzler" <[EMAIL PROTECTED]>
To: "Esben Laursen" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Saturday, July 12, 2003 12:43 AM
Subject: Re: Kernel compile error with make-kpkg
> On Fri, 11 Jul 2003 23:50:06 +0200
> "Esben Laursen" <[EMAIL PROTECTED]> wrote:
> >
> > When I try to compile a 2.4.21 kernel with Debians make-kpkg tool, I get
> > this error no matter what I try!! The command im useing is: make-kpkg
> > --append_to_version -test kernel-image
> >
> > I think it's when the package is being build there is an error, or am I
> > wrong?
> >
> > Here is the error I get:
> >
> > cd /usr/src/linux/debian/tmp-image/lib/modules/2.4.21-test; \
> > mkdir -p pcmcia; \
> > find kernel -path '*/pcmcia/*' -name '*.o' | xargs -i -r ln -sf ../{}
> > pcmcia if [ -r System.map ]; then /sbin/depmod -ae -F System.map -b
> > /usr/src/linux/debian/tmp-image -r 2.4.21-test; fi depmod: ***
> > Unresolved symbols in
> > /usr/src/linux/debian/tmp-image/lib/modules/2.4.21-test/kernel/drivers/
> > media/radio/miropcm20.o depmod: aci_rw_cmd_Rsmp_cc7c4cd8
> > depmod: aci_port_Rsmp_0d82adb6
> > depmod: aci_version_Rsmp_93350c87
> > depmod: *** Unresolved symbols in
> > /usr/src/linux/debian/tmp-image/lib/modules/2.4.21-test/kernel/drivers/
> > net/wan/comx.o depmod: proc_get_inode
> > make[2]: *** [_modinst_post] Error 1
> > make[2]: Leaving directory `/usr/src/linux-2.4.21'
> > make[1]: *** [real_stamp_image] Error 2
> > make[1]: Leaving directory `/usr/src/linux-2.4.21'
> >
> > Can anyone help me with what's wrong??
>
> You need to provide more information than you've given. Specifically,
> what version of gcc did you use (the output of linux/scripts/ver_linux
> would provide lots of info, but the gcc version you're using is probably
> enough). Also, and especially, what architecture are you on, and did
> you specify that architecture in your kernel config?
>
> -c
>
> --
> Chris Metzler [EMAIL PROTECTED]
>
>Here is the output from a gcc -v
>Reading specs from /usr/lib/gcc-lib/i386-linux/2.95.4/specs
>gcc version 2.95.4 20011002 (Debian prerelease)
>
>Im trying to compile a kernel with support for the PII CPU, and my kernel
>now is a standart >Debain kernel-image-2.4.18-bf2.4 with the 386
>architecture.
>Im also importing the /boot/config-2.4.18-bf2.4 from the "make menuconfig"
>so that I get all the >things I need and only have to change a few things
>like the architecture.
>I've attached the /usr/src/linux/scripts/var_linux file so you can see it.
Isn't the correct syntax something like:
make-kpkg --append-to-version=.something kernel_image (note the = and .)?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kernel compile error with make-kpkg
- Original Message -
From: "Chris Metzler" <[EMAIL PROTECTED]>
To: "Esben Laursen" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Saturday, July 12, 2003 12:43 AM
Subject: Re: Kernel compile error with make-kpkg
> On Fri, 11 Jul 2003 23:50:06 +0200
> "Esben Laursen" <[EMAIL PROTECTED]> wrote:
> >
> > When I try to compile a 2.4.21 kernel with Debians make-kpkg tool, I get
> > this error no matter what I try!! The command im useing is: make-kpkg
> > --append_to_version -test kernel-image
> >
> > I think it's when the package is being build there is an error, or am I
> > wrong?
> >
> > Here is the error I get:
> >
> > cd /usr/src/linux/debian/tmp-image/lib/modules/2.4.21-test; \
> > mkdir -p pcmcia; \
> > find kernel -path '*/pcmcia/*' -name '*.o' | xargs -i -r ln -sf ../{}
> > pcmcia if [ -r System.map ]; then /sbin/depmod -ae -F System.map -b
> > /usr/src/linux/debian/tmp-image -r 2.4.21-test; fi depmod: ***
> > Unresolved symbols in
> > /usr/src/linux/debian/tmp-image/lib/modules/2.4.21-test/kernel/drivers/
> > media/radio/miropcm20.o depmod: aci_rw_cmd_Rsmp_cc7c4cd8
> > depmod: aci_port_Rsmp_0d82adb6
> > depmod: aci_version_Rsmp_93350c87
> > depmod: *** Unresolved symbols in
> > /usr/src/linux/debian/tmp-image/lib/modules/2.4.21-test/kernel/drivers/
> > net/wan/comx.o depmod: proc_get_inode
> > make[2]: *** [_modinst_post] Error 1
> > make[2]: Leaving directory `/usr/src/linux-2.4.21'
> > make[1]: *** [real_stamp_image] Error 2
> > make[1]: Leaving directory `/usr/src/linux-2.4.21'
> >
> > Can anyone help me with what's wrong??
>
> You need to provide more information than you've given. Specifically,
> what version of gcc did you use (the output of linux/scripts/ver_linux
> would provide lots of info, but the gcc version you're using is probably
> enough). Also, and especially, what architecture are you on, and did
> you specify that architecture in your kernel config?
>
> -c
>
> --
> Chris Metzler [EMAIL PROTECTED]
Here is the output from a gcc -v
Reading specs from /usr/lib/gcc-lib/i386-linux/2.95.4/specs
gcc version 2.95.4 20011002 (Debian prerelease)
Im trying to compile a kernel with support for the PII CPU, and my kernel now is a
standart Debain kernel-image-2.4.18-bf2.4 with the 386 architecture.
Im also importing the /boot/config-2.4.18-bf2.4 from the "make menuconfig" so that I
get all the things I need and only have to change a few things like the architecture.
I've attached the /usr/src/linux/scripts/var_linux file so you can see it.
Esben
ver_linux
Description: Binary data
Re: Kernel compile error with make-kpkg
On Fri, 11 Jul 2003 23:50:06 +0200
"Esben Laursen" <[EMAIL PROTECTED]> wrote:
>
> When I try to compile a 2.4.21 kernel with Debians make-kpkg tool, I get
> this error no matter what I try!! The command im useing is: make-kpkg
> --append_to_version -test kernel-image
>
> I think it's when the package is being build there is an error, or am I
> wrong?
>
> Here is the error I get:
>
> cd /usr/src/linux/debian/tmp-image/lib/modules/2.4.21-test; \
> mkdir -p pcmcia; \
> find kernel -path '*/pcmcia/*' -name '*.o' | xargs -i -r ln -sf ../{}
> pcmcia if [ -r System.map ]; then /sbin/depmod -ae -F System.map -b
> /usr/src/linux/debian/tmp-image -r 2.4.21-test; fi depmod: ***
> Unresolved symbols in
> /usr/src/linux/debian/tmp-image/lib/modules/2.4.21-test/kernel/drivers/
> media/radio/miropcm20.o depmod: aci_rw_cmd_Rsmp_cc7c4cd8
> depmod: aci_port_Rsmp_0d82adb6
> depmod: aci_version_Rsmp_93350c87
> depmod: *** Unresolved symbols in
> /usr/src/linux/debian/tmp-image/lib/modules/2.4.21-test/kernel/drivers/
> net/wan/comx.o depmod: proc_get_inode
> make[2]: *** [_modinst_post] Error 1
> make[2]: Leaving directory `/usr/src/linux-2.4.21'
> make[1]: *** [real_stamp_image] Error 2
> make[1]: Leaving directory `/usr/src/linux-2.4.21'
>
> Can anyone help me with what's wrong??
You need to provide more information than you've given. Specifically,
what version of gcc did you use (the output of linux/scripts/ver_linux
would provide lots of info, but the gcc version you're using is probably
enough). Also, and especially, what architecture are you on, and did
you specify that architecture in your kernel config?
-c
--
Chris Metzler [EMAIL PROTECTED]
(remove "snip-me." to email)
"As a child I understood how to give; I have forgotten this grace since I
have become civilized." - Chief Luther Standing Bear
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[SOLVED]Re: Kernel - compile error
I was trying to compile a 2.4.18 kernel source that
comes with the cds of DEBIAN .. so, I wasn't get to
compile it without SMP support (since this can't be
enabled to insert some modules, like ptserial.o to
makes my HSPPCtel modem works..).
So, last night I got the 2.4.18 kernel source from
debian.org/packages, and I got compile it normally.
So the problem was the version of the 2.4.18 kernel
source.
I take a week trying to discover this problem ..
Thanks very much to all that spend some time help
me.
Rodrigo F Baroni
Computer Science Grad Student
--- Rob Weir <[EMAIL PROTECTED]> escreveu: > [I'm
on-list, obviously, so please don't CC me.
> Also, please let your
> editor do some sort of sensible wrapping (say at 72
> columns), since your
> messages just look horrific.]
>
> On Wed, Jan 08, 2003 at 01:39:38PM -0300, Rodrigo F.
> Baroni wrote:
> > --- Rob Weir <[EMAIL PROTECTED]> escreveu: > On
> Sun,
> > Jan 05, 2003 at 03:36:36PM -0300, Rodrigo F.
> > > Baroni wrote:
> > > > Hello all,
> > > >
> > > > Kernel 2.4.18 in a 233Mhz PC Pentium
> 233Mhz,
> > > > LMR591 mother board (everything on-board) -
> after
> > > > compile the kernel (#make bzImage) the follow
> > > error
> > > > appear:
> > > >
> > > >
> > > > "make: warning: Clock skew detected. Your
> > > build
> > > > may be incomplete"
> > > >
> > > >
> > > > I got to boot with it, but I don't know
> if
> > > it
> > > > there isn't some problem... since it will be a
> > > node in
> > > > a cluster..
> > > > Does anybody knows what's going on ?
> > >
> > > make adds some smarts to software compilation:
> it
> > > only rebuilds things
> > > whose dependencies have changed. For example,
> if
> > > example.o is built
> > > from example.c and includes header.h, then
> example.o
> > > will only be
> > > rebuilt if example.c or header.h have changed.
> It
> > > does this by checking
> > > the modification time of files. make, of
> course,
> > > recurses up the
> > > dependency tree. It looks like make is getting
> > > confused about when a
> > > file was modified. Are you running ntpdate or
> > > having clock problems?
> > >
> >
> > No. Yet, the same message ("Clock skew detected.
> > Your build may be incomplete") had happened in
> another
> > machine (PentiumIII 550Mhz, Asus p299
> motherboard).
> > Maybe be some problem of the 2.4.18 kernel, I
> think...
>
> I doubt it, since millions of people are using it
> successfully
>
> > I had got another problem, but this don´t let
> the
> > compile get finish, saying about support to smp,
> but
> > since are machines mono-processor, I have disabled
> > support to it (SMP) - what give the follw error
> when
> > %make bzImage :
> >
> >nro_smp_processor not defined
> >
> >
> > If I enable the support to SMP, the compilation
> of
> > kernel goes normally, but some drivers don´t work
> with
> > it.
> >This have been a problem for some time to me...
>
> Have you tried backing up .config and running 'make
> mrproper'?
>
> ATTACHMENT part 2 application/pgp-signature
___
Busca Yahoo!
O melhor lugar para encontrar tudo o que você procura na Internet
http://br.busca.yahoo.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kernel - compile error
[I'm on-list, obviously, so please don't CC me. Also, please let your
editor do some sort of sensible wrapping (say at 72 columns), since your
messages just look horrific.]
On Wed, Jan 08, 2003 at 01:39:38PM -0300, Rodrigo F. Baroni wrote:
> --- Rob Weir <[EMAIL PROTECTED]> escreveu: > On Sun,
> Jan 05, 2003 at 03:36:36PM -0300, Rodrigo F.
> > Baroni wrote:
> > > Hello all,
> > >
> > > Kernel 2.4.18 in a 233Mhz PC Pentium 233Mhz,
> > > LMR591 mother board (everything on-board) - after
> > > compile the kernel (#make bzImage) the follow
> > error
> > > appear:
> > >
> > >
> > > "make: warning: Clock skew detected. Your
> > build
> > > may be incomplete"
> > >
> > >
> > > I got to boot with it, but I don't know if
> > it
> > > there isn't some problem... since it will be a
> > node in
> > > a cluster..
> > > Does anybody knows what's going on ?
> >
> > make adds some smarts to software compilation: it
> > only rebuilds things
> > whose dependencies have changed. For example, if
> > example.o is built
> > from example.c and includes header.h, then example.o
> > will only be
> > rebuilt if example.c or header.h have changed. It
> > does this by checking
> > the modification time of files. make, of course,
> > recurses up the
> > dependency tree. It looks like make is getting
> > confused about when a
> > file was modified. Are you running ntpdate or
> > having clock problems?
> >
>
> No. Yet, the same message ("Clock skew detected.
> Your build may be incomplete") had happened in another
> machine (PentiumIII 550Mhz, Asus p299 motherboard).
> Maybe be some problem of the 2.4.18 kernel, I think...
I doubt it, since millions of people are using it successfully
> I had got another problem, but this don´t let the
> compile get finish, saying about support to smp, but
> since are machines mono-processor, I have disabled
> support to it (SMP) - what give the follw error when
> %make bzImage :
>
>nro_smp_processor not defined
>
>
> If I enable the support to SMP, the compilation of
> kernel goes normally, but some drivers don´t work with
> it.
>This have been a problem for some time to me...
Have you tried backing up .config and running 'make mrproper'?
msg23144/pgp0.pgp
Description: PGP signature
Re: Kernel - compile error
--- Rob Weir <[EMAIL PROTECTED]> escreveu: > On Sun,
Jan 05, 2003 at 03:36:36PM -0300, Rodrigo F.
> Baroni wrote:
> > Hello all,
> >
> > Kernel 2.4.18 in a 233Mhz PC Pentium 233Mhz,
> > LMR591 mother board (everything on-board) - after
> > compile the kernel (#make bzImage) the follow
> error
> > appear:
> >
> >
> > "make: warning: Clock skew detected. Your
> build
> > may be incomplete"
> >
> >
> > I got to boot with it, but I don't know if
> it
> > there isn't some problem... since it will be a
> node in
> > a cluster..
> > Does anybody knows what's going on ?
>
> make adds some smarts to software compilation: it
> only rebuilds things
> whose dependencies have changed. For example, if
> example.o is built
> from example.c and includes header.h, then example.o
> will only be
> rebuilt if example.c or header.h have changed. It
> does this by checking
> the modification time of files. make, of course,
> recurses up the
> dependency tree. It looks like make is getting
> confused about when a
> file was modified. Are you running ntpdate or
> having clock problems?
>
No. Yet, the same message ("Clock skew detected.
Your build may be incomplete") had happened in another
machine (PentiumIII 550Mhz, Asus p299 motherboard).
Maybe be some problem of the 2.4.18 kernel, I think...
I had got another problem, but this don´t let the
compile get finish, saying about support to smp, but
since are machines mono-processor, I have disabled
support to it (SMP) - what give the follw error when
%make bzImage :
nro_smp_processor not defined
If I enable the support to SMP, the compilation of
kernel goes normally, but some drivers don´t work with
it.
This have been a problem for some time to me...
Rodrigo
___
Busca Yahoo!
O melhor lugar para encontrar tudo o que você procura na Internet
http://br.busca.yahoo.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kernel - compile error
On Sun, Jan 05, 2003 at 03:36:36PM -0300, Rodrigo F. Baroni wrote: > Hello all, > > Kernel 2.4.18 in a 233Mhz PC Pentium 233Mhz, > LMR591 mother board (everything on-board) - after > compile the kernel (#make bzImage) the follow error > appear: > > > "make: warning: Clock skew detected. Your build > may be incomplete" > > > I got to boot with it, but I don't know if it > there isn't some problem... since it will be a node in > a cluster.. > Does anybody knows what's going on ? make adds some smarts to software compilation: it only rebuilds things whose dependencies have changed. For example, if example.o is built from example.c and includes header.h, then example.o will only be rebuilt if example.c or header.h have changed. It does this by checking the modification time of files. make, of course, recurses up the dependency tree. It looks like make is getting confused about when a file was modified. Are you running ntpdate or having clock problems? -rob msg23007/pgp0.pgp Description: PGP signature
Re: kernel compile error
Rodrigo F. Baroni said: > /usr/src/kernel-source-2.4.18/include/linux/kernel_stat.h:48: > `smp_num_cpus' undeclared (first use in this function) A guess for a workaround would be to check to see if SMP is enabled in the config, if it is, turn it off. If it is not, turn it on, and see if that helps. nate -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kernel compile error?
On Sun, Jul 29, 2001 at 08:53:44AM -0800, Christopher S. Swingley wrote: [snip] > It looks like the problem is the 'ld' step, where it uses '-oformat binary' > instead of '--oformat binary'. I edited the Makefile in > /usr/src/linux/arch/i386/boot, and it worked. Is this a bug with the > 2.4.1 kernel Makefile, or has 'ld' changed very recently in it's behavior? ld changed about a month or so ago. Apparently to avoid confusion with the -o flag. -- Eric G. Miller
Re: kernel compile error
Eric R Cheney wrote: > > Just want to follow-up and say thanks. The follow up because there were a > couple of hypotheses about what could go wrong. Jeremy Nickurak's > hypothesis did the trickso people compiling kernel's under unstable > take note. Maybe we would if the replies would've been sent to the list.Since they weren't I guess we're just happy for you and take note that you did solve your problem whatever that might've been.:-) Anyway,if you had the -oformat problem it was answered last week or so. Gretings
Re: kernel compile error
Just want to follow-up and say thanks. The follow up because there were a couple of hypotheses about what could go wrong. Jeremy Nickurak's hypothesis did the trickso people compiling kernel's under unstable take note. Thanks Jeremy for your help...I would never have guessed...thanks -Eric On Sun, 11 Mar 2001, Jeremy Nickurak wrote: > In linux/arch/i386/boot/Makefile, all the "-oformat" occurances need to be > changed to "--oformat". > > On Sun, 11 Mar 2001 19:11:18 Eric R Cheney wrote: > > OK, then when I go to copy the bzImage file to /boot/, it's not there. In > > fact, I the reran bzImage step and in fact it cuts out with an error > > messageI doesn't compile the source codeAnybody know what I'm > > doing > > wrong? I am migrating from RedHat and maybe I'm assuming things I > > shouldn't beAny clues? > > -- > Jeremy Nickurak -= [EMAIL PROTECTED] =- > "You know, Hobbes, some days even my lucky rocketship underpants don't > help." > -- Calvin > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- Eric Cheney [EMAIL PROTECTED]
Re: kernel compile error
[EMAIL PROTECTED] wrote: > > > > OK, then when I go to copy the bzImage file to /boot/, it's not there. In > > fact, I the reran bzImage step and in fact it cuts out with an error > > messageI doesn't compile the source codeAnybody know what I'm doing > > wrong? I am migrating from RedHat and maybe I'm assuming things I > > shouldn't beAny clues? what are the errors? erik
Re: kernel compile error
> OK, then when I go to copy the bzImage file to /boot/, it's not there. In > fact, I the reran bzImage step and in fact it cuts out with an error > messageI doesn't compile the source codeAnybody know what I'm doing > wrong? I am migrating from RedHat and maybe I'm assuming things I > shouldn't beAny clues? Could be something to do with your assembler -- I seem to recall having some similar problem. Make sure you have all of the programs listed in /usr/src/linux/Documentation/Changes. Then recompile the kernel with make mrproper make config make dep bzImage modules modules_install &> make.log and if it still breaks down, post the relevant section of make.log. Cheers Tiarnan
Re: kernel compile error
In linux/arch/i386/boot/Makefile, all the "-oformat" occurances need to be changed to "--oformat". On Sun, 11 Mar 2001 19:11:18 Eric R Cheney wrote: > OK, then when I go to copy the bzImage file to /boot/, it's not there. In > fact, I the reran bzImage step and in fact it cuts out with an error > messageI doesn't compile the source codeAnybody know what I'm > doing > wrong? I am migrating from RedHat and maybe I'm assuming things I > shouldn't beAny clues? -- Jeremy Nickurak -= [EMAIL PROTECTED] =- "You know, Hobbes, some days even my lucky rocketship underpants don't help." -- Calvin
Re: Kernel compile error
Quoting Blair Haukedal ([EMAIL PROTECTED]): > I cannot compile the Debian 2.2.17 kernel. I get the following: > > peewee:kernel-source-2.2.17:(root)73$ make config > rm -f include/asm > ( cd > include ; ln -sf asm-i386 asm) > /bin/sh: cd: include: No such file or > directory > mkdir: cannot create directory `include/linux/modules': No such > file or directory > make: *** [symlinks] Error 255 > > What am I missing - please help. You appear to be missing much of the kernel source. If you cd .../kernel-source-2.2.17 as you did above, and then ls include you should see asmasm-generic asm-mips asm-sparcmath-emu video asm-alpha asm-i386 asm-ppc asm-sparc64 net asm-armasm-m68k asm-s390 linuxscsi though it doesn't matter if there's no "asm" as the first entry (that's what ln -sf creates). Cheers, -- Email: [EMAIL PROTECTED] Tel: +44 1908 653 739 Fax: +44 1908 655 151 Snail: David Wright, Earth Science Dept., Milton Keynes, England, MK7 6AA Disclaimer: These addresses are only for reaching me, and do not signify official stationery. Views expressed here are either my own or plagiarised.
Re: Kernel compile error
Looks like you might need the bin86 package. (The assembler for x86 machines...) Just a guess... I'm not a C guru by a long shot. On Mon, Sep 04, 2000 at 09:53:17PM -0600, Blair Haukedal wrote: > I cannot compile the Debian 2.2.17 kernel. I get the following: > > peewee:kernel-source-2.2.17:(root)73$ make config > rm -f include/asm > ( cd > include ; ln -sf asm-i386 asm) > /bin/sh: cd: include: No such file or > directory > mkdir: cannot create directory `include/linux/modules': No such > file or directory > make: *** [symlinks] Error 255 > > What am I missing - please help. > >...blh... > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null > -- Nate Duehr <[EMAIL PROTECTED]> GPG Key fingerprint = DCAF 2B9D CC9B 96FA 7A6D AAF4 2D61 77C5 7ECE C1D2 Public Key available upon request, or at wwwkeys.pgp.net and others. pgpR9zBYAAUpG.pgp Description: PGP signature
Re: Kernel compile error
there is more to this error then just the below, please include the full output, include the previous, 35 lines if possible. chances are it is something you enabled but is broken, to find out what it is i need the full output. also what version of gcc are you using ? to output make to a logfile: make bzImage >&kernel.log nate JP Sartre wrote: > > Hi guys.. I got a strange error when attempting to recompile my kernel today. > I was able to compile it yesterday, so I'm not sure why it is choking today. > Anyhow, here's the output: > > /usr/src/kernel-source-2.2.17/include/linux/kernel_stat.h:47: for each > function it appears in.) > make[2]: *** [ksyms.o] Error 1 > make[2]: Leaving directory `/usr/src/kernel-source-2.2.17/kernel' > make[1]: *** [first_rule] Error 2 > make[1]: Leaving directory `/usr/src/kernel-source-2.2.17/kernel' > make: *** [_dir_kernel] Error 2 > > Any ideas what I'm missing? Could it be something I selected in the config? > Thanks for any help you can provide. > > JP > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null -- ::: ICQ: 75132336 http://www.aphroland.org/ http://www.linuxpowered.net/ [EMAIL PROTECTED]
Re: Kernel Compile error: What am I missing?
Russel wrote: >Oops...I've got either a 2.2.10, 2.2.12, and 2.2.14. Tried em all. > >I've got the binutils and gcc versions required in Documentation/Changes >( I even checked using the commands listed in that file) > >If the file builds just fine on your computer...has the file changed >between kernel versions? Has it changed at all in years? Would something >else have changed? Naturally, I must be missing something. I just wish I >knew what. ugh. I think this might be your problem: --- kernel-source-2.2.10/arch/m68k/fpsp040.orig/bindec.SFri Apr 26 05:12:35 1996 +++ kernel-source-2.2.10/arch/m68k/fpsp040/bindec.S Tue Oct 12 17:36:55 1999 @@ -484,7 +484,7 @@ fmovex (%a0),%fp0 |load X from memory fabsx %fp0|use abs(X) tstw%d5 |LAMBDA is in lower word of d5 - bnessc_mul |if neg (LAMBDA = 1), scale by mul + jne sc_mul |if neg (LAMBDA = 1), scale by mul fdivx %fp1,%fp0 |calculate X / SCALE -> Y to fp0 brasA10_st |branch to A10 The line # matches the one in your error message: >>Assembler Messages: >>Bindec.S :487 >>/usr/src/linux/arch/m68k/fpsp040 >>[Bindec.o] error 1 >>value of -512 too large for field of 1 bytes at 511 Judging from the error message I'd say that the source has changed to the extent that sc_mul is now out of reach of a short (8 bit) branch from that point and now requires a (32? bit) jump (sorry, my m68k assembler is a bit rusty these days). That fragment comes from a patch named binutils295-fpsp040-2.2.10.diff.gz included in kernel-patch-2.2.10-m68k_2.2.10-6.deb. I presume then that you are rolling your own kernel from the upstream sources. Looks to me like you might have better luck with the Debian kernel-source* and kernel-patch* packages. Frank
Re: Kernel Compile error: What am I missing?
Oops...I've got either a 2.2.10, 2.2.12, and 2.2.14. Tried em all. I've got the binutils and gcc versions required in Documentation/Changes ( I even checked using the commands listed in that file) If the file builds just fine on your computer...has the file changed between kernel versions? Has it changed at all in years? Would something else have changed? Naturally, I must be missing something. I just wish I knew what. ugh. Is there a script that can tell what's there and what isn't and report back if anything is missing? Thanks! Russell Russell wrote: >Here's the message I get: > >Assembler Messages: >Bindec.S :487 >/usr/src/linux/arch/m68k/fpsp040 >[Bindec.o] error 1 >value of -512 too large for field of 1 bytes at 511 > >I asked the people on the m68k list, and they didn't know. I am sure I'm >missing some vital library or other piece of code in the compile process, I >just can't figure out what it could be. > >Can anyone help? Sorry, that file builds just fine on my Amiga, kernel 2.0.36. What kernel version are you building, with what gcc and binutils versions? Frank
Re: Kernel Compile error: What am I missing?
Russell wrote: >Here's the message I get: > >Assembler Messages: >Bindec.S :487 >/usr/src/linux/arch/m68k/fpsp040 >[Bindec.o] error 1 >value of -512 too large for field of 1 bytes at 511 > >I asked the people on the m68k list, and they didn't know. I am sure I'm >missing some vital library or other piece of code in the compile process, I >just can't figure out what it could be. > >Can anyone help? Sorry, that file builds just fine on my Amiga, kernel 2.0.36. What kernel version are you building, with what gcc and binutils versions? Frank
Re: kernel compile error
On Fri, 10 Sep 1999, Paul wrote: Have you installed libc6-dev and libncurses4-dev (this one only for make menuconfig) ? bye! > (Not sure if this made it the first time) > Back Again! >2 distinct problems this time, firstly I seem to have been > taken off the list (so please copy to this address). I suppose I`ll have > to resubscribe. > Secondly I`m trying to compile network support into the kernel, (I`ve > got AT-1700 cards in both machines and want to connect the 2 together > basically) but after I "make bzdisk" to be safe I get the following > message at the end of the process. Where am I going wrong? > Also any tips for an idiots guide to networking would be appreciated as > I`m finding it very hard going even knowing where to begin. > > > rm -f $tmppiggy $tmppiggy.gz $tmppiggy.lnk > gcc -D__KERNEL__ -I/usr/src/kernel-source-2.0.36/include -traditional -c > head.S > gcc -D__KERNEL__ -I/usr/src/kernel-source-2.0.36/include -O2 > -DSTDC_HEADERS -c misc.c -o misc.o > ld -m elf_i386 -Ttext 0x10 -e startup_32 -o bvmlinux head.o misc.o > piggy.o > make[2]: Leaving directory > `/usr/src/kernel-source-2.0.36/arch/i386/boot/compressed' > gcc -I/usr/src/kernel-source-2.0.36/include -O2 -fomit-frame-pointer > -D__BFD__ -D__BIG_KERNEL__ -o tools/bbuild tools/build.c > -I/usr/src/kernel-source-2.0.36/include > tools/build.c:25: stdio.h: No such file or directory > tools/build.c:26: string.h: No such file or directory > tools/build.c:27: stdlib.h: No such file or directory > tools/build.c:28: sys/types.h: No such file or directory > tools/build.c:29: sys/stat.h: No such file or directory > tools/build.c:30: sys/sysmacros.h: No such file or directory > tools/build.c:31: unistd.h: No such file or directory > tools/build.c:32: fcntl.h: No such file or directory > tools/build.c:35: errno.h: No such file or directory > make[1]: *** [tools/bbuild] Error 1 > make[1]: Leaving directory > `/usr/src/kernel-source-2.0.36/arch/i386/boot' > make: *** [bzdisk] Error 2 > > Thanks > > Paul Walton > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null > > --- ** Powered by Debian/GNU Linux ** Linux User 140860 Machine 61143 Juli-Manel Merino Vidal -->> [EMAIL PROTECTED] - http://jmmv.cjb.net
Re: kernel compile error-help
try the package : kernel-package it makes all automaticaly. else : perhaps you need the package bin86
RE: kernel compile error-help
Hi, The command as86 is not found so the directory of as86 is not in your PATH (I don't think so) or (probably) the package bin86 is not installed on your system Alexandre Devaure -- De :mel[SMTP:[EMAIL PROTECTED] Date d'envoi : mercredi 5 mai 1999 12:39 A : debian-user@lists.debian.org Objet : kernel compile error-help hi, Trying to compile sound support into a kernel (2.0.36), i am getting the following error messages: after `make zImage` make[1] as86 command not found make [1] ***[bootsect.o] Error 127 make[1] Leaving directory `/usr/src/linux/arc/i386/boot` make[1] ***[zImage] error 2 How can this be corrected ..what is wrong? Running slink V2.1 on a Thoshiba Laptop 8000. best-mel -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
Re: kernel compile error-help
On Wed, May 05, 1999 at 10:39:44AM +, mel wrote: > hi, > Trying to compile sound support into a kernel (2.0.36), i am getting the > following error messages: > after `make zImage` > make[1] as86 command not found > make [1] ***[bootsect.o] Error 127 > make[1] Leaving directory `/usr/src/linux/arc/i386/boot` > make[1] ***[zImage] error 2 > How can this be corrected ..what is wrong? > Running slink V2.1 on a Thoshiba Laptop 8000. > best-mel bin86 - 16-bit assembler and loader This is the as86 and ld86 distribution written by Bruce Evans. It's a complete 8086 assembler and loader which can make 32-bit code for the 386+ processors (under Linux it's used only to create the 16-bit bootsector and setup binaries). -- Ian Peters "I never let schooling interfere with my education." [EMAIL PROTECTED] -- Mark Twain
Re: Kernel Compile Error
Gregory T. Norris wrote: > > Try running "dpkg -l|grep gcc", and make sure that you have gcc installed > instead of/in addition to egcc. If memory serves, there are problems > related to compiling the 2.0.x kernels with egcc, and so they have > #error directives set up in order to disallow it. > > After installing gcc (assuming that it's not installed at all), you may > need to do something like "export CC=/usr/bin/gcc" prior to building > the kernel. I have the egcs version installed. However, it is from potato. When I try to get the old gcc using apt-get it tells me that I already have the most current version installed. I'v given up on 2.0.36, and have moved on to 2.2.1 which is giving me a whole new set of difficulties :@ Thanks for posting, and I am sure that I'll be posting until I figure this thing out. I'm off to the archive now. Thanks again -- __ _ Mark Wagnon Debian GNU/ -o) / / (_)__ __ __ Chula Vista, CA /\\/ /__/ / _ \/ // /\ \/ / mailto:[EMAIL PROTECTED] _\_v/_/_//_/\_,_/ /_/\_\
Re: Kernel Compile Error
On Sat, Mar 27, 1999 at 08:08:44PM -0800, Mark Wagnon wrote: > Hi all- > > I was trying to compile the 2.0.36 kernel on my slink system to include > support for sound. > > I went through the make xconfig deal and typed make dep and make clean > without incident. However when I tried to make zImage I got the > following output: > > [error-text snipped] Try running "dpkg -l|grep gcc", and make sure that you have gcc installed instead of/in addition to egcc. If memory serves, there are problems related to compiling the 2.0.x kernels with egcc, and so they have #error directives set up in order to disallow it. After installing gcc (assuming that it's not installed at all), you may need to do something like "export CC=/usr/bin/gcc" prior to building the kernel.
Re: kernel compile error
On Mon, 30 Jun 1997 23:27:30 EDT dpk ([EMAIL PROTECTED]) wrote: [stuff about SIGSEGV w/compiling kernel] > I have gotten this once before. I just did a 'make clean; make dep; make > zImage' and it compiled okay... as to why this happens I don't know. These kinds of unreproducible errors when compiling the kernel (or anything) are likely due to hardware problems: faulty cache or memory, etc... There are a number of faqs available describing this problem. Gcc is an excelent memory tester :-) Phil. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: kernel compile error
I have gotten this once before. I just did a 'make clean; make dep; make zImage' and it compiled okay... as to why this happens I don't know. Dennis On Mon, 30 Jun 1997, Kevin J Poorman wrote: > Date: Mon, 30 Jun 1997 22:09:44 CDT > From: Kevin J Poorman <[EMAIL PROTECTED]> > To: debian-user@lists.debian.org > Cc: [EMAIL PROTECTED], [EMAIL PROTECTED] > Subject: kernel compile error > Resent-Date: 1 Jul 1997 04:09:00 - > Resent-From: debian-user@lists.debian.org > Resent-cc: recipient.list.not.shown:;@lists.debian.org > > Hi. > I just upgraded to Debian 1.3 (which went with out a hitch) > > but now I want to compile my kernel so I have Sound Suport and other > things > > I went and grabed the source and tryed to compile it ... and this is what > I got > > > Begin Screen Dump. > gcc -D__KERNEL__ -I/usr/src/kernel-source-2.0.30/include -Wall > -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strength-reduce -pipe > -m486 -DCPU=486 -c -o pty.o pty.c > gcc -D__KERNEL__ -I/usr/src/kernel-source-2.0.30/include -Wall > -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strength-reduce -pipe > -m486 -DCPU=486 -c -o vt.o vt.c > gcc -D__KERNEL__ -I/usr/src/kernel-source-2.0.30/include -Wall > -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strength-reduce -pipe > -m486 -DCPU=486 -c -o mem.o mem.c > gcc -D__KERNEL__ -I/usr/src/kernel-source-2.0.30/include -Wall > -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strength-reduce -pipe > -m486 -DCPU=486 -c -o vc_screen.o vc_screen.c > gcc -D__KERNEL__ -I/usr/src/kernel-source-2.0.30/include -Wall > -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strength-reduce -pipe > -m486 -DCPU=486 -c -o random.o random.c > cpp: output pipe has been closed > gcc: Internal compiler error: program cc1 got fatal signal 11 > make[3]: *** [random.o] Error 1 > make[3]: Leaving directory `/usr/src/kernel-source-2.0.30/drivers/char' > make[2]: *** [first_rule] Error 2 > make[2]: Leaving directory `/usr/src/kernel-source-2.0.30/drivers/char' > make[1]: *** [sub_dirs] Error 2 > make[1]: Leaving directory `/usr/src/kernel-source-2.0.30/drivers' > make: *** [linuxsubdirs] Error 2 > > End screen dump > > any help twoards fixing this problem is greatly appreiceated > > > -Kevin > > > -- > TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to > [EMAIL PROTECTED] . > Trouble? e-mail to [EMAIL PROTECTED] . > > + dpk <[EMAIL PROTECTED]> + work : 517.353.8892 + + Systems Undergrad + pager: 517.222.5875 + + Division of Engineering Computing Services + + -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
