Installing GD on 10.3.9 Server

N

nicki

Registered
Hi- I'm installing gd on a 10.3.9 server and have ironed out all the problems in installing the required components and I've configured gd successfully, but it fails on make. The error is:
configure.ac:28: error: Autoconf version 2.58 or higher is required
But I have installed the 2.58 so I'm not sure why it keeps saying that. I used fink to install it. Do I need to somehow refresh it or force it to use the highest version?
I'm using the latest version of gd. The one previous didn't work. But maybe I should try the older one again.
Thanks,
Nicki
 
An update- I have installed autoconf 2.59 and 2.58 manually after using fink b/c when I asked it what version it was it says 2.57

It still says 2.57
/usr/bin/autoconf --version
autoconf (GNU Autoconf) 2.57

And my make still fails due to it not being 2.58 or higher.
 
More than likely you are installing a second copy of autoconf (original is in /usr/bin/autoconf) and the configure script is not finding it. When you do the 'make install' for Autoconf 2.58/2.59, what is the installation prefix??

/usr/local/bin/autoconf perhaps?
 
Well, I never get to the make install. I just do make and it fails. Maybe I should do it for the sake of finding this out?
 
ok, this is what i think we're looking for- it's in user/local/bin. so, how do i force it to use that one? should i try to force it to install to /usr/bin or try to force gd to use /usr/local? thanks so much
.....

Making install in bin
/bin/sh ../config/mkinstalldirs /usr/local/bin
/usr/bin/install -c autom4te /usr/local/bin/autom4te
/usr/bin/install -c autoconf /usr/local/bin/autoconf
/usr/bin/install -c autoheader /usr/local/bin/autoheader
/usr/bin/install -c autoreconf /usr/local/bin/autoreconf
/usr/bin/install -c ifnames /usr/local/bin/ifnames
/usr/bin/install -c autoscan /usr/local/bin/autoscan
/usr/bin/install -c autoupdate /usr/local/bin/autoupdate
 
Well, you can compile *AUTOCONF* by doing a 'configure --prefix=/usr/' - that will put the files into the current directory.

That's probably the easiest way. If you wish to have multiple versions of autoconf - then you'll have to either edit the autoconf template within the program you are compiling, or juggle symbolic links around. (there MAY be an autoconf environment variable - you'd have to check some man pages on that - I'm not 100% sure).

EDIT: do a "./configure --help | more" for a list of which switches are available for the package you are compiling.
 
So I tried running configure
./configure --prefix=/usr/bin --mandir=/usr/man1 --infodir=/usr/info
b/c the info dir was complaining too.

That worked and I installed gd. Success! Thanks to you.

However, my gd tests aren't acting exactly as I would expect them too. Have you ever run the tests or know anything about them? It's giving me a good error so I think I installed it ok, maybe I just need to change some things...

WWW:/Users/csserv/Desktop/gdbuild/gd-2.0.34 nhandy$ ./gdtest test/gdtest.png
Reference File has 5 Palette entries
%Initial Versions: OK
Bus error

When I run this, I have to sudo to get it to work....

WWW:/Users/csserv/Desktop/gdbuild/gd-2.0.34 nhandy$ ./gdtestft Zapfino.dfont

I feel like I shouldn't have to sudo to use the functions, you know? I think I'll just have to work the permissions a little.

But, it works and I'm psyched- thanks so much for your help!
 
Are you using GD to link against PHP? Or for another project?

I've had tests fail when everything else works - its usually because they update the source, change something, but forget to update the test to reflect the new change.

Bus error is a Mac error that bugs me a lot. Every other Unix variant I've used puts a more descriptive error... ie: "lp0: printer on fire?" :)

In any case - you shouldn't have to sudo to get that to work. You are simply compiling a program and linking it against a library. Its possible that the kernel has reserved certain calls for system instead of user - but I doubt it. If its really bugging you, you can recompile the test with the -g flag added to the GCC_FLAGS variable in the Makefile (or whatever its called) .. that'll compile debug symbols into the executable - then you can run the debugger (gdb) to find out what is causing it to crash.

See http://www.gnu.org/software/gdb/gdb.html for more info
 
You must log in or register to reply here.
Back
Top