> Are there any differences between the way you compile > GNUstep Base, and the way the package is built? e.g. what flags do you > pass to configure?
I compiled the stable GNUstep Startup by using the InstallGNUstep script (installation to home directory), and the Subversion checkout by calling compile-all with a --prefix parameter, having edited it so as to call GNUstep make's configure script with --with-config-file=<whatever>. I assume, therefore, that my configuration is pretty much whatever the configure scripts default to. > Do you have libffi-dev installed? With GNUstep Base 1.16.3, it will use > libffi if it can find it, even if you say --enable-ffcall, unless you > specifically say --disable-libffi. I had noticed that as well, consequently done a make distclean and removed libffi-dev before building anew. > Anyways, this may all be moot, since you say it doesn't happen with > libgnustep-base1.16-libffi. After lenny is released, we will be > defaulting to using libffi, since upstream prefers it now. The reason > we haven't switched yet is because we wouldn't be able to sufficiently > test such a big change before the release of lenny O.K. The program I'm working on will possibly make direct use of libffi instead of relying on NSInvocation eventually, anyway. I guess I'll just have to tell my users to install libgnustep-base1.16-libffi for now. (Of course, it'd be nice for it to work out of the box.) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
