aports/main/llvm4, branch master Main aports tree community/llvm4: move from main 2017-11-14T17:44:44+00:00 Jakub Jirutka jakub@jirutka.cz 2017-11-06T16:22:06+00:00 5264d838ede53a1afd1b238ad278041b6e4203cf The default (latest) llvm package is now llvm5. 
The default (latest) llvm package is now llvm5.
main/llvm*: upgrade to 5.0.0 2017-11-14T17:42:44+00:00 xentec xentec@aix0.eu 2017-10-23T16:24:56+00:00 9ba5bef315e95740081f6f36e646a7c137d36e6a 






community/php7: add FIXME comment
2017-09-26T15:43:42+00:00

Natanael Copa
ncopa@alpinelinux.org

2017-09-26T15:39:51+00:00

8686e5201e95356a82d2a7a38d9f91f590db566f












main/llvm4: add missing dependency py-setuptools to -test-utils
2017-05-17T10:54:08+00:00

Jakub Jirutka
jakub@jirutka.cz

2017-05-17T10:48:11+00:00

3dd1698d0276c15f6453d1999ae8dcaa1043ecb4












main/llvm4: improve abuild's support for non-default LLVM usage
2017-05-17T01:10:01+00:00

Jakub Jirutka
jakub@jirutka.cz

2017-05-17T01:08:02+00:00

735529259257a8cb168e4e4305f8bec0bcb2d6de

And also fix "replaces", it's inherited to subpackages, so all
subpackages had replaces="llvm".





And also fix "replaces", it's inherited to subpackages, so all
subpackages had replaces="llvm".







main/llvm4: rename lit subpkg to -test-utils, move FileCheck and not here
2017-05-17T01:10:01+00:00

Jakub Jirutka
jakub@jirutka.cz

2017-05-17T00:36:09+00:00

24bd280a18ce673ba4f4f22601c9d5aa949895d6

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.





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.







main/llvm4: rebuild after adding new subpkg
2017-05-16T18:19:06+00:00

Jakub Jirutka
jakub@jirutka.cz

2017-05-16T18:19:06+00:00

d4d185456f222da322e7f3a02980fe404838bb2c












main/llvm4: add lit subpackage
2017-05-16T16:11:23+00:00

Shiz
hi@shiz.me

2017-05-12T11:30:23+00:00

658eb1da4c0690d2e16d506c881eac3d3444ec39












main/llvm4: ignore test failures on s390x for now
2017-04-25T13:15:48+00:00

Jakub Jirutka
jakub@jirutka.cz

2017-04-25T13:15:48+00:00

f760379d178551bbc008bd5250598062ce35ea0f

  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





  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







main/llvm4: disable check() on armhf
2017-04-25T13:06:50+00:00

Jakub Jirutka
jakub@jirutka.cz

2017-04-25T13:05:13+00:00

431e70edcbe28d57008805e5409f5aa9079e25d9

It takes tooo long to run them on the armhf builder.





It takes tooo long to run them on the armhf builder.