You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Compiling libfec on Mac OS 10.11.3 (El Capitan) keeps failing by saying error: unknown target CPU 'i386' when running make after ./configure.
I tried to fix that by manually specifing the build target via --build=x86_64 (as I'm running 64-bit architecture and i686 fails with a similar error) when running configure (e.g. ./configure --build=x86_64), but this leads to an error when linking stating ld: unknown option: -soname=libfec.so.
By looking at the makefile there seems to be a target for Mac OS (libfec.dylib in line 98), it just does not get triggered.
Passing a full tuple like x86_64-apple-darwin to the configure script (e.g. ./configure --build=x86_64-apple-darwin) successfully builds libfec on my machine.
I hope this helps other users on Mac OS X as this behaviour is somewhat strange. Maybe the configure script is somehow wrong...
The text was updated successfully, but these errors were encountered:
Compiling libfec on Mac OS 10.11.3 (El Capitan) keeps failing by saying
error: unknown target CPU 'i386'
when runningmake
after./configure
.I tried to fix that by manually specifing the build target via
--build=x86_64
(as I'm running 64-bit architecture and i686 fails with a similar error) when running configure (e.g../configure --build=x86_64
), but this leads to an error when linking statingld: unknown option: -soname=libfec.so
.By looking at the
makefile
there seems to be a target for Mac OS (libfec.dylib
in line 98), it just does not get triggered.Passing a full tuple like
x86_64-apple-darwin
to theconfigure
script (e.g../configure --build=x86_64-apple-darwin
) successfully builds libfec on my machine.I hope this helps other users on Mac OS X as this behaviour is somewhat strange. Maybe the configure script is somehow wrong...
The text was updated successfully, but these errors were encountered: