V5.0 /scripts/link-vmlinux.sh fails

SliTaz Forum » English Support » Live and installation

V5.0 /scripts/link-vmlinux.sh fails

(10 posts) (3 voices)

Started 3 years ago by dkuchay
Latest reply from dkuchay
This topic is resolved

Tags:

No tags yet.

dkuchay

offline
Member

Think I have an issue to report. I have V5.0 in a vdi and am trying to build kernel for odd hardware. Failed two times at the same spot so I downloaded new source and watched it patch. Pushed through 4 aufs files that were not there.

I only flipped one option in menuconfig: /drivers/input/misc/atlas_btns

Left all else as stock options. Most of it builds but near the end where you start to watch for kernel size and just before modules start to buildl I get this error:

/scripts/link-vmlinux.sh
lne 114 Invalid signal specification
Make *** [Makefile:1156 vmlinuxclean]
Error 1

Before building I installed slitaz-toolchain. On my first build I got only a few lines in when I was told that BC was missing from system. I did a tazpkg get-install bc and saw readlink also come in.

Is there a step or package I am missing?

Posted 3 years ago #
mojo

offline
Key Master

Verify all BUILD_DEPENDS from the linux/receipt are installed:
http://hg.slitaz.org/wok/file/c8740863dd45/linux/receipt#l15
bc is included and would have been auto-installed if cook linux command is used to build linux.

The error may indicate bash in not installed.
If your not using cookutils to build packages you should install packages listed in cook.conf SETUP_PKGS variable
http://hg.slitaz.org/cookutils/file/e69f1fca1e39/cook.conf#l39

Posted 3 years ago #
dkuchay

offline
Member

Thank you. didnt realize I was on old method. After installing slitaz-toolchain I did choose bash.

cook setup

cook linux

failed with missing aufs3 patch directories in /home/slitaz. Is this my fault that the directories are not there?
Also how can I insert a config file for a particular kernel build? Will —interactive do that once patch dirs are in place?

Posted 3 years ago #
dkuchay

offline
Member

Went back in to this and opened kernel receipt grabbed all dependencies. No ulibc-crosscompiler though. Not in repo.

I did a cook setup —wok

cook linux
cook linux-3.16.55
cook new linux. — makes blank receipt file
cook linux -gs

All these commands either did nothing or look to bring in new kernel and source and I am not sure if —interactive will allow me to make menuconfig

Is there a way I can use the source already downloaded? Realizing new tools work better for large architectural feats how can one just add some drivers to a kernel and move on quicky? Even on V5 when the kernel source downloads if says right there to use make tazpkg if you want to make a installable package. Including screen shot of what fails this time and at the same spot. Documentation is hard to follow. Do we use conspy for this? When should and should I use or not use conspy?

Posted 3 years ago #
Bellard

offline
Key Master

# tazpkg -gi mercurial
# mkdir /home/slitaz && cd /home/slitaz
# hg clone http://hg.slitaz.org/wok
<modify linux/receipt and linux/stuff/* as you want>
# cook linux

Posted 3 years ago #
dkuchay

offline
Member

Thank you. This will keep me busy for a while.

Posted 3 years ago #
dkuchay

offline
Member

A few steps in I get told that error on dep 13.

Cloned wok. Looked over linux-sourcereceipt. Wanted to test a build to make sure I had access to menuconfig (default kernels will not work)

cooker pkg linux-source —interactive

was issued and it exited chroot a moment later on dep 13 error. Looking over the deps the only one that I can not find is busybox-boot. There were not even 13 deps on the kernel. Just checked. Busybox-boot is the tenth and last dep listed on the receipt. What is dep 13?

Will I be able to use a custom config file or get in to menuconfig (interactively) using this method? Although my error is not the exact same as the thread this was started on but I still fail on same spot in make tazpkg within kernel source directory

Also if I want v4 iso’s to work on my hardware I have been told that I may need to build old syslinux-3.82 on v4. This was a package in v3. I use tazlito and just make old syslinux appear in packages directory. Yet have I seen x11 work on these iso’s. No errors either.

If I want to get old syslinux in to wok and then make an iso what is the workflow? I cant seem to find old syslinux-3.82 in hg.... Where is it? I went to web interface and browsed but can not find it. Do I need to download it from outside of Slitaz?

Whats the chance I can convert a package list from tazlto in to a build recipe for cooker?? I just need to include a custom kernel and use old syslinux to get my old hardware to boot your newer versions. 4 and 5. Two changes. Do I really need to manually fill out package receipts for all packages within a distribution for two changs?

Posted 3 years ago #
dkuchay

offline
Member
Ironically I got that image installed to hardware and openbox-session went missing out of /usr/bin. Got it replaced by bringing in tazpkg’s on usb sick. Once I got x to start no icons would show. Installed clearlooks, tango and hi-color and all registered invalid image format so I changed internal flash chips this morning. Now I have new interesting but relative.

I have the module I am trying to load showing in ls but modprobe refuses to load it saying it cant find it. So I run depmod and try again.
Attachments
00A22895-6771-404F-A3E9-969C650554B9..jpeg (93.7 KB, 376 downloads) 3 years old
Posted 3 years ago #
dkuchay

offline
Member

Think I am on to something.

When using tazlito there are packages that get included like linux-wireless.

Well..... I build my own kernel and if I change the cpu model then extra packages that Slitaz offers that import kernel modules like bluetooth or wireless or agp... these all I am guessing were built on a i386 specific kernel. I am using geode specific kernel so that things like geode companion chip become visible in kernel config. Many builds now I see module that will not load indicating improper format. I feel that these are from Sltaz packages that overlay kernel modules from a.different cpu model and this may be why I see error on invalid format. Why I can depmod and try to reload and it still fails.

Going to eliminate the linux-* packages from tazlito disto-packages.list and try again.

Posted 3 years ago #
dkuchay

offline
Member

Confirmed. If building ones own kernel eliminate any linux-* module or driver packages from your kernel when using tazlito.

Posted 3 years ago #

RSS feed for this topic

Reply

You must log in to post.

V5.0 /scripts/link-vmlinux.sh fails

Attachments

Reply