From clangd-dev at lists.llvm.org  Thu Jul  9 04:37:11 2020
From: clangd-dev at lists.llvm.org (Hans Wennborg via clangd-dev)
Date: Thu, 9 Jul 2020 13:37:11 +0200
Subject: [clangd-dev] [11.0.0 Release] One week to the branch
Message-ID: <CAB8jPhd5j7w9N_T65zRpvu-jgnk=Eb0EVehGhOnYhGZt_uON8Q@mail.gmail.com>

Hello everyone,

This is a short reminder that the upcoming release branch is scheduled
for next week: Wednesday, 15 July. (See schedule to the right on
https://llvm.org)

When the branch is created, the trunk version will be bumped to 12.0.0.

Please try to avoid major disruptions to the tree around the branch
point. If you become aware of any problems, please let me know via
email.

Thanks,
Hans

From clangd-dev at lists.llvm.org  Wed Jul 15 05:09:43 2020
From: clangd-dev at lists.llvm.org (Hans Wennborg via clangd-dev)
Date: Wed, 15 Jul 2020 14:09:43 +0200
Subject: [clangd-dev] [11.0.0 Release] The release branch is here;
	trunk is now 12.0.0
Message-ID: <CAB8jPheD5syd9nyOdUjhuW7Xf11DpPYNXidQWHkiO2uVnRV+4A@mail.gmail.com>

Hello everyone,

The release branch for LLVM 11 was created from the trunk at
2e10b7a39b930ef8d9c4362509d8835b221fbc0a, and the trunk version was
bumped to 12.0.0.

Release blockers are tracked by https://llvm.org/PR46725 Please mark
any bugs, old or new, that need to be fixed before the release as
blocking that bug.

Please keep me in the loop via email on any bugs, commits, or other
issues that might be relevant for the release. In particular, if
you're currently investigating issues with trunk and working on fixes,
please help me make sure that those fixes end up on the branch also.

To get a change committed to the branch, please commit it to trunk as
per usual, and then request it to be merged -- ideally by filing a
blocker of https://llvm.org/PR46725, or by cc'ing me on the commit
email.

(Please don't report issues or request merges over
IRC/Discord/Discourse; there's a large risk that I'll miss it. Please
use email.)

The first release candidate will be tagged soon (hopefully in a day or
two if the branch looks stable), and testing of that can begin. The
full release schedule can be found under "Upcoming Releases" to the
right at https://llvm.org

Thanks,
Hans

From clangd-dev at lists.llvm.org  Thu Jul 16 07:34:11 2020
From: clangd-dev at lists.llvm.org (Hans Wennborg via clangd-dev)
Date: Thu, 16 Jul 2020 16:34:11 +0200
Subject: [clangd-dev] [llvm-dev] [11.0.0 Release] The release branch is
 here; trunk is now 12.0.0
In-Reply-To: <A79EEBFA-F317-4765-9D4D-B31570B1261E@apple.com>
References: <CAB8jPheD5syd9nyOdUjhuW7Xf11DpPYNXidQWHkiO2uVnRV+4A@mail.gmail.com>
 <A79EEBFA-F317-4765-9D4D-B31570B1261E@apple.com>
Message-ID: <CAB8jPhd0wZjoeDrdX0uvw30uHQUZRrTuebeL-XpyM_Ua1u7rCQ@mail.gmail.com>

Sounds good to me.

On Wed, Jul 15, 2020 at 8:25 PM Louis Dionne <ldionne at apple.com> wrote:
>
> Thanks for tagging, Hans. Can I go ahead with the CMake version bump advertised in http://lists.llvm.org/pipermail/llvm-dev/2020-June/142893.html?
>
> This may cause some instability on a few builders that have not upgraded to a recent CMake yet, but I'll iterate as explained in the linked thread. Let me know if it's OK to go ahead now or if you'd prefer that I wait for a few days.
>
> Cheers,
> Louis
>
> > On Jul 15, 2020, at 08:09, Hans Wennborg via llvm-dev <llvm-dev at lists.llvm.org> wrote:
> >
> > Hello everyone,
> >
> > The release branch for LLVM 11 was created from the trunk at
> > 2e10b7a39b930ef8d9c4362509d8835b221fbc0a, and the trunk version was
> > bumped to 12.0.0.
> >
> > Release blockers are tracked by https://llvm.org/PR46725 Please mark
> > any bugs, old or new, that need to be fixed before the release as
> > blocking that bug.
> >
> > Please keep me in the loop via email on any bugs, commits, or other
> > issues that might be relevant for the release. In particular, if
> > you're currently investigating issues with trunk and working on fixes,
> > please help me make sure that those fixes end up on the branch also.
> >
> > To get a change committed to the branch, please commit it to trunk as
> > per usual, and then request it to be merged -- ideally by filing a
> > blocker of https://llvm.org/PR46725, or by cc'ing me on the commit
> > email.
> >
> > (Please don't report issues or request merges over
> > IRC/Discord/Discourse; there's a large risk that I'll miss it. Please
> > use email.)
> >
> > The first release candidate will be tagged soon (hopefully in a day or
> > two if the branch looks stable), and testing of that can begin. The
> > full release schedule can be found under "Upcoming Releases" to the
> > right at https://llvm.org
> >
> > Thanks,
> > Hans
> > _______________________________________________
> > LLVM Developers mailing list
> > llvm-dev at lists.llvm.org
> > https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>

From clangd-dev at lists.llvm.org  Sun Jul 12 09:55:00 2020
From: clangd-dev at lists.llvm.org (Tanya Lattner via clangd-dev)
Date: Sun, 12 Jul 2020 09:55:00 -0700
Subject: [clangd-dev] 2020 Virtual LLVM Developers' Meeting - Call for
 presentations! (deadline EXTENDED)
In-Reply-To: <80B8BC43-AE4C-4D2F-A129-0B73BAE0E55F@llvm.org>
References: <80B8BC43-AE4C-4D2F-A129-0B73BAE0E55F@llvm.org>
Message-ID: <3BF4A06F-BAD2-41C4-8A30-0460B617E9F0@llvm.org>

The deadline has been extended until July 20 11:59PM PDT.

Thanks,
Tanya

> On Jun 12, 2020, at 4:58 PM, Tanya Lattner <tanyalattner at llvm.org> wrote:
> 
> All developers and users of LLVM and related sub-projects are invited to present at the first virtual 2020 LLVM Developers’ Meeting <http://llvm.org/devmtg/2020-09/>!
> 
> We are looking for the following proposals:
> Technical Talks (25-30 minutes including Q&A):
> Talks on:
> LLVM Infrastructure,Clang and all related sub-projects
> On uses of LLVM in academia or industry
> On new projects using Clang or LLVM
> Tutorials (60 minutes)
> In depth talks on LLVM infrastructure or other core libraries, tools, etc. Demos encouraged.
> Student Research Competition Technical Talks & Poster (20-25 minutes including Q&A)
> Talks from students using LLVM, Clang, and all sub-projects in research.
> The audience usually votes on a winner.
> Lightning Talks (5 minutes, no questions, no discussions)
> Quick talks about a use or improvement of LLVM and other sub-projects.
> Birds of a Feather <https://en.wikipedia.org/wiki/Birds_of_a_feather_(computing)> (30 minutes)
> Historically these are informal and ad-hoc, but at our meeting they are prepared in advance and are guided discussions (usually with a slide deck) about a specific topic. For informal and ad-hoc, please consider a Round Table (details to come). 
> Panels (30-60 minutes)
> Panels may discuss any topic as long as it’s relevant to LLVM or related sub-projects. Panels can take many forms, but a common format is to begin with short introductions from each panel member, and follow with an interactive dialogue among the panelists and audience members. Panels should consist of at least 3 people and have a moderator.
> Posters (1 hour session)
> Posters presenting work using LLVM and related subprojects. Poster presenters will answer questions from attendees and give mini presentations. 
> 
> As this conference is virtual and our very first, we are still working out the numerous details. The length of the talk types below are subject to change, but the above gives you an idea of what we expect. The majority of the talks will be pre-recorded except for panels, birds of a feather, posters, and possibly lightning talks.  In addition, we will be requiring most speakers to participate in some form of live Q&A. Time zones are a huge challenge with a virtual conference and we will do our best to be reasonable in our expectations. 
> 
> The timeframe for submission is also much tighter due to allowing time for speakers to record and us to process videos. We apologize for the inconvenience. 
> 
> Submission Requirements:
> The submission deadline is July 15, 2020 at 11:59PM PDT.
> 
> Please submit your proposal here:
> LLVM2020 Submissions <https://hotcrp.llvm.org/usllvm2020/>
> For each proposal, please submit a title, short abstract, submission type, abstract for the website, include who the speakers or panel member/moderators are, and provide a more detailed description of the talk through an extended PDF abstract. We highly recommend you consult and follow the guide at the end of this CFP when submitting your proposal.
> 
> FAQ
> 
> When will I be notified of acceptance?
> 
> Our goal is to notify all submissions by July 31, 2020.
> 
> When is the conference?
> 
> In order to not conflict with another large virtual conference, we have moved the 2020 LLVM Developers’ Meeting to October 6-8. The exact times of the conference are still under discussion.
> 
> Should I register if I have submitted a proposal?
> 
> Given this is a virtual conference and we have less space restrictions and a different fee structure, you can register at any time before the registration deadline. We will be providing details on registration in July. 
> 
> When will the recordings be due?
> 
> Recordings should be completed by September 14.
> 
> Will I be required to have a video camera?
> 
> We do not want the lack of recording equipment to prevent submissions and will be sorting out options to help those without recording equipment available. Please stay tuned for details. 
> 
> When will my live Q&A be?
> 
> As the conference is virtual, our attendees and speakers will be in many different time zones. We won’t know the program until closer to the event and then we can start to form a schedule. Our schedule will attempt to meet the needs of many time zones, but will not be a perfect solution. You may be asked to give a live Q&A early in the morning, late at night, or multiple times. 
> 
> Who is on the program committee?
> 
> The program committee is composed of active developers of the LLVM, Clang, and related sub-communities. The website will be updated with the list of the program committee members.
> 
> I have a question, who do I contact?
> 
> Please email the LLVM Dev Mtg Organizers (devmtg-organizers at lists.llvm.org <mailto:devmtg-organizers at lists.llvm.org>), or the LLVM Developers’ Meeting mailing list. http://lists.llvm.org/mailman/listinfo/llvm-devmeeting <http://lists.llvm.org/mailman/listinfo/llvm-devmeeting>
> 
> Detailed guidance on writing a proposal for the LLVM Developers’ Meeting
> 
> Writing a proposal for the LLVM Developers’ Meeting
> 
> This document is a guide to help you submit the best proposal and increase your chances of your proposal being accepted. The LLVM Developers’ Meeting program committee receives more proposals than can be accepted, so please read this guide carefully.
> 
> If you have never presented at an LLVM Developers’ Meeting, then do not fear this process. We are actively looking for new speakers who are excited about LLVM and helping grow the community through these educational talks! You do not need to be a long time developer to submit a proposal.
> 
> General Guidelines:
> It should be clear from your abstract what your topic is, who your targeted audience is, and what are the takeaways for attendees. The program committee gets a lot of proposals and does not have time to read 10 page papers for each submission (excluding SRC submissions).
> Talks about a use of LLVM (etc) should include details about how LLVM is used and not only be about the resulting application.
> Tutorials on “how to use X” in LLVM (or other subproject) are greatly desired and beneficial to many developers. Entry level topics are encouraged as well.
> Talks that have been presented at other technical conferences tend to not get accepted. If you have presented this topic before, make it clear what is new and different in your talk.
> 
> 
> Technical Talk and SRC Talk  Proposal Template:
> ** Include in the extended abstract PDF attachment **
> 
> Title:
> This will be displayed on the website, schedule, and signs. Keep it short and catchy to attract attendees to your talks. A couple of examples are “WebAssembly: Here Be Dragons” or “Beyond Sanitizers: guided fuzzing and security hardening”. There is also a field in the submission form for this same title.
> 
> Description:
> 1-2 paragraphs. You can also use this for the Website Abstract field in the submission form.
> We suggest you proof read and pay attention to grammar.
> 
> Details:
> Here you can include more details about your talk. An outline, demo description, background of the speaker, etc. 1-2 paragraphs is usually sufficient.
> This section will not be published and is intended for the PC to better understand how interesting your talk will be to the audience. For example, if you would prefer not to reveal some conclusions in the published abstract, explaining them here ensures that the PC can take them into account when evaluating your proposal.
> 
> SRC Paper:
> If this is an SRC talk, please attach your paper as well.
> 
> Panel Talk Proposal Template:
> ** Include in the extended abstract PDF attachment **
> 
> Title:
> This will be displayed on the website, schedule, and signs. These tend to be very straight forward about the area being discussed. An example is “Future directions and features for LLDB”. There is also a field in the submission form for this same title.
> 
> Description:
> 1-2 paragraphs. May also be used for the website abstract field in the submission form.
> Provide some talking points or potential subtopics.
> We suggest you proof read and pay attention to grammar.
> 
> Details:
> Provide additional details: goals of the panel, and example questions. Panels are to brainstorm and discuss ideas on a specific topic between the experts on the panel and the audience. You should also include detailed 2-3 sentence bios for each speaker on the panel. You may or may not include speaker names as the submissions are blind.
> 
> Tutorial Proposal Template:
> ** Include in the extended abstract PDF attachment **
> 
> Title:
> This will be displayed on the website, schedule, and signs. Keep it short and catchy to attract attendees to your talks. There is also a field in the submission form for this same title.
> 
> Description:
> 1-2 paragraphs. May also be used for the website abstract field in the submission form.
> We suggest you proof read and pay attention to grammar.
> 
> Details:
> Include additional details such as tutorial outline, what materials you will provide attendees, etc.
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/clangd-dev/attachments/20200712/51af582c/attachment-0001.html>

From clangd-dev at lists.llvm.org  Wed Jul 15 11:25:26 2020
From: clangd-dev at lists.llvm.org (Louis Dionne via clangd-dev)
Date: Wed, 15 Jul 2020 14:25:26 -0400
Subject: [clangd-dev] [llvm-dev] [11.0.0 Release] The release branch is
 here; trunk is now 12.0.0
In-Reply-To: <CAB8jPheD5syd9nyOdUjhuW7Xf11DpPYNXidQWHkiO2uVnRV+4A@mail.gmail.com>
References: <CAB8jPheD5syd9nyOdUjhuW7Xf11DpPYNXidQWHkiO2uVnRV+4A@mail.gmail.com>
Message-ID: <A79EEBFA-F317-4765-9D4D-B31570B1261E@apple.com>

Thanks for tagging, Hans. Can I go ahead with the CMake version bump advertised in http://lists.llvm.org/pipermail/llvm-dev/2020-June/142893.html?

This may cause some instability on a few builders that have not upgraded to a recent CMake yet, but I'll iterate as explained in the linked thread. Let me know if it's OK to go ahead now or if you'd prefer that I wait for a few days.

Cheers,
Louis

> On Jul 15, 2020, at 08:09, Hans Wennborg via llvm-dev <llvm-dev at lists.llvm.org> wrote:
> 
> Hello everyone,
> 
> The release branch for LLVM 11 was created from the trunk at
> 2e10b7a39b930ef8d9c4362509d8835b221fbc0a, and the trunk version was
> bumped to 12.0.0.
> 
> Release blockers are tracked by https://llvm.org/PR46725 Please mark
> any bugs, old or new, that need to be fixed before the release as
> blocking that bug.
> 
> Please keep me in the loop via email on any bugs, commits, or other
> issues that might be relevant for the release. In particular, if
> you're currently investigating issues with trunk and working on fixes,
> please help me make sure that those fixes end up on the branch also.
> 
> To get a change committed to the branch, please commit it to trunk as
> per usual, and then request it to be merged -- ideally by filing a
> blocker of https://llvm.org/PR46725, or by cc'ing me on the commit
> email.
> 
> (Please don't report issues or request merges over
> IRC/Discord/Discourse; there's a large risk that I'll miss it. Please
> use email.)
> 
> The first release candidate will be tagged soon (hopefully in a day or
> two if the branch looks stable), and testing of that can begin. The
> full release schedule can be found under "Upcoming Releases" to the
> right at https://llvm.org
> 
> Thanks,
> Hans
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev


From clangd-dev at lists.llvm.org  Thu Jul 16 07:53:12 2020
From: clangd-dev at lists.llvm.org (Louis Dionne via clangd-dev)
Date: Thu, 16 Jul 2020 10:53:12 -0400
Subject: [clangd-dev] [llvm-dev] [11.0.0 Release] The release branch is
 here; trunk is now 12.0.0
In-Reply-To: <CAB8jPhd0wZjoeDrdX0uvw30uHQUZRrTuebeL-XpyM_Ua1u7rCQ@mail.gmail.com>
References: <CAB8jPheD5syd9nyOdUjhuW7Xf11DpPYNXidQWHkiO2uVnRV+4A@mail.gmail.com>
 <A79EEBFA-F317-4765-9D4D-B31570B1261E@apple.com>
 <CAB8jPhd0wZjoeDrdX0uvw30uHQUZRrTuebeL-XpyM_Ua1u7rCQ@mail.gmail.com>
Message-ID: <39A86311-9ABB-40CA-9560-77A24EF30135@apple.com>

Thanks! I've just pushed the commit and will iterate on it until everyone is upgraded.

Happy to finally get this started!
Louis

> On Jul 16, 2020, at 10:34, Hans Wennborg <hans at chromium.org> wrote:
> 
> Sounds good to me.
> 
> On Wed, Jul 15, 2020 at 8:25 PM Louis Dionne <ldionne at apple.com> wrote:
>> 
>> Thanks for tagging, Hans. Can I go ahead with the CMake version bump advertised in http://lists.llvm.org/pipermail/llvm-dev/2020-June/142893.html?
>> 
>> This may cause some instability on a few builders that have not upgraded to a recent CMake yet, but I'll iterate as explained in the linked thread. Let me know if it's OK to go ahead now or if you'd prefer that I wait for a few days.
>> 
>> Cheers,
>> Louis
>> 
>>> On Jul 15, 2020, at 08:09, Hans Wennborg via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>>> 
>>> Hello everyone,
>>> 
>>> The release branch for LLVM 11 was created from the trunk at
>>> 2e10b7a39b930ef8d9c4362509d8835b221fbc0a, and the trunk version was
>>> bumped to 12.0.0.
>>> 
>>> Release blockers are tracked by https://llvm.org/PR46725 Please mark
>>> any bugs, old or new, that need to be fixed before the release as
>>> blocking that bug.
>>> 
>>> Please keep me in the loop via email on any bugs, commits, or other
>>> issues that might be relevant for the release. In particular, if
>>> you're currently investigating issues with trunk and working on fixes,
>>> please help me make sure that those fixes end up on the branch also.
>>> 
>>> To get a change committed to the branch, please commit it to trunk as
>>> per usual, and then request it to be merged -- ideally by filing a
>>> blocker of https://llvm.org/PR46725, or by cc'ing me on the commit
>>> email.
>>> 
>>> (Please don't report issues or request merges over
>>> IRC/Discord/Discourse; there's a large risk that I'll miss it. Please
>>> use email.)
>>> 
>>> The first release candidate will be tagged soon (hopefully in a day or
>>> two if the branch looks stable), and testing of that can begin. The
>>> full release schedule can be found under "Upcoming Releases" to the
>>> right at https://llvm.org
>>> 
>>> Thanks,
>>> Hans
>>> _______________________________________________
>>> LLVM Developers mailing list
>>> llvm-dev at lists.llvm.org
>>> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>> 


From clangd-dev at lists.llvm.org  Tue Jul 28 10:49:59 2020
From: clangd-dev at lists.llvm.org (Hans Wennborg via clangd-dev)
Date: Tue, 28 Jul 2020 19:49:59 +0200
Subject: [clangd-dev] [11.0.0 Release] Release Candidate 1 is here
Message-ID: <CAB8jPhfEK_B9Rnk+1LYwMVGcQ0pZ3RQ0qqOHhgkdBCw36FcPRQ@mail.gmail.com>

Hello everyone,

We're a little bit behind schedule, but RC1 is now here. It was tagged
earlier today as llvmorg-11.0.0-rc1.

Source code and docs are available at
https://prereleases.llvm.org/11.0.0/#rc1 and
https://github.com/llvm/llvm-project/releases/tag/llvmorg-11.0.0-rc1

Pre-built binaries will be added as they become available.

Please file bug reports for any issues you find as blockers of
https://llvm.org/pr46725

Release testers: please start your engines, run the script, share your
results, and upload binaries.

RC2 was originally scheduled for Friday, but seeing as we just cut
this one it will come a little later.

Thanks,
Hans

From clangd-dev at lists.llvm.org  Wed Jul 29 05:02:25 2020
From: clangd-dev at lists.llvm.org (=?UTF-8?Q?Micha=C5=82_G=C3=B3rny?= via clangd-dev)
Date: Wed, 29 Jul 2020 14:02:25 +0200
Subject: [clangd-dev] [Release-testers] [11.0.0 Release] Release
	Candidate 1 is here
In-Reply-To: <CAB8jPhfEK_B9Rnk+1LYwMVGcQ0pZ3RQ0qqOHhgkdBCw36FcPRQ@mail.gmail.com>
References: <CAB8jPhfEK_B9Rnk+1LYwMVGcQ0pZ3RQ0qqOHhgkdBCw36FcPRQ@mail.gmail.com>
Message-ID: <59cd4e0a8eed88907214b8e1e73095b31612ed88.camel@gentoo.org>

On Tue, 2020-07-28 at 19:49 +0200, Hans Wennborg via Release-testers
wrote:
> Hello everyone,
> 
> We're a little bit behind schedule, but RC1 is now here. It was tagged
> earlier today as llvmorg-11.0.0-rc1.
> 
> Source code and docs are available at
> https://prereleases.llvm.org/11.0.0/#rc1 and
> https://github.com/llvm/llvm-project/releases/tag/llvmorg-11.0.0-rc1
> 
> Pre-built binaries will be added as they become available.
> 
> Please file bug reports for any issues you find as blockers of
> https://llvm.org/pr46725
> 
> Release testers: please start your engines, run the script, share your
> results, and upload binaries.
> 

On Gentoo:

- clang fails to build due to using internal llvm headers, bug filed.

- openmp needs backport from master, also filed.

- lldb tests are still broken, still had no time to look at them.

- compiler-rt started failing on GotsanCheck after switching to new
build machine, I'm trying to figure it out right now.

-- 
Best regards,
Michał Górny

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 618 bytes
Desc: This is a digitally signed message part
URL: <http://lists.llvm.org/pipermail/clangd-dev/attachments/20200729/bf2f8170/attachment.sig>

From clangd-dev at lists.llvm.org  Thu Jul 30 11:35:51 2020
From: clangd-dev at lists.llvm.org (Bernhard Rosenkraenzer via clangd-dev)
Date: Thu, 30 Jul 2020 20:35:51 +0200
Subject: [clangd-dev]
 =?utf-8?b?Pz09P3V0Zi04P3E/IFtSZWxlYXNlLXRlc3RlcnNd?=
 =?utf-8?b?IFsxMS4wLjA/PT0/dXRmLTg/cT8gUmVsZWFzZV0gUmVsZWFzZSBDYW5kaWRh?=
 =?utf-8?q?te_1_is_here?=
In-Reply-To: <CAB8jPhfEK_B9Rnk+1LYwMVGcQ0pZ3RQ0qqOHhgkdBCw36FcPRQ@mail.gmail.com>
Message-ID: <7af9-5f231300-d-12231160@105686244>

Hi, 
 
On Tuesday, July 28, 2020 19:49 CEST, Hans Wennborg via Release-testers <release-testers at lists.llvm.org> wrote: 
 
> Source code and docs are available at
> https://prereleases.llvm.org/11.0.0/#rc1 and
> https://github.com/llvm/llvm-project/releases/tag/llvmorg-11.0.0-rc1

Fails to build here in OpenMandriva with flang and docs enabled.
Will look a bit closer and report a bug/fix when I have a bit of time.

FAILED: tools/flang/docs/CMakeFiles/docs-flang-html 
cd /home/bero/temp/abf/llvm/BUILD/llvm-project-release-11.x/build/tools/flang/docs && /usr/bin/sphinx-build -b html -d /home/bero/temp/abf/llvm/BUILD/llvm-project-release-11.x/build/tools/flang/docs/_doctrees-flang-html -q -t builder-html /home/bero/temp/abf/llvm/BUILD/llvm-project-release-11.x/flang/docs /home/bero/temp/abf/llvm/BUILD/llvm-project-release-11.x/build/tools/flang/docs/html

Application error:
config directory doesn't contain a conf.py file (/home/bero/temp/abf/llvm/BUILD/llvm-project-release-11.x/flang/docs)
[16/721] Generating man Sphinx documentation for flang into "/home/bero/temp/abf/llvm/BUILD/llvm-project-release-11.x/build/tools/flang/docs/man"
FAILED: tools/flang/docs/CMakeFiles/docs-flang-man