Alexander Hansen wrote: > > Luke Stras wrote: [] >> There's nothing obviously wrong in the log -- at least, not that I >> could spot. If someone else notices what's going on, I will be very >> grateful.
There are lots of things wrong. For example > checking whether we are using the GNU C compiler... no > checking whether gcc accepts -g... no ... > checking if libtool supports shared libraries... no > checking whether to build shared libraries... no All of these should be yes. The last one eventually leads to the mv failure, because no dylibs are built. > > I get an identical failure. Unfortunately, since this is a cmake-based > build system, it's not very verbose in its output. > > I built this same version at one point, so something must have changed > on my system that causes it not to build. I'll see if I can come up > with anything obvious. Try downgrading autoconf to 2.63. It will then build. Autoconf-2.64 creates a configure script that does not work. This is how far I got; I don't know what is really wrong with autoconf this time. -- Martin ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Fink-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fink-users
