-
Notifications
You must be signed in to change notification settings - Fork 44
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
Doesn't build on M1/M2 Macs #120
Comments
Ok, fixed the libffi problem using this link: libffi/libffi#571 adding the parameter "--build=aarch64-apple-darwin20.0.0" to CONFIGURE_CMD on line 556 of the build script allows libffi to build correctly. Apparently it detects the architecture incorrectly in libffi's configure script and this forces it. I'm going to just go ahead and document my modifications to the build script as I go along trying to get this to work, hopefully can come up with a script that works on apple silicon eventually. |
Thanks for following up and posting your work on this, it's very helpful. |
+1 I’m really interested in compiling gnuradio for Apple silicon. |
I've modified the script in order to compile GNU Radio 3.10.4.0 using the macos built-in python version (v3.9).
Do you have ideas for solving? Ivan |
You're missing the meson package. Most likely it's just not installed in such a way as to be accessible to that version of python. |
Uhm, probably your right...
How can I modify the meson install lines to make it visible to glib? Sould I modify function Ivan |
I'm not at a computer right now, but even though meson is installed it's apparently not available to the python version you're using. The basic gist is that you need to run python pip3 -m install meson under the version of python you are using. In other words you're going to need to run that command, but using the full path of the python version that is being used to build this. Python on Mac is such a pain to work with... |
I'm installing meson through the script itself.
|
The release doesn't run on M1 Macs, it seems to start x-windows and then just quits, doesn't give any other indication of what's wrong. So trying to build using these scripts (after fixing the boost download issue and the lib tool download issue and manually installing python 3.9 and adjusting the build script to point to that install), it runs into trouble compiling ffi -- seems to be an arm assembly issue perhaps. This one is a bit over my head. Maybe someone has an idea on how to resolve it? I've attached my modified build script in case I made a mistake there that's causing the issue.
build.sh.txt
partial compile output:
libtool: compile: clang -mmacosx-version-min=10.7 -DHAVE_CONFIG_H -I. -I.. -I. -I../include -Iinclude -I../src -I/Applications/GNURadio.app/Contents/MacOS/usr/include -I/opt/X11/include -I/Applications/GNURadio.app/Contents/MacOS/usr/include -I/opt/X11/include -Wall -fexceptions -MT src/arm/ffi.lo -MD -MP -MF src/arm/.deps/ffi.Tpo -c ../src/arm/ffi.c -fno-common -DPIC -o src/arm/.libs/ffi.o
../src/arm/sysv.S:64:1: error: unexpected token at start of statement
@ This selects the minimum architecture level required.
^
../src/arm/sysv.S:112:1: error: unknown directive
.syntax unified
^
../src/arm/sysv.S:152:2: error: unexpected token at start of statement
@ r0: ffi_prep_args
^
../src/arm/sysv.S:153:2: error: unexpected token at start of statement
@ r1: &ecif
^
../src/arm/sysv.S:154:2: error: unexpected token at start of statement
@ r2: cif->bytes
^
../src/arm/sysv.S:155:2: error: unexpected token at start of statement
@ r3: fig->flags
^
The text was updated successfully, but these errors were encountered: