| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
The default (latest) llvm package is now llvm5.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
And also fix "replaces", it's inherited to subpackages, so all
subpackages had replaces="llvm".
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It seems that overriding pkgver for a subpackage really wasn't
a good idea. I still don't know what the heck happened on the build
servers, but for some unknown reason lit-*.apk was not uploaded to
mirrors. Also builders rebuilt llvm4 twice, even when the previous
build succeeded.
Anyway, I'm even more convinced that it was just a bad idea. Upstream
does not actually release lit, they release only llvm with bundled
lit. It has some version number in setup.py, but what if they let it
unchanged between two llvm releases, despite making some changes in
the lit's codebase?
It's true that it's wrong to call it lit-4.0.0 when its installed as
a python module with version number 0.6.0. So I kinda workarounded it
by renaming this subpackage to llvm4-test-utils with
provides="lit-0.6.0-rX". :) And to not leave lit here alone, I've
also moved FileCheck and not utils here, 'cause these are testing
utils too and lit needs them.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Failing Tests (5):
LLVM-Unit :: Support/SupportTests/FileOutputBuffer.Test
LLVM-Unit :: Support/SupportTests/FileSystemTest.FileMapping
LLVM-Unit :: Support/SupportTests/FileSystemTest.Resize
LLVM :: DebugInfo/PDB/pdbdump-readwrite.test
LLVM :: DebugInfo/PDB/pdbdump-write.test
Build log: https://gist.github.com/jirutka/6edc951ad5b8002cf1780546cf661edc
See also: https://github.com/alpinelinux/aports/pull/1261#issuecomment-296365081
|
| |
|
|
| |
It takes tooo long to run them on the armhf builder.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
SystemZ is target for s390x architecture.
|
| | |
|
| |
|
