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
Update brave to v1.52.122 #54
Conversation
I'll throw this at a beefy machine and see if it has anything for us tomorrow ;-) |
Not so much luck, it looks like a patch is out of date somewhere:
|
a4787b2
to
303ae7b
Compare
I've forgot to cleanup the patches, now all of them should apply. |
Thanks for the update. I just sent this off to build... |
With 303ae7b I got stuck on the same patch...
|
I think that you should prune those patches in |
Oh yuck, we need to change the wildcard line picking patches to expand from the |
303ae7b
to
2bc7ffc
Compare
upstream release Signed-off-by: Martin Rodriguez Reboredo <yakoyoku@gmail.com>
2bc7ffc
to
c8a2864
Compare
@alerque I think as of now everything can be prepared cleanly, please let me know if otherwise. |
I tried building this a few times but it's been hiding in a queue behind Electron builds. We've had lots more trouble with Google's Chromium repository, so some of our builds are switching to a mirror. Even though the repository is the same so you can share a backend data store for both, the PKGBUILD system doesn't like having different remotes, so we've renamed the GitHub mirror so that multiple builds can share it while still having access to the canonical one. I've switched this to the mirror. You can avoid re-downloading the sources if you want by manually renaming the directory and changing the remote URL in your pkgsrc cache if you are interested. The build I ran did not finish. I am not sure if this is a function of something not being initialized right in the sources before hand or something to do with Rust being fresh (1.70.0) and llvm being 15 not 17.
If that error tells you anything useful let me know. |
Seems that Chromium tries to use an intree built |
Thanks for the updates. I pulled them in and shipped it off for building. It got farther but still eventually tripped up on something Rust releated:
Note this is in a clean chroot builder using the current core and extra repositories to supply dependencies built using the same scripts official packages are built with on the same servers we use for offloading builds for official packages. |
e7219b0
to
4cd80ef
Compare
Seemingly, Brave uses another |
New failure paint:
|
Those seem to be warnings only, the error must be on that truncated part. |
You are correct, sorry I kind of skimmed over that. It turns out the error is way farther up in the build sequence:
bitcoin-core? |
4cd80ef
to
0ace7e8
Compare
I'd try to be more helpful besides just sending this to build and passing errors, but I'm swamped trying to get stupid Electron stuff rebuilt for Arch! What an absolute crazy-pants exercise! |
0ace7e8
to
c03da77
Compare
|
c03da77
to
dfc38ed
Compare
I feel that I'm closer, but I'll have to admit that I don't know such a way to at least predict which component is going to fail at compile time, wish I could have that hability. |
I don't know how close we are either but surely each one we get past must be that much closer! From working on Electron the last few weeks I don't think there is any good way to catch everything in advance, it is a lot of trial and error especially working with gcc patches. By the way how are you testing this on your end? Is it just a matter of disk space and processor time that means these aren't tested locally? Because you should be hitting exactly the same failures as I am. I'm kind of surprised your fixes have been working if you haven't been testing at all, and if you are testing I'm confused why you don't hit the next problems too. At this point you should be able to almost exactly replicate by builds with Arch's dev tooling, install |
I've been testing the build by running |
|
upstream release Signed-off-by: Martin Rodriguez Reboredo <yakoyoku@gmail.com>
dfc38ed
to
8c054e9
Compare
I have now built the monster, fully patched, and it works. For future reference I left a list of targets to build in certain order so it doesn't choke at least my machine. Hope it's helpful for someone else.
|
Another thing that I've recently discovered is that we can pass |
This PR is merged, thanks again for all the effort. The package I generated is also hosted in my user repository.
I'm happy to facilitate any useful changes applied to the Arch Chromium and Electron packages, but I don't know what those flags do. Do you have a link to where they are document or can you comment on how they would help? |
You are welcome too.
Those configs are pretty similar to GCC's/Clang's |
This PR updates
brave
to1.52.122
.Changes:
extra/chromium
at114.0.5735.110
.extra/chromium
GitLab repo.build()
to use fewer LOCs.TODOs:
makepkg -o
).(I may require a more powerful machine to compile things faster)see comment down below.