Tiny Core Extensions > TCE Q&A Forum
tinycore kernel installed ???
Jason W:
Sorry it has not worked. Might be missing dependencies.
Oh, and please remember to use English here as per the official rules, unless it is in the international section.
Thanks.
Jason W:
Oh, one important detail. Make sure to use these commands after unpacking the kernel source, naming it or linking it to /usr/src/linux, then doing "make menuconfig && make install" in /usr/src/linux:
--- Code: ---# rm /lib/modules/2.6.29.1-tinycore/build
# ln -s /usr/src/linux /lib/modules/2.6.29.1-tinycore/build
--- End code ---
Now it should work with "make all" in the dahdi directory.
Juanito:
--- Quote from: Jason W on November 25, 2009, 09:30:22 PM ---Oh, one important detail. Make sure to use these commands after unpacking the kernel source, naming it or linking it to /usr/src/linux...
--- End quote ---
I could easily be mistaken, but I thought the readme for 2.6.x advises against this. You might need to link /lib/build or similar to /usr/src/linux-2.6.x for compiling modules from extenal source though.
Jason W:
That is the same warning that was in linux-2.4.0, and it especially applied in the era when kernel headers used by glibc were symlinks in /usr/src/linux/include that pointed to /usr/linclude/linux, or vice versa. In other words, unpacking a different kernel into /usr/src/linux would overwrite the headers glibc was built against. Being that our kernel headers are real files in the base-dev extension, we don't have anything installed into /usr/src/linux. It is most likely harmless to have, especially as we don't update kernel verisons without a toolchain update.
Lunar linux and Gentoo I believe still uses the symlink to point to the currently used kernel source probably due to their package manager cd-ing into /usr/src/linux to do the kernel build, but Arch, Debian, CRUX, and others do not. It is a relic from having the kernel headers present there. The "build" symlink in /lib/modules to the current source is used by modern distros, as well as /usr/src/linux-VERSION.
WIth the proper BUILD symlink in /lib/modlues/`uname -r`, the symlink is most likely not needed for any builds of modern module packages. So I would personally agree that avoiding the /usr/src/linux symlink is good practice.
ftmouse:
Thanks again for "jason W" and you administrator for my help.
Finally yesterday, has passed the compilation, although still do not understand all the details, and causes of
My approach is to:
1 downloads
http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.29.1.tar.bz2
--- Code: ---mv linux-2.6.29.1.tar.bz2 /tmp
--- End code ---
2 unzip
--- Code: ---cd /tmp
tar xfvj linux-2.6.29.1.tar.bz2
--- End code ---
3 link to /usr/src/linux
--- Code: ---ln -s /tmp/linux-2.6.29.1 /usr/src/linux
--- End code ---
4 link to /lib/modules/2.6.29.1-tinycore/build
--- Code: ---ln -s /tmp/linux-2.6.29.1 /lib/modules/2.6.29.1-tinycore/build
--- End code ---
5 compilation "config"
--- Code: --- cd linux-2.6.29.1
make menuconfig
--- End code ---
Direct selection save
6 compilation kernel
--- Code: ---make
--- End code ---
Then you can successfully build a dahdi-linux-complete-2.2.0.2+2.2.0.tar.gz
The other: by tracking the discovery seems to tinycore_2.5.iso, as well as linux-headers-2.6.29.1-tinycore.tcz in the
Do not include ". Config" file. I do not know how to get, and perhaps this is the most fundamental solution.
ps:
My English is bad, maybe the word does not convey his ideas, very sorry.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version