On Thu, 01 Feb 2024 00:00:28 +0100,
Chun Tian (binghe) wrote:
>
> I think for Camm the only purposes of using MacPorts is to easily get
> GCC and various open source tools installed in his Catalina box. For
> examples, after a successful installation, a simple command like "sudo
> port install gcc13" will get GCC installed, so is "gmp" and "git", etc.
>
> Then, if GCL can be successfully built by the normal workflow (i.e.
> ./configure and make), then it's the job of MacPorts packager (Kirill)
> to update the Portfile for GCL. I think there's no need to involve Camm
> to the extra complexities of MacPorts including its long building paths.
>
Well,
It requries some dancing with environment variables and configure options.
On macOS 12 I can build it outside of MacPorts with script like that:
export CC='/usr/bin/clang'
export CFLAGS='-pipe -fno-pie
-isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk -arch x86_64
-Wno-implicit-function-declaration -g -O0'
export CPATH='/opt/local/include'
export CPPFLAGS='-I/opt/local/include
-isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk'
export LDFLAGS='-L/opt/local/lib -Wl,-headerpad_max_install_names -fno-pie
-Wl,-syslibroot,/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk -arch
x86_64'
export LIBRARY_PATH='/opt/local/lib'
export MACOSX_DEPLOYMENT_TARGET='12.0'
export SDKROOT='/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk'
./configure --prefix=/opt/local \
--disable-notify \
--disable-statsysbfd \
--enable-ansi \
--enable-custreloc \
--enable-emacsdir=/opt/local/share/emacs/site-lisp/gcl \
--enable-infodir=/opt/local/share/info \
--enable-readline \
--disable-gprof \
--without-x \
--disable-xgcl \
--host=x86_64-apple-darwin \
--build=x86_64-apple-darwin \
--target=x86_64-apple-darwin
make
not everything here is required, but it allows to build it with some degree of
sucess and some "ugly patches".
But I think you're right. The right way is install dependencies via MacPorts and
try to develop it outside.
--
wbr, Kirill
