Skip to content
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

Rebuild icu69 #214

Merged
merged 18 commits into from
Jan 20, 2022
Merged

Rebuild icu69 #214

merged 18 commits into from
Jan 20, 2022

Conversation

izahn
Copy link
Contributor

@izahn izahn commented Dec 15, 2021

Checklist

  • Used a personal fork of the feedstock to propose changes
  • Bumped the build number (if the version is unchanged)
  • Reset the build number to 0 (if the version changed)
  • Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
  • Ensured the license file is being packaged.

Closes #207
Closes #212
Closes #213

@conda-forge-linter
Copy link

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@@ -46,6 +46,7 @@ source:
- patches/0013-qtwebengine-missing_EVIOCGPROP.diff
- patches/0014-qtwebengine-HAVE_SENDMMSG.diff
- patches/google_breakpad_aarch_include.patch
- patches/0015-qtwebengine-fix-bison-gt-36.patch
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh nice.

@akrherz
Copy link

akrherz commented Dec 15, 2021

This is impressive and hard work you folks are putting in, but I am curious of the goals here given what has happened with the new qt-main repo. Could somebody tersely summarize what is happening ? Perhaps I am the only one curious :)

@hmaarrfk
Copy link
Contributor

Maybe this thread can help #192

I remember somebody announcing it on a thread somewhere, but I'm not sure where.

The goal here is mostly to migrate this until something else is fixed between qt and qt-main (and qt-webengine).

Ultimately, I think the qt package will just depend on qt-main and qt-webengine but I'm not sure when that will happen.

@hmaarrfk
Copy link
Contributor

@izahn how did you hack the aarch64 build again? The hack seems to require python 2 which is not in the mian channel for aarch64.

@izahn
Copy link
Contributor Author

izahn commented Dec 15, 2021

@izahn how did you hack the aarch64 build again? The hack seems to require python 2 which is not in the mian channel for aarch64.

Sorry which hack? I might have done something but I have an old brain and don't remember.

@izahn
Copy link
Contributor Author

izahn commented Dec 15, 2021

This is impressive and hard work you folks are putting in, but I am curious of the goals here given what has happened with the new qt-main repo. Could somebody tersely summarize what is happening ? Perhaps I am the only one curious :)

The goal is to keep qt in sync with the rest of the conda-forge ecosystem by merging the icu69 migration PR. Keeping conda-forge packages in sync with the global pinning is the mechanism by which packages are kept compatible with each other. Because the icu69 migration PR has been languishing qt is currently incompatible with the most recent tensorflow-base and everything else that has been migrated to icu 69

@akrherz
Copy link

akrherz commented Dec 15, 2021

The goal is to keep qt in sync with the rest of the conda-forge ecosystem

Thank you and totally agree as I have been thrashing about a lot within conda-forge due to the missing qt + icu69 combination :) This would be awesome to figure out!

@hmaarrfk
Copy link
Contributor

@izahn was it you that cared about aarch64? maybe it was somebody else. I'm trying to use the conda-forge channel for the hack instead of main:
51b4485

Lets see if that works.

@izahn
Copy link
Contributor Author

izahn commented Dec 15, 2021

@izahn was it you that cared about aarch64? maybe it was somebody else. I'm trying to use the conda-forge channel for the hack instead of main: 51b4485

That is horrifying :-)

@hmaarrfk
Copy link
Contributor

what makes you think we no longer need to merge build and host for qtwebengine?

@izahn
Copy link
Contributor Author

izahn commented Dec 15, 2021

what makes you think we no longer need to merge build and host for qtwebengine?

python build-locally.py completed the build without error.

@hmaarrfk
Copy link
Contributor

oh. very cool!

@hmaarrfk
Copy link
Contributor

Do we have time to try removing the openssl hack? I feel like openssl is already installed in the host environment....

@izahn
Copy link
Contributor Author

izahn commented Dec 15, 2021

Do we have time to try removing the openssl hack? I feel like openssl is already installed in the host environment....

My motivation for improvements here is limited because https://github.com/conda-forge/qt-main-feedstock will soon replace it if all goes well. I think we should just get the icu migration out the door and call it a day.

@hmaarrfk
Copy link
Contributor

I guess you should at least include the fix for finding python-2 and openssl from conda-forge instead of main. Using mamba will help the solve time a bit too.

@izahn
Copy link
Contributor Author

izahn commented Dec 15, 2021

I feel optimistic that what we have here works and is good enough. I'm building linux_64_ now, any volunteers to build the others? We need

  • linux_aarch64_
  • osx_64_
  • win_64_

@hmaarrfk
Copy link
Contributor

hmaarrfk commented Jan 1, 2022

i don't think I'm against going to gcc 11.

@izahn
Copy link
Contributor Author

izahn commented Jan 2, 2022

It seems like indeed for libgcc=9.3 and icu=69 the environment is impossible to solve. Is there any objection in pinning the compilers version to 11? In this case I can solve locally (without the additional nspr/sqlite pins).

@izahn - could you please re-invite me to your fork?

@Tobias-Fischer I just sent the invite again, sorry for the delay. Happy new year!

@Tobias-Fischer
Copy link
Contributor

Okay, I got the PR to build on aarch. At the moment the tests fail because some system requirements (libGL etc) are not installed; I asked Isuru to install them and will run the build again once that's done.

To get the PR to build, I needed to tweak some bits:

@izahn
Copy link
Contributor Author

izahn commented Jan 16, 2022

Has there been any movement here @Tobias-Fischer @hmaarrfk ? I think we just need to build and upload right?

@Tobias-Fischer
Copy link
Contributor

Hi @isuruf - sorry to ping you. Could you please install the libGL system dependencies on the aarch server so I can build again with passing tests?

Thanks!

@isuruf
Copy link
Member

isuruf commented Jan 16, 2022

Done

@Tobias-Fischer
Copy link
Contributor

Thanks - I triggered the aarch build.

@pkgw
Copy link
Contributor

pkgw commented Jan 17, 2022

I just want to say: huge thanks to everyone working hard on these builds! The frustrating thing about this kind of work is that the better job you do, the less that the rest of the world even gets to appreciate how challenging it is ...

@@ -63,7 +63,8 @@ rm -rf $PREFIX/bin/protoc
# Then find the .gn or .gni files that these ninja files were created from and figure out wtf is going on.

# qtwebengine needs python 2
conda create -y --prefix "${SRC_DIR}/python2_hack" -c https://repo.continuum.io/pkgs/main --no-deps python=2
# conda create -y --prefix "${SRC_DIR}/python2_hack" -c https://repo.continuum.io/pkgs/main --no-deps python=2
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Its probably not worth rebuilding with this line removed, but maybe we can remember to remove it in the future.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's already commented out, isn't it?

@Tobias-Fischer
Copy link
Contributor

I think we have all builds now. Next step is someone from core to look at the logs and upload the packages to the conda-forge channel?

@hmaarrfk
Copy link
Contributor

@conda-forge/core could you please upload the packages

@izahn
Copy link
Contributor Author

izahn commented Feb 7, 2022

@Tobias-Fischer I don't understand why but mamba can't seem to find the windows build:

CONDA_SUBDIR=win-64 mamba create -n test qt=5.12.9=h556501e_5 -q --dry-run
Encountered problems while solving:
  - nothing provides requested qt ==5.12.9 h556501e_5

And mamba wants to install the old one instead:

CONDA_SUBDIR=win-64 mamba create -n test qt -q --dry-run
  Package                 Version  Build               Channel                  Size
──────────────────────────────────────────────────────────────────────────────────────
  Install:
──────────────────────────────────────────────────────────────────────────────────────

  + ca-certificates     2021.10.8  h5b45459_0          conda-forge/win-64     176 KB
  + icu                      68.2  h0e60522_0          conda-forge/win-64      16 MB
  + jpeg                       9e  h8ffe710_0          conda-forge/win-64     373 KB
  + libclang               11.1.0  default_h5c34c98_1  conda-forge/win-64      21 MB
  + libpng                 1.6.37  h1d00b33_2          conda-forge/win-64     724 KB
  + libzlib                1.2.11  h8ffe710_1013       conda-forge/win-64      63 KB
  + openssl                1.1.1l  h8ffe710_0          conda-forge/win-64       6 MB
  + qt                     5.12.9  h5909a2a_4          conda-forge/win-64     106 MB
  + sqlite                 3.37.0  h8ffe710_0          conda-forge/win-64       1 MB
  + ucrt             10.0.20348.0  h57928b3_0          conda-forge/win-64       1 MB
  + vc                       14.2  hb210afc_6          conda-forge/win-64      13 KB
  + vs2015_runtime    14.29.30037  h902a5da_6          conda-forge/win-64       1 MB
  + zlib                   1.2.11  h8ffe710_1013       conda-forge/win-64     106 KB

Any idea what is going wrong here?

@izahn
Copy link
Contributor Author

izahn commented Feb 7, 2022

I'm especially confused because https://anaconda.org/conda-forge/qt/5.12.9/download/win-64/qt-5.12.9-h556501e_5.tar.bz2 exists, but somehow mamba doesn't see it.

@jakirkham
Copy link
Member

Probably a sync issue. Working with Anaconda to resolve

@isuruf
Copy link
Member

isuruf commented Feb 7, 2022

@izahn, please open issues in the future instead of commenting on PRs already merged.

conda/infrastructure#514

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants