lapple:~ root# port installed name:guile The following ports are currently installed: guile @2.0.14_1 guile @2.2.2_0 (active) guile18 @1.8.8_6 (active)
lapple:ports root# port provides /opt/local/bin/guile;ls -l /opt/local/bin/guile /opt/local/bin/guile is provided by: guile -rwxr-xr-x 1 root admin 8904 May 3 16:27 /opt/local/bin/guile So it looks like there was a guile update to 2.2.2_0 (based on the date of the file), which autogen wasn't ready for. The config log shows it trying to fall back to guile18 when 2.0 isn't found, but isn't getting that right either.
config.log-autogen.txt.gz
Description: GNU Zip compressed data
> On May 3, 2017, at 21:52, Ryan Schmidt <[email protected]> wrote: > > >> On May 3, 2017, at 19:15, Richard L. Hamilton <[email protected]> wrote: >> >> autogen fails rev-upgrade after installing from binaries (!) (update: for >> some reason, later today it no longer attempts to install from binaries). >> It then fails the build: >> >> :info:configure awk: can't open file >> /opt/local/include/guile18/libguile/version.h >> >> except of course that the file isn't there: > > The file not being there would be an excellent explanation for why it cannot > be opened. :) > > Which guile ports are installed? > > port installed name:guile > > autogen has a dependency on the guile port, which is at version 2.0.14, and > although the autogen configure process thinks it's found a guile > installation, it shows that it found version 1.8, which shouldn't happen and > is not what happens on my system. > >> :info:configure configure: checking for guile 2.0 >> :info:configure configure: checking for guile 1.8 >> :info:configure configure: found guile 1.8 > > If you attach the config.log, that might help us figure out what's going on. > > >
smime.p7s
Description: S/MIME cryptographic signature
