I guess your machine runs out of memory and the kernel decides to kill the compiler to keep the rest of the system healthy. You can confirm this by checking the output of 'dmesg' after the error happens.

If you go trough the article Marcel referenced and start at the top and work your way slowly down you are guided through the process of installing a suitable openembedded environment and building your first image for the target. (you would probably save some time when at first bitbaking console-tdx-image instead of of angstrom-lxde-image)

After that you could go trough the qt-creator page, again starting at top and go work your way slowly down which would make you create and install:

a image for the target with the relevant qt libraries

the SDK with the relevant qt libraries

If you are new to embedded Linux I recommend attending training on this subject, e.g. as one provided by free-electrons or at least go through their slides to make yourself familiar with some of the terms and interworking going on on such a system.

While screen shots are anyway not the preferred way to convey log output, as one can not search in it or can not make sure if 'O' is a letter or a number, in yours one can only see that qtwebkit did not compile successfully, the real cause of the error is hidden somewhere outside of the screen shot.

We might be able to give some useful advice if you provide the build log file, e.g. as saved from the terminal window, or as stored here:tmp-glibc/log/cooker/colibri-imx6/console-latest.logtogether with the logfile from the task that failed which is referenced in the error text you actually have in your screenshot, e.g.:tmp-glibc/work/armv7at2hf-neon-angstrom-linux-gnueabi/qtwebkit/5.7.1+gitAUTOINC+76e2732f01-r0/temp/log.do_compile.2661