Closed coatless closed 6 years ago
Well, but autoconf is not a library - it's in fact a standard build tool, the recipes are only for library dependencies of packages.
That said, the error you see is because you have macOS with SIP (system integrity protection) enabled, so it won't allow you to change permissions on some directories. You can check, but I think it is benign because tar will untar and set permissions on files it can touch.
@s-u agreed. I suppose a better question is: What kind of developer environment are the recipes being built on?
Can I assume that the environment is fully outfitted with the GNU suite of tools? e.g. autoconf
, automake
, and libtool
?
RE: SIP. Thanks, I've disabled that on the VM.
@s-u
I'm trying to add a recipe for
autoconf
. The main question I have relates to the underlying system configuration.Replicating the Build System
To use the recipe's
make
file, we must first:/usr/local
?I bring this up because I'm running into permission issues:
This indicates that the problem relates
Makefile
directive of:Recipe
I've implemented the recipe as:
autoconf
inrecipes/
I'm building it on macOS 10.14 (Mojave) with:
This is generating the following
make
entry inbuild
'sMakefile
: