“M. Edward (Ed) Borasky” [email protected] writes:
then do the “make install”. [ … ]
Yeah … that’s the way it’s supposed to work – check first, then
install. But I usually make a new home in /opt for testing stuff anyhow,
rather than letting it default into /usr/local. And I have had instances
where things broke in “make check” that didn’t break after “make
install” because of some path issues. I’ll take this as encouragement to
hunt them down and document them.
Yes, I see how that approach can be helpful. I just usually do the
following: if “make check” fails, don’t even try the install. I’ve
never seen a case where the check succeeded and the software blew up
after installation … although I know that this certainly could happen,
and your procedure would catch this problem.
In any case, this time I got the same error during the “make check” both
before and after the installation.