Open Quuxplusone opened 4 years ago
It should already be fixed in trunk and 9.x branch.
Attached build.log.gz
(66187 bytes, application/gzip): build log
I'm guessing it's this one:
------------------------------------------------------------------------
r366513 | lanza | 2019-07-19 01:40:23 +0200 (Fri, 19 Jul 2019) | 9 lines
[cmake] Update NATIVE build variables to account for standalone changes
Summary:
LLDB_PATH_TO_{CLANG,LLVM}_BUILD were removed and replaced with
{LLVM,Clang}_DIR. Adjust the NATIVE build to account for this.
Subscribers: mgorny
Differential Revision: https://reviews.llvm.org/D64959
------------------------------------------------------------------------
Let me give it a try.
(In reply to Michał Górny from comment #1)
> It should already be fixed in trunk and 9.x branch.
(In reply to Thiago Macieira from comment #3)
> I'm guessing it's this one:
>
> ------------------------------------------------------------------------
> r366513 | lanza | 2019-07-19 01:40:23 +0200 (Fri, 19 Jul 2019) | 9 lines
Well, that isn't the one. Can you point out which one it should be? There's
apparently only one commit in branches/release_90 beyond the final release and
it's unrelated.
Actually, I think it hasn't been pushed yet. The backport request is:
https://bugs.llvm.org/show_bug.cgi?id=43442
Also, you're using the wrong repository. The correct one is:
(In reply to Michał Górny from comment #5)
> Actually, I think it hasn't been pushed yet. The backport request is:
>
> https://bugs.llvm.org/show_bug.cgi?id=43442
Thanks, backport works.
> Also, you're using the wrong repository. The correct one is:
>
> https://github.com/llvm/llvm-project/
What do you mean? git.llvm.org is not the correct repository for llvm.org?
(In reply to Thiago Macieira from comment #6)
> > Also, you're using the wrong repository. The correct one is:
> >
> > https://github.com/llvm/llvm-project/
>
> What do you mean? git.llvm.org is not the correct repository for llvm.org?
Yes. That's just the old svn→git mirror and since svn isn't being updated...
(In reply to Michał Górny from comment #7)
> (In reply to Thiago Macieira from comment #6)
> > > Also, you're using the wrong repository. The correct one is:
> > >
> > > https://github.com/llvm/llvm-project/
> >
> > What do you mean? git.llvm.org is not the correct repository for llvm.org?
>
> Yes. That's just the old svn→git mirror and since svn isn't being updated...
Ah, got it. Thanks. Updating my clones then.
(In reply to Thiago Macieira from comment #8)
> (In reply to Michał Górny from comment #7)
> > (In reply to Thiago Macieira from comment #6)
> > > > Also, you're using the wrong repository. The correct one is:
> > > >
> > > > https://github.com/llvm/llvm-project/
> > >
> > > What do you mean? git.llvm.org is not the correct repository for llvm.org?
> >
> > Yes. That's just the old svn→git mirror and since svn isn't being
updated...
>
> Ah, got it. Thanks. Updating my clones then.
A merged repo makes for more difficult patch management for packages, though.
Now the patches I need to apply to lldb are in the same repository as the
patches for clang. And git format-patch will (by default) create files with one
dir too many (a/lldb, b/lldb) compared to the package.
Oh well, need to rewrite the scripts too then.
I know how you feel. I've spent a few hours updating all our packages in Gentoo.
Apparently the original plan presumed all those mirrors would continue to be operational but so far it doesn't seem to be happening.
Regenerating patches like this:
git format-patch -N --src-prefix=a/tools/ --dst-prefix=b/tools/ @{u} clang
rename 00 clang-00 00*.patch
git format-patch -N --no-prefix @{u} llvm
rename 00 llvm-00 00*.patch
build.log.gz
(66187 bytes, application/gzip)