Bug 200269
| Summary: | Clang failed due to some internal error during buildworld on RPI2. | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Base System | Reporter: | jau | ||||||||
| Component: | arm | Assignee: | freebsd-arm (Nobody) <freebsd-arm> | ||||||||
| Status: | Closed Overcome By Events | ||||||||||
| Severity: | Affects Some People | CC: | loos, mmoll, thj | ||||||||
| Priority: | --- | ||||||||||
| Version: | CURRENT | ||||||||||
| Hardware: | arm | ||||||||||
| OS: | Any | ||||||||||
| Attachments: |
|
||||||||||
Created attachment 156855 [details]
1st of the two files clang instructed to be attached
Created attachment 156856 [details]
2nd of the two files clang instructed to be attached
c++: error: unable to execute command: Killed This usually happens when you run out of memory, do you have any swap space set ? 1GB of RAM is not enough to build world with -jX on Rpi 2. Jukka, what's the status here? |
Created attachment 156854 [details] The last 150 lines of the build time messages I was maybe pushing things a bit, but I decided to try buildworld and buildkernel on my RPI2. It would have been nice to be able to say it is in principle self hosting. As it seems, it is not quite there yet. During buildworld while clang was compiling itself it failed with an error message which did not help me much. Obviously there was some sort of an internal error, but that was pretty much all. So, just in case someone knows clang better and has some interest in understanding what happened I attach the last 150 lines of the build time messages and the couple of files clang itself instructed to be attached to any bug reports. The cpp file was so big that it became necessary to compress it using xz.