Yes, it is pretty safe to run ./configure more than once.  The 1st time, it
create the config.cache and so on.  The 2nd time, it use the config.cache
and other stuffs instead of starting from scratch.  To redo everything from
scratch.  I believe one of those config.* files need to be removed so you
can start again from scratch, not sure which files that need to be delete.
But don't delete the original file, config or configure.

Second of all, the list you provided to me.  I noticed it is a link file,
not a source file because of hte L before rwx.  The first three links that
point to the 4th file.  The fouth file is a link that aren't pointed to
anything, so it meant it is a link without a file.  That may be why you got
the error.


"Tom Rogers" <[EMAIL PROTECTED]> wrote in message
> Hi,
> Thursday, July 25, 2002, 1:41:25 AM, you wrote:
> CG> Well my RedHat system got hosed, so I reinstalled everything. I'm back
> CG> installing PHP now, and I'm wondering if it's safe for me to run
> CG> multiple times. Here's the situation:
> CG> I want to compile with gd support, and pdflib, and a bunch of other
> CG> Instead of running a whole huge 5 line ./configure, can I run one at a
> CG> to make sure they all work, then run the whole thing?
> CG> Also, just noticed this: I have gd installed, and in
/usr/lib, so I
> CG> tried ./configure --with-apxs --with-gd=/usr/lib/ (also tried without
> CG> trailing /), but it gives: configure: error: Unable to find
> CG> anywhere under /usr/lib/
> CG> What gives?
> CG> (in this ouptut, the stuff that's not important is cut out -- dates,
> CG> [root@saturn php-4.2.2]# ls -l /usr/lib/libgd.*
> CG> lrwxrwxrwx S /usr/lib/ ->
> CG> lrwxrwxrwx S /usr/lib/ ->
> CG> lrwxrwxrwx S /usr/lib/ ->
> CG> lrwxrwxrwx S /usr/lib/
> CG> [root@saturn php-4.2.2]#
> CG> TIA,
> CG> c.
> CG> --
> CG> PHP General Mailing List (
> CG> To unsubscribe, visit:
> it may be looking for libgd.a in the gd directory do a make libgd.a
> then copy it to /usr/lib
> --
> Best regards,
> Tom

PHP General Mailing List (
To unsubscribe, visit:

Reply via email to