Sample project packing crash: "RunUAT ERROR: AutomationTool..."

Arch Linux, UE4 release installed without errors (A new, community-hosted Unreal Engine Wiki - Announcements - Epic Developer Community Forums)

Opened the editor, new project, “2d sample”, no starter content. All settings are stock, nothing has been touched in the project. File → “Package Project” → “Linux”

Runs for ~15-30 minutes LOG: UE4 Linux package sample project crash - Pastebin.com

One error line “UATHelper: Packaging (Linux): RunUAT ERROR: AutomationTool was unable to run successfully.
PackagingResults: Error: Unknown Error”

I have 0 experience in UE4 so this is a test whether I want to use it as a dev platform. I set the project folder as target for the “build/packaging” but there’s nothing in it. I have no idea where to begin, as this is the simplest test that you could ask for which simply fails. Thank you for any productive feedback.

UPDATE: For some reason the “output log window” in UE4 is hiding important information, yes all filters ticked.
Investigating the terminal , I’m being informed about this new log file: “UAT_Log.txt” Log: UAT_Log.txt - Pastebin.com

Hey, it looks like you did not compile correctly(At least for Arch), you will need to recompile the engine in the most likely case. I am not using the AUR package but the patches in the AUR are handy to get everything working as it should. Check aur.git - AUR Package Repositories

Also I tend to RunUAT from terminal as it gives better output. This gives some hints on that A new, community-hosted Unreal Engine Wiki - Announcements - Unreal Engine Forums

Would you mind explaining what exactly gives you that impression? Fixing a problem by “avoiding” it is not a solution. The compilations was error less, as I already stated

UPDATE2: I downgraded to clang35, from clang5 latest version. UE4 compiled flawless with it, but packaging won’t …
So now all good:

********** STAGE COMMAND COMPLETED **********
********** PACKAGE COMMAND STARTED **********
********** PACKAGE COMMAND COMPLETED **********
********** ARCHIVE COMMAND STARTED **********
********** ARCHIVE COMMAND COMPLETED **********
BUILD SUCCESSFUL
AutomationTool exiting with ExitCode=0 (Success)

So I am using UE4 on Arch for some time now, and packaging my project daily. I am not avoiding anything just using a verified tested and submitted upstream way to build the engine. Your error messages are something I have seen before and I am providing you with a solution that works an a current clang version so you do not have to downgrade or anything like you mentioned in your accepted answer.

Technically the Engine compilation and functionality is probably tested on something like Ubuntu and since we are using something that is not Ubuntu the compilation process might vary a bit hence the patches I linked.

The same error you have always appears when clang version changes a bit and the editor needs to be recompiled from time to time. So if you want to stick with older clang it should work just fine, for those of us that need newer clang for other things and downgrading every time we want to do Engine work(i.e. daily) is not an option.