Thank you, that allows configure to complete w/o error. Next up, libtool
/bin/sh "/scm/oss/subversion/libtool" --tag=CC --silent --mode=compile gcc
-std=c90 -DDARWIN -DSIGPROCMASK_SETS_THREAD_MASK -DDARWIN_10
-Werror=unknown-warning-option -g -O2 -g -O2 -I./subversion/include
-I/usr/local/opt/openssl/include -I/usr/local/Cellar/lz4/1.8.0/include -o
subversion/libsvn_delta/branch.lo -c subversion/libsvn_delta/branch.c
/bin/sh: /scm/oss/subversion/libtool: No such file or directory
make: *** [subversion/libsvn_delta/branch.lo] Error 127
So I can find a /usr/bin/libtool and one in
but both are binary, and the failing make step is an attempt to hand a
shell script to /bin/sh to execute. This feels like a wrapper-like thing,
and I've googled a little, but can't see anything clear like "copy this
script to folder/libtool".
On Sat, Oct 28, 2017 at 8:07 AM, Troy Curtis Jr <troycurtisjr_at_gmail.com>
> On Sat, Oct 28, 2017, 7:02 AM Paul Hammant <paul_at_hammant.org> wrote:
>> OK, so I can get so far ...
>> svn co http://svn.apache.org/repos/asf/subversion/trunk subversion
>> cd subversion
>> brew install libtool apr
>> cp /usr/local/Cellar/libtool/2.4.6_1/share/libtool/build-aux/config.sub
>> ./configure --build=x86_64 --prefix=/usr/local --with-openssl --with-ssl
>> --with-zlib --with-apr=/usr/local/Cellar/apr/1.6.3/
>> (Note that I had to config.sub in my Homebrew folders and copy it into
>> the build/ directory - barfs without it)
>> .. but it barfs after during the configure step:
>> checking how to use output level for Ruby bindings tests... normal
>> checking for ctypesgen.py... none
>> checking stdbool.h usability... yes
>> checking stdbool.h presence... yes
>> checking for stdbool.h... yes
>> checking for stdint.h... (cached) yes
>> configure: creating ./config.status
>> config.status: creating Makefile
>> config.status: error: cannot find input file: `subversion/libsvn_*/*.
>> I can't see any files ending in .pc.in in any subversion/libsvn_
>> prefixed folder (in the checkout). Therefore I'm not surprised the
>> configure step fails when it's looking for those files.
>> Any advice would be appreciated.
>> - Paul
> Since you are building from a checkout and not from a dist tarball, you
> need to run "autogen.sh" before configure.
Paul Hammant DevOps <https://devops.paulhammant.com> Let me give you a step
by step plan to get out of the hell of ClearCase and crazy branching models
and into the world of high-throughput CD on DevOps foundations.
Received on 2017-10-28 14:24:33 CEST