Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 07:49
    isuruf edited #932
  • Dec 03 23:56
    ocefpaf commented #938
  • Dec 03 23:45
    jakirkham commented #938
  • Dec 03 20:30
    jjhelmus commented #938
  • Dec 03 19:55
    scopatz commented #938
  • Dec 03 19:32
    ocefpaf labeled #938
  • Dec 03 19:30
    ocefpaf opened #938
  • Dec 03 07:16
    h-vetinari commented #902
  • Dec 02 23:33
    vtbassmatt commented #902
  • Dec 02 20:54
    scopatz closed #871
  • Dec 02 17:30
    h-vetinari commented #902
  • Nov 30 05:34

    conda-forge-coordinator on master

    Re-ran make.py. [ci skip] (compare)

  • Nov 30 05:34
    jakirkham commented #937
  • Nov 30 05:34
    jakirkham commented #937
  • Nov 30 05:33
    jakirkham commented #937
  • Nov 30 05:30

    jakirkham on master

    DOC added docs for pinging teams Merge pull request #937 from be… (compare)

  • Nov 30 05:30
    jakirkham closed #937
  • Nov 30 05:02
    beckermr opened #937
  • Nov 28 19:55

    conda-forge-coordinator on master

    Re-ran make.py. [ci skip] (compare)

  • Nov 28 19:51
    scopatz commented #935
Ray Donnelly
@mingwandroid
If you want to propose your own way go ahead, if you want to discuss then https://github.com/conda-forge/cmake-feedstock/issues would probably be the place for that.
Ray Donnelly
@mingwandroid
We could even provide mutliple methods and pick the "best" on a per-recipe basis.
there's Preload, specifically named bash array env vars to pass to cmake, toolchain files and changes to cmake itself to consider as options.
deepali-c
@deepali-c
I am trying to write conda recipe for https://github.com/pytorch/fairseq. I see the following error:
RuntimeError: Setuptools downloading is disabled in conda build. Be sure to add all dependencies in the meta.yaml url=https://pypi.org/simple/pycparser/
Although I have pycparser added as dependency in the host section. I have also tried putting it in build section but it still fails.
Uwe L. Korn
@xhochy
Azure Pipelines are not starting anymore since ~30min on staged-recipes, https://status.dev.azure.com/ says no issue. Anyone has an idea?
Devon Ryan
@dpryan79
Looks like azure processes on staged-recipes have started again
Uwe L. Korn
@xhochy
I still only see Waiting for an available agent on conda-forge/staged-recipes#9597
Duncan Macleod
@duncanmmacleod

hi all, I’m having trouble building a package on windows using meson. I get

'meson' is not recognized as an internal or external command,
operable program or batch file.
The system cannot find the path specified.

when I specify meson in the build section. Is there a special trick to getting windows to recognise a python-script? See conda-forge/gst-orc-feedstock#3

@xhochy, I’m also seeing that across a number of feedstocks
Uwe L. Korn
@xhochy
Finally, it run for my PR.
Duncan Macleod
@duncanmmacleod
can someone from core please rerun the azure pipeline for celery-eternal? thanks
Uwe L. Korn
@xhochy
@duncanmmacleod when you're a feedstock maintainer you can do that yourself.
Either via Github's Checks tab or https://conda-forge.org/docs/maintainer/infrastructure.html#restarting-builds
Duncan Macleod
@duncanmmacleod
since this is a master branch build, where should I post the please restart CI command?
Chris Burr
@chrisburr
You can't but you can click on commits from the root of the repository
If you then click on the red cross followed by details
You should get to a page with a restart button
Uwe L. Korn
@xhochy
rerun ci
Not the best GIF you can make but I hope that helps
Isuru Fernando
@isuruf
@xhochy, looks great. Wanna send a PR to conda-forge docs?
Uwe L. Korn
@xhochy
@isuruf yes, but will do it new recording later that looks less clumsy.
Christopher J. Wright
@CJ-Wright
conda-forge in gifs would be a great docs page
Isuru Fernando
@isuruf
Thanks @xhochy
Duncan Macleod
@duncanmmacleod
ok, my build is rerunning, thanks @chrisburr, @xhochy!
Julian Rüth
@saraedum
Does someone know what ld: library not found for -lcrt1.10.6.o on macOS is about? (trying to build valgrind on macOS)
https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=73695&view=logs&jobId=ce7cbaa7-582c-5570-40f4-267b3d85fc9f&taskId=4a56039b-7269-50ae-de7a-538e91e6de06&lineStart=655&lineEnd=656&colStart=1&colEnd=1
Isuru Fernando
@isuruf
@saraedum, build system is setting -mmacosx-version-min=10.6
Duncan Macleod
@duncanmmacleod
does anyone know is conda-api is still maintained, or whether there is something else to use to create/modify environments from python?
Julian Rüth
@saraedum
@isuruf it seems to be setting it to -mmacosx-version-min=10.9 actually. So is it wrong that the build is searching for 10.6 here?
Isuru Fernando
@isuruf
@saraedum,
x86_64-apple-darwin13.4.0-clang -arch x86_64 -O2 -g -Wall -Wmissing-prototypes -Wshadow -Wpointer-arith -Wstrict-prototypes -Wmissing-declarations -Wcast-align -Wcast-qual -Wwrite-strings -Wempty-body -Wformat -Wformat-security -Wignored-qualifiers -Wenum-conversion -finline-functions -fno-stack-protector -fno-strict-aliasing -fno-builtin -Wno-cast-align -Wno-self-assign -Wno-tautological-compare -mmacosx-version-min=10.6 -march=core2 -mtune=haswell -mssse3 -ftree-vectorize -fPIC -fPIE -O2 -pipe -I$PREFIX/include -fdebug-prefix-map=$SRC_DIR=/usr/local/src/conda/valgrind-3.15.0 -fdebug-prefix-map=$PREFIX=/usr/local/src/conda-prefix -undefined dynamic_lookup -arch x86_64 -O2 -g -Wall -Wmissing-prototypes -Wshadow -Wpointer-arith -Wstrict-prototypes -Wmissing-declarations -Wcast-align -Wcast-qual -Wwrite-strings -Wempty-body -Wformat -Wformat-security -Wignored-qualifiers -Wenum-conversion -finline-functions -fno-stack-protector -fno-strict-aliasing -fno-builtin -Wno-cast-align -Wno-self-assign -Wno-tautological-compare -mmacosx-version-min=10.6 -Wl,-pie -Wl,-headerpad_max_install_names -Wl,-dead_strip_dylibs -Wl,-rpath,$PREFIX/lib -L$PREFIX/lib -o valgrind valgrind-launcher-darwin.o valgrind-m_debuglog.o
Above is what I see in azure
Julian Rüth
@saraedum
@isuruf You're right of course. Some lines say 10.9 and then 10.6 later in the same line. That confused me. So should we build with 10.9 actually?
Isuru Fernando
@isuruf
@saraedum, you should build with whatever MACOSX_DEPLOYMENT_TARGET variable tells you
It's 10.9 globally in conda-forge
Julian Rüth
@saraedum
That's 10.9 ok thanks. :)
Anthony Scopatz
@scopatz
@mingwandroid etc, are there any docs for how to build a CDT package?
Ray Donnelly
@mingwandroid
Not sure, but they are just normal recipes with no real deps.
jayfurmanek
@jayfurmanek

@hmaarrfk did a good job with some recent ones on aarch64 here:
conda-forge/staged-recipes#9028

It clubs the -devel versions into the same recipe

Anthony Scopatz
@scopatz
I think I am confused about how they work then
Ray Donnelly
@mingwandroid
Hmm, I'd rather they remained autogenerated personally.
jayfurmanek
@jayfurmanek
I followed that for these ppc64le ones:
conda-forge/staged-recipes#9395 (merged)
conda-forge/staged-recipes#9583 (needs a review)
Anthony Scopatz
@scopatz
Yeah, how do I autogenerate them, is my question
Ray Donnelly
@mingwandroid
conda skeleton rpm --distro=centos6 --arch=x86_64 libGL
Anthony Scopatz
@scopatz
Ahh OK
Ray Donnelly
@mingwandroid
`conda skeleton rpm --distro=centos7 --arch=ppc64le libGL
jayfurmanek
@jayfurmanek
will that work for non-x86?
Ray Donnelly
@mingwandroid
the distros are a bit hard-coded at the top of cran.py in conda-build
still, it seems to work ok
jayfurmanek
@jayfurmanek
well thats good
Ray Donnelly
@mingwandroid
you can even build them on Windows (though I'm checking that still works now)
Isuru Fernando
@isuruf
@mingwandroid, they don't on windows