Thanks Ralf Issue 24418 created. Happy to help where possible.
https://github.com/numpy/numpy/issues/24418 On Mon, Aug 14, 2023 at 7:59 AM Ralf Gommers <ralf.gomm...@gmail.com> wrote: > > > On Mon, Aug 14, 2023 at 1:16 PM Doug Turnbull <softwared...@gmail.com> > wrote: > >> Hey all >> >> First time trying to build / test numpy main branch, so I'm probably >> doing something wrong. >> >> I brought down main and everything built on the first try. However I'm >> getting test failures related to meson. >> >> Specifically the tests in "python -m pytest >> numpy/core/tests/test_mem_policy.py" all give errors. The errors seem >> related to meson and visual studio: >> >> >> >> >> *> Visual Studio environment is needed to run Ninja. It is recommended to >> use Meson wrapper:/Users/douglas.turnbull/ws/numpy/venv/bin/meson compile >> -C .> ERROR: Could not detect Ninja v1.8.2 or newer* >> >> This is an m1 mac with Python 3.11.4. Scrolling up in meson_log.txt I see >> a linker error: >> >> *> ld: symbol(s) not found for architecture arm64* >> >> Included system information >> >> Project version: undefined >> C compiler for the host machine: cc (clang 14.0.3 "Apple clang version >> 14.0.3 (clang-1403.0.22.14.1)") >> C linker for the host machine: cc ld64 857.1 >> Host machine cpu family: aarch64 >> Host machine cpu: aarch64 >> >> Snippet from meson log >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> *Detecting Apple linker via: `cc -Wl,-v` -> 1stderr:@(#)PROGRAM:ld >> PROJECT:ld64-857.1BUILD 23:13:29 May 7 2023configured to support archs: >> armv6 armv7 armv7s arm64 arm64e arm64_32 i386 x86_64 x86_64h armv6m armv7k >> armv7m armv7emLibrary search paths: . /opt/homebrew/lib /usr/local/lib >> /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/libFramework search >> paths: >> /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/Undefined >> symbols for architecture arm64: "_main", referenced from: implicit >> entry/start for main executableld: symbol(s) not found for architecture >> arm64clang: error: linker command failed with exit code 1 (use -v to see >> invocation)* >> >> Seeing a note recommending gcc in the docs, I'm going to try using gcc >> rather than clang as next steps. But I wanted to share this issue if it is >> indeed one. >> > > Hi Doug, thanks for the report. Clang should work just fine, and is the > default on macOS. I'm not sure what's going on there, but I can reproduce > the issue by running `cc -Wl,-v` outside of my regular development envs. > Would you mind opening an issue at https://github.com/numpy/numpy/issues > with more details on how you installed your compilers and Python, and are > activating your dev env before running the problematic `pytest` command? > > Cheers, > Ralf > > > >> >> -Doug >> _______________________________________________ >> NumPy-Discussion mailing list -- numpy-discussion@python.org >> To unsubscribe send an email to numpy-discussion-le...@python.org >> https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ >> Member address: ralf.gomm...@googlemail.com >> > _______________________________________________ > NumPy-Discussion mailing list -- numpy-discussion@python.org > To unsubscribe send an email to numpy-discussion-le...@python.org > https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ > Member address: softwared...@gmail.com >
_______________________________________________ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-le...@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: arch...@mail-archive.com
