llvm dev - Apr 2016 - Status of the official LLVM APT repositories

On Wed, Apr 13, 2016 at 2:09 AM, Amaury SECHET via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> I'd like to shime in here. These apt repository used to contain
packages
> named llvm-3.8-tools containing, amongst other things, the lit python
> library used to test llvm. It seems that it went away recently and I have
> travis build failing because of this.
>
> What is going here ? It that just a mistake ? Is there something I can do
> to help get this package back ?
>
To get Lit on Travis, we do
install:
  - pip install --user lit
  - python -c "import lit; lit.main();" --version | head -n 1

Did the tools package contain "not" and "FileCheck"? (We
currently have to
carry copies of them in our own source tree.)
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20160413/c6ee3599/attachment.html>

On Wed, Apr 13, 2016 at 1:00 AM, Johan Engelen via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> To get Lit on Travis, we do
> install:
>   - pip install --user lit
>   - python -c "import lit; lit.main();" --version | head -n 1
>
> Did the tools package contain "not" and "FileCheck"?
(We currently have to
> carry copies of them in our own source tree.)
>
I hope it doesn't contain 'not', that executable name is a little
too
generic to install into /usr/bin. We could probably distribute FileCheck,
though. I doubt we'll see name collisions, and other projects seem to find
it useful.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20160413/815638a7/attachment.html>

On Wed, Apr 13, 2016 at 6:59 PM, Reid Kleckner <rnk at google.com> wrote:
> On Wed, Apr 13, 2016 at 1:00 AM, Johan Engelen via llvm-dev <
> llvm-dev at lists.llvm.org> wrote:
>
>> To get Lit on Travis, we do
>> install:
>>   - pip install --user lit
>>   - python -c "import lit; lit.main();" --version | head -n 1
>>
>> Did the tools package contain "not" and
"FileCheck"? (We currently have
>> to carry copies of them in our own source tree.)
>>
>
> I hope it doesn't contain 'not', that executable name is a
little too
> generic to install into /usr/bin.
>
Maybe :)

> We could probably distribute FileCheck, though. I doubt we'll see name
> collisions, and other projects seem to find it useful.
>
That would be nice for LDC. The "not" source code is compatible with
LLVM
3.5-3.9 at least, so we only need one not.cpp file. For FileCheck we need a
version for each LLVM version we support (3.5-3.9).
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20160413/93bd0c6d/attachment.html>