-
Notifications
You must be signed in to change notification settings - Fork 129
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
can't build on mac with command line tools #124
Comments
I wonder if using the brew version of autogen, autoconf, m4 etc instead of building them all from source would help here. I installed autogen, libtool, autoconf, m4, e2fsprogs via brew and ran the following: export PKG_CONFIG_PATH="/opt/homebrew/opt/e2fsprogs/lib/pkgconfig:$PKG_CONFIG_PATH"
./autogen.sh
CFLAGS="-idirafter/opt/homebrew/opt/e2fsprogs/include -idirafter/usr/local/include/osxfuse/" LDFLAGS="-L/opt/homebrew/Cellar/e2fsprogs/1.46.4/lib" ./configure
make Again, not sure if this only worked because I had the full xcode, but at least I only had to build fuse-ext2 and not everything else. |
@jswitzer Tested out on macOS 12.3 Beta (21E5212f). With no full Xcode installed. Pretty smooth when running your commands. But had trouble with In my own case, I met this output again. Even with full Xcode installed. Workaround:
|
I'm also not a fan of this enormous Xcode and trying not to use it at all, and until now doing well. Here, xcode is basically used to generate the Preferences pane. If you can live without it, just deactivate the build of the Make sure to have a clean directory before re-building by running PS: I didn't find an easy way to transform and xcodeproj into a Makefile-based project... |
Building on macosx fails if command line tools only are installed. All modules apart from this fuse-ext2 build and install successfully.
The error logged is:
I don't know how the other modules build using just the command line tools, but downloading and installing the bloatware of Xcode (11GB) is unreasonable just for this final part of the install.
The text was updated successfully, but these errors were encountered: