How did you get to this conclusion? I have no such crashes, and cant reproduce it.
Waiting on input before closing this report. Please try to submit more useful bug reports.

I am running debian/wheezy. My live-build-config is in my /home/myname directory.
Running lb build gets an error:

~/root/syslinux/ldlinux.c32 missing

and then crashes. And yes, there is a symlink pointing to /usr/lib/syslinux/ldlinux.c32.
I checked, and thsi lib is really not existent. And it is NOT in debian/wheezy, but in syslinux from debian/experimental.

I added these files manually, so it did not crash again.

BTW: ALL documentations here and in the forum describe, how to build kali within a kali installation, buit there is none, which described it in a debian environment (except mine, of course).

There is another bugreport by me, there are some directories missing. The workaround for it is alos described in my documentation.

Thanks for reading and your attention! Besides: Kali is awesome!

Best regards

Hans

Thanks for the update.
Mentioning you are doing this outside of a Kali box makes more sense.
We have not tested this procedure fully, but will do so and add the documentation to our docs site.
Thanks!

You're welcome! The problem is mostly not a real kali-linux problem, it is a problem with the syslinux package version.

Important hint: If you get to test it on a debian system, do NOT mix with its repository! Otherwise you will get in another problem: libkrb53 breaks the build, as there is a dependency problem. I still found no solution for this. Maybe I should add a new bugreport related to this???

On which system did you do your builds? Ubuntu? (I guess, as Backtrack 5 was Ubuntu based).

You may check my documentation on www.ccpeine.de, there might be changes in the future. Still testing!

Happy hacking

Hans

Currently we do our builds on Debian Squeeze systems with a live-build taken from Debian Wheezy (3.0.1 currently). But doing builds in Debian Wheezy or Debian Unstable works as well currently (unstable is a moving target so it might not last long once wheezy is released).

We have not tested any Ubuntu systems.

Muts, where do you want to document this?

Yes, this might be explain things. At squeeze (when I remember correctly), the required files are in syslinux-package, but missing in wheezy. In debian/experimental they are again existent. Maybe kali could put those in its repository?

What about the other crash, caused by missing directories in ~/live-linux-config/binary/isolinux/ I described in my documentation? Shall I create a new bugreport? Could still not verify, if it is a bug in live-builder or related to the kali scripts. I will be happy to test and report, if someone could give me a clue.

Hans

Your analysis is wrong AFAIK. Please attach the full output of the failing build.

Those files that are not copied are not an issue at all since they are not needed by syslinux 4.x. Syslinux 5.x requires them and live-build should already be ready for syslinux 5.x.

But you certainly don't have to use syslinux 5.x to get Kali's live-build to work. On the contrary, I would advise you to stay away from the experimental repository unless you're sure of what you're doing.

As for the other issue that you documented, it would help if you told us where that documentation is and what the problem looks like... because right now I'm not aware of any problem. We're building Kali live images without problems on our sides.

In any case, please always attach the full logs of your failing builds. If you use our "build_all.sh --single" script then you have a .log file ready to give us. Otherwise just redirect standard output and standard error to a file and send us that file.

Ok guys,

here is my detailed build report. Sorry, it lasted some time, but each build lasts some hours. I added a clean binary.log for each run, beginning with first_run and so on.

At each run, I changed manually things, like manuylly copying files, creating directories or emtying some directories.

At anny error in the log, you might imagine what I did, so I think, detailed explanations are not necessary. Otherwise, just ask

I am running this on a fully upgraded debian/wheezy (64-bit), I added some tools like wicd-gtk The fully list kali.chroot.list I will send, too.

The first run is started with lb clean --purge , then did the following

lb config --architecture i386 --bootappend-live "boot=live config locales=de_DE.UTF-8 keyboard-layouts=de keyboard-variants=nodeadkeys"

after this I started with the first build (lb build)

At any crash I deleted the binary and created a new one. So I get a fresh binary.log for every build. Sorry, there are some German messages in it, but I guess, there will be someone in the team, who might translate them or just ask.

All files will all be attached.

Hope this explaines more than I can.

Best regards

Hans

P.S. Got an error during upload, please apologize, if this message is a double.

What version of live-build and syslinux are you using ?

dpkg -s live-build syslinux

As I already told: I am using debian-amd64/wheezy, up-to-date.

Version is then 3.0.1-1

Problem still exists! It is still not possible to build a kali system. Just checked with a fresh live-build and got into the same errors again, as already described.

Hans

Checked again. Still got into the same problem as already described. I believe, there are two problems.One is the missing libs of syslinux package. This could easily be solved.

On the other hand, there is also the problem with the missing directories. It looks like a problem with the HOOKS scripts. Is there a difference between the live-build package in kali and debian?

Please set this bugreport to a higher level, bcause at the moment building kali is very very hard to realize.

Best regards

Hans

I just looked at bit harder, your problem is that you actually have multiple kernels installed in binary/live/* and that live-build is not aware of it because there's only one kernel flavor that is set in the live-build configuration.

Something is pulling linux-image-3.2.0-4-686-pae in your image. And it's not any of the default Kali packages. It looks like one of the nvidia packages that you are installing...

If you drop nvidia-kernel-686-pae, you'll be fine. You don't need any precompiled nvidia modules. You can just install nvidia-kernel-dkms and you'll be fine.

Thanks for looking at this bug. I removed all nvidia-packages from kali.list.chroot. It seems, it build fine now. May I ask some questions not quite relating to this?

1. Do I need an entry "libgl1-nvidia-glx:i386" in kali.list.chroot to be able to use Nvidia gpu for password cracking?

2. For German environment is the following command correct?
   lb config --architecture i386 --bootappend-live "boot=live locales=de_DE.UTF-8 keyboard-layouts=de keyboard-variants=nodeadkeys"

or do I have to add

boot=live noconfig=sudo username=root hostname=kali ignore_uuid

addiotionally?

Thanks very much for the answer! Let the bug closed, please.

Cheers

Hans

For 1. I have no idea.

For 2. --bootappend-live is already used by Kali so you have to start with Kali's value and then add your own option. So “--bootappend-live "boot=live noconfig=sudo username=root hostname=kali <YOUR OPTIONS HERE>"”.

Found now the correct way, to build kali-image with working German environment and LXDE. I also added nvidia-packages to it, so that I can iuse GPU acceleration, when needed.

The correct command is (for other readers):

lb config –architecture i386 –bootappend-live “boot=live noconfig=sudo username=root hostname=kali ignore_uuid locales=de_DE.UTF-8 keyboard-layouts=de keyboard-variants=nodeadkeys” (see also at http://www.ccpeine.de/?p=1152)

I think, this bug can safely be closed.

Thank you very much for all the help!

Best regards

Hans

I have updated nvidia-graphics-modules in kali-proposed-updates. It now builds nvidia-kernel-3.12-kali1-amd64 and nvidia-kernel-3.12-kali1-686-pae and nvidia-kernel-3.12-kali1-486 which provide the pre-compiled modules.