-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
www-client/ungoogled-chromium-125.0.6422.141_p1: track_event_data_source.h:331:20: error: a template argument list is expected after a name prefixed by the template keyword [-Wmissing-template-arg-list-after-template-kw] #351
Comments
Give this patch a try: https://android.googlesource.com/platform/external/perfetto.git/+/e2f661907a717551235563389977b7468da6d45e%5E%21/#F0 Note though, that it won't apply from the sources root. |
thanks! i had to remove one more |
i encountered the same issue in |
no more of these issues, but i didn't finish the build as i got an error in clang... |
i just synced the repo and tried |
Because it is an llvm issue, not Chromium. |
I could compile with next patch placed at |
I can confirm the same patch works with www-client/ungoogled-chromium-126.0.6478.126_p1 |
@Gerodote Have you tried live version of llvm? If the issue persists there, perhaps I should include the patch. |
@PF4Public , I could not compile some parts of llvm-9999 stack like two or three days ago, that's why I'm using llvm with version 19.0.0_pre20240623 , though, I'll test with version 19.0.0_pre20240706 |
Chromium developers seem to acknowledge this issue: https://chromium-review.googlesource.com/c/chromium/src/+/5604664. The fix should be in 127. |
issue persist. afaik, they are not going to fix it because it's by standard. |
i commented on their bug that i found similar at llvm/llvm-project#95720 i also have another issue when compiling ungoogled-chromium (it seems i'm the only one getting it though) so i filed this issue llvm/llvm-project#96623 which was chained to two follow-up issues as they were able to reproduce it. |
I've got the same impression. I'll include your patch then. |
If the other patches on here don't fix it up for everyone, here's a link to the patch that I compiled after chasing down all the links in this ticket and editing their patches - https://pastebin.com/96ih8dT7 . It worked for me with |
@brianpardy I wonder why you need something additional, is it because of live version? |
@brianpardy , I wonder too |
They may not strictly be needed. I prepped this patch just before this issue got active again and haven't tried the more minimal patches that were posted recently. The grpc and BUILD.gn contents came from https://issuetracker.google.com/issues/344680447 . I kept building and failing and just pulled in every patch that looked relevant. Or my USE flags might make them needed, I build with nvidia, lto and pgo.
|
@brianpardy Do you intentionally use |
@PF4Public yes, I can see that I specifically enabled libcxx when a change was made during the 121- series to default it to false, I had build errors at that time without it. I don't know if I still need it on current releases. |
I try my best to decouple ungoogled-chromium from libcxx and rust in my overlay. Sometimes it takes more time than I anticipated (and I have less at my disposal) :) |
this is the error:
here are the use flags:
and here clang versions:
The text was updated successfully, but these errors were encountered: