Closed regro-cf-autotick-bot closed 5 years ago
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.
Now the build completed on linux, but there is a failure on import of PyQt5.QtOpenGL for the gcc7 cases. from the test section of the log
ModuleNotFoundError: No module named 'PyQt5.QtOpenGL'
and earlier during the build:
Checking to see if the QtOpenGL module should be built...
/home/conda/feedstock_root/build_artifacts/pyqt_1542329934029/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeh/bin/qmake -o cfgtest_QtOpenGL.mk cfgtest_QtOpenGL.pro
Project ERROR: Unknown module(s) in QT: opengl
@conda-forge-admin, please rerender
Hi! This is the friendly automated conda-forge-webservice.
I tried to re-render for you, but it looks like there was nothing to do.
can any maintainer of this feedstock restart the failing builds? qt5.6 from conda-forge is now build with opengl enabled.
@looooo , there is now an OpenGL-related linking error during the linux gcc builds:
x86_64-conda_cos6-linux-gnu-c++ -Wl,-O2 -Wl,--sort-common -Wl,--as-needed -Wl,-z,relro -Wl,-z,now -Wl,--disable-new-dtags -Wl,-rpath,$PREFIX/lib -L$PREFIX/lib -Wl,-rpath-link,$PREFIX/lib -Wl,-rpath-link,/home/conda/feedstock_root/build_artifacts/qt_1542565944096/_build_env/x86_64-conda_cos6-linux-gnu/sysroot -Wl,-O1 -Wl,-rpath,$PREFIX/lib -o cfgtest_QtGui cfgtest_QtGui.o -L$PREFIX/lib -lQt5Gui -lQt5Core -lGL -lpthread
$BUILD_PREFIX/bin/../lib/gcc/x86_64-conda_cos6-linux-gnu/7.3.0/../../../../x86_64-conda_cos6-linux-gnu/bin/ld: cannot find -lGL
collect2: error: ld returned 1 exit status
make: *** [cfgtest_QtGui] Error 1
Do we need to add some or all of these CDT packages under build as in the Qt recipe?: https://github.com/conda-forge/qt-feedstock/blob/a9c82fb1d90830f8b648ee4186ef66db5056e852/recipe/meta.yaml#L35-L40
What does CDT stand for anyway? I am not familiar with the acronym.
What does CDT stand for anyway? I am not familiar with the acronym.
Yes I am also wondering about the naming for some time. You can find a little bit of information here
Do we need to add some or all of these CDT packages under host as in the Qt recipe?:
For another qt-dependent feedstock I added quite a few of these cdt's to make it work. So yes I think these should be added. But maybe someone more familiar with cdt's can help here. @mingwandroid
We may want to think about something like build_exports whereby qt adds build dependencies for CDT packages. Thoughts welcome!
A made a PR including the CDT packages (see #42) and it built successfully.
Ok, thanks! Closing this one then.
It is likely this feedstock needs to be rebuilt. Notes and instructions for merging this PR:
Please note that if you close this PR we presume that the feedstock has been rebuilt, so if you are going to perform the rebuild yourself don't close this PR until the your rebuild has been merged.
This package has the following downstream children: enaml glue-core glue-vispy-viewers hyperspy-gui-traitsui instaseis And potentially more.
If this PR was opened in error or needs to be updated please add the
bot-rerun
label to this PR. The bot will close this PR and schedule another one.This PR was created by the cf-regro-autotick-bot. The cf-regro-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. If you would like a local version of this bot, you might consider using rever. Rever is a tool for automating software releases and forms the backbone of the bot's conda-forge PRing capability. Rever is both conda (
conda install -c conda-forge rever
) and pip (pip install re-ver
) installable. Finally, feel free to drop us a line if there are any issues!