mod_php4: Anyone gotten it to build on 4.7 yet?

mod_php4: Anyone gotten it to build on 4.7 yet?

Post by mikete.. » Sat, 11 Jan 2003 03:08:40



Hi,

I'm trying to get an Apache/SSL/PHP4/MySQL/etc. server set-up on a
newly installed 4.7 machine.

I did the cvsup (and make world, etc.) to get the latest source.

I installed apache13-modssl and mysql323-server.

Then, I went to install mod_php4 and I keep getting an error about
how the configure script failed and to e-mail the maintainer (which
I did, but I'd guess he's one of those people who gets 10,000 e-mails
a day, so I'm not holding hope).

I did some scouring on Google and some people suggested linking the
(this is off the top of my head, so the names may not be exactly
correct, but you can get my idea):

/usr/lib/mysql/libmysqlclient.so to /usr/lib/libmysqlclient.so

Well, I tried this and did not get any further.

I can cd into the work dir and run the configure by hand just fine,
but I suspect that I'm not passing-in some argument that the official
ports Makefile is.

Can someone point me in the right direction to get this mod_php4 to
install?  I'd prefer not to build everything by hand and instead use
the ports so I can leverage existing work.

Thanks,
Mike

 
 
 

mod_php4: Anyone gotten it to build on 4.7 yet?

Post by Remco Bresser » Sat, 11 Jan 2003 03:50:29


Hi,

No problems building it overhere.. Try CVSUP'ing the thing again..

remco bressers


> Hi,

> I'm trying to get an Apache/SSL/PHP4/MySQL/etc. server set-up on a
> newly installed 4.7 machine.

> I did the cvsup (and make world, etc.) to get the latest source.

> I installed apache13-modssl and mysql323-server.

> Then, I went to install mod_php4 and I keep getting an error about
> how the configure script failed and to e-mail the maintainer (which
> I did, but I'd guess he's one of those people who gets 10,000 e-mails
> a day, so I'm not holding hope).

> I did some scouring on Google and some people suggested linking the
> (this is off the top of my head, so the names may not be exactly
> correct, but you can get my idea):

> /usr/lib/mysql/libmysqlclient.so to /usr/lib/libmysqlclient.so

> Well, I tried this and did not get any further.

> I can cd into the work dir and run the configure by hand just fine,
> but I suspect that I'm not passing-in some argument that the official
> ports Makefile is.

> Can someone point me in the right direction to get this mod_php4 to
> install?  I'd prefer not to build everything by hand and instead use
> the ports so I can leverage existing work.

> Thanks,
> Mike


 
 
 

mod_php4: Anyone gotten it to build on 4.7 yet?

Post by Kirk Strause » Sat, 11 Jan 2003 05:30:06



> I did the cvsup (and make world, etc.) to get the latest source.

But did you cvsup ports?  Updating your source is not the same thing.
--
Kirk Strauser
 
 
 

mod_php4: Anyone gotten it to build on 4.7 yet?

Post by mikete.. » Sat, 11 Jan 2003 05:40:32




>> I did the cvsup (and make world, etc.) to get the latest source.

> But did you cvsup ports?  Updating your source is not the same thing.

Yep -- updated the whole shebang (ports-all).

I just did a cvsup moments ago and saw many of the ports get updated,
but not lang/php4 or mod_php4.

I still get this error when doing a make in mod_php4:

===========================================================================
checking for mysql_close in -lmysqlclient... no
checking for mysql_error in -lmysqlclient... no
configure: error: mysql configure failed. Please check config.log for more information.
===>  Script "configure" failed unexpectedly.

      the "/usr/ports/www/mod_php4/work/php-4.2.3/config.log" including the
      output of the failure of your make command. Also, it might be a good
      idea to provide an overview of all packages installed on your system
      (e.g. an `ls /var/db/pkg`).
*** Error code 1

Stop in /usr/ports/www/mod_php4.
*** Error code 1

Stop in /usr/ports/www/mod_php4.
===========================================================================

The error in the config.log (as requested in the above error) is:
===========================================================================
configure:39907: checking for mysql_error in -lmysqlclient
configure:39926: cc -o conftest -O -pipe  -I/usr/local/include  -DHARD_SERVER_LIMIT=512 -DDOCUMENT_LOCATION="/usr/local/www/data/" -DDEFAULT_PATH="/usr/local/bin:/bin:/usr/bin" -DACCEPT_FILTER_NAME="httpready" -DMOD_SSL=208112 -DEAPI -DEAPI_MM -DUSE_EXPAT
        -L/usr/lib -L/usr/local/lib/mysql
        -R/usr/local/lib -L/usr/local/lib -R/usr -L/usr conftest.c -lmysqlclient  -lz -lmhash -lmcve -lmcrypt -lltdl -lcrypt -lpam -lbz2 -lz -lcrypt -lssl -lcrypto -lm  -lcrypt 1>&5
/usr/local/lib/libmcve.so: undefined reference to `pthread_mutex_unlock'
/usr/local/lib/libmcve.so: undefined reference to `pthread_mutex_destroy'
/usr/local/lib/libmcve.so: undefined reference to `pthread_mutex_lock'
/usr/local/lib/libmcve.so: undefined reference to `pthread_mutex_init'
configure: failed program was:
#line 39915 "configure"
#include "confdefs.h"
/* Override any gcc2 internal prototype to avoid an error.  */
/* We use char because int might match the return type of a gcc2
    builtin and then its argument prototype would still apply.  */
char mysql_error();

int main() {
mysql_error()
; return 0; }
===========================================================================

I don't seem to be the only one getting this problem:
<http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&q=freebsd...>

Any ideas?

Thanks,
Mike

 
 
 

mod_php4: Anyone gotten it to build on 4.7 yet?

Post by Aaron Baughe » Sat, 11 Jan 2003 06:15:05



> I'm trying to get an Apache/SSL/PHP4/MySQL/etc. server set-up on a
> newly installed 4.7 machine.

> I installed apache13-modssl and mysql323-server.

When you install mysql323-server (or maybe it's only when you install
mysql323-client, I forget) it creates a startup file at
/usr/local/etc/rc.d/mysql-client.sh.  All this does is:

  /sbin/ldconfig -m /usr/local/lib/mysql

In other words, it makes the location of the mysql client libraries
available to be compiled and linked against.  Run that as root, and
the mod_php4 port should be able to find mysql.

--
Aaron

 
 
 

mod_php4: Anyone gotten it to build on 4.7 yet?

Post by mikete.. » Sat, 11 Jan 2003 07:18:46



> When you install mysql323-server (or maybe it's only when you install
> mysql323-client, I forget) it creates a startup file at
> /usr/local/etc/rc.d/mysql-client.sh.  All this does is:

>  /sbin/ldconfig -m /usr/local/lib/mysql

> In other words, it makes the location of the mysql client libraries
> available to be compiled and linked against.  Run that as root, and
> the mod_php4 port should be able to find mysql.

Thanks Aaron -- I will try that!  It makes sense, but I wonder why
the port does not do it on its own.

I'm in the middle of a portupgrade, but I'll give it a shot as soon
as that's done.

Thanks,
Mike

 
 
 

mod_php4: Anyone gotten it to build on 4.7 yet?

Post by mikete.. » Sat, 11 Jan 2003 07:20:37



> Thanks Aaron -- I will try that!  It makes sense, but I wonder why
> the port does not do it on its own.

Nevermind -- I see that it's intended to be run on startup and I have
not restarted this machine since I installed MySQL.  I guess this is
one package that wants to be like Windows and reboot to use it ;^)

Mike

 
 
 

mod_php4: Anyone gotten it to build on 4.7 yet?

Post by Kirk Strause » Sat, 11 Jan 2003 08:00:09



> Nevermind -- I see that it's intended to be run on startup and I have not
> restarted this machine since I installed MySQL.  I guess this is one
> package that wants to be like Windows and reboot to use it ;^)

Huh?  Those files in rc.d are just regular scripts.  I use them to start and
stop services on running machines all the time.  One caveat is that some
rc.d scripts expect to be called with their full pathname (i.e.,
/usr/local/etc/rc.d/foo.sh) because they use that path information to find
config files, etc.
--
Kirk Strauser
 
 
 

mod_php4: Anyone gotten it to build on 4.7 yet?

Post by mikete.. » Sat, 11 Jan 2003 09:14:04



> Huh?  Those files in rc.d are just regular scripts.  I use them to start and
> stop services on running machines all the time.  One caveat is that some
> rc.d scripts expect to be called with their full pathname (i.e.,
> /usr/local/etc/rc.d/foo.sh) because they use that path information to find
> config files, etc.

Well, I was meaning Windows-like as in it did not tell me that there was
a control script I needed to run to get other programs to compile, and
since the scripts are in the startup dir, I thought it might be slightly
humorous to make a reference to Windows (since rebooting is the way that
Windows seems to complete the install process many times).

Nevermind -- I guess it was not that entertaining. ;^)

Mike

 
 
 

mod_php4: Anyone gotten it to build on 4.7 yet?

Post by mikete.. » Sat, 11 Jan 2003 11:23:19



> When you install mysql323-server (or maybe it's only when you install
> mysql323-client, I forget) it creates a startup file at
> /usr/local/etc/rc.d/mysql-client.sh.  All this does is:

>  /sbin/ldconfig -m /usr/local/lib/mysql

> In other words, it makes the location of the mysql client libraries
> available to be compiled and linked against.  Run that as root, and
> the mod_php4 port should be able to find mysql.

Well, I tried this and I still get the same error.  I have
run both:

/usr/local/etc/rc.d/000.mysql-client.sh
/usr/local/etc/rc.d/mysql-server.sh

and if I do a ps|grep mysql, I do have the server running, so it
appears to be installed fine and is not bombing.

Any other ideas why I am getting that configure error from mod_php4?

Thanks,
Mike

 
 
 

mod_php4: Anyone gotten it to build on 4.7 yet?

Post by Kirk Strause » Sat, 11 Jan 2003 11:40:05



> Nevermind -- I guess it was not that entertaining. ;^)

Either that, or I hadn't had sufficient coffee yet.  Pick one.  :)
--
Kirk Strauser
 
 
 

mod_php4: Anyone gotten it to build on 4.7 yet?

Post by Aaron Baughe » Sat, 11 Jan 2003 20:53:39



> Well, I tried this and I still get the same error.  I have
> run both:

What's the actual error again?  I didn't see it in your original
post.  Can you post the last few lines that are displayed before it
dies?

--
Aaron

 
 
 

mod_php4: Anyone gotten it to build on 4.7 yet?

Post by mikete.. » Sun, 12 Jan 2003 01:34:23




>> Well, I tried this and I still get the same error.  I have
>> run both:

> What's the actual error again?  I didn't see it in your original
> post.  Can you post the last few lines that are displayed before it
> dies?

===========================================================================
checking for mysql_close in -lmysqlclient... no
checking for mysql_error in -lmysqlclient... no
configure: error: mysql configure failed. Please check config.log for more information.
===>  Script "configure" failed unexpectedly.

      the "/usr/ports/www/mod_php4/work/php-4.2.3/config.log" including the
      output of the failure of your make command. Also, it might be a good
      idea to provide an overview of all packages installed on your system
      (e.g. an `ls /var/db/pkg`).
*** Error code 1

Stop in /usr/ports/www/mod_php4.
*** Error code 1

Stop in /usr/ports/www/mod_php4.
===========================================================================

The error in the config.log (as requested in the above error) is:
===========================================================================
configure:39907: checking for mysql_error in -lmysqlclient
configure:39926: cc -o conftest -O -pipe  -I/usr/local/include  -DHARD_SERVER_LIMIT=512 -DDOCUMENT_LOCATION=
"/usr/local/www/data/" -DDEFAULT_PATH="/usr/local/bin:/bin:/usr/bin" -DACCEPT_FILTER_NAME="httpready" -DMOD_
SSL=208112 -DEAPI -DEAPI_MM -DUSE_EXPAT
        -L/usr/lib -L/usr/local/lib/mysql
        -R/usr/local/lib -L/usr/local/lib -R/usr
        -L/usr conftest.c -lmysqlclient  -lz -lmhash -lmcve -lmcrypt -lssl -lcrypto -lm  -lcrypt 1>&5
/usr/local/lib/libmcve.so: undefined reference to `pthread_mutex_unlock'
/usr/local/lib/libmcve.so: undefined reference to `pthread_mutex_destroy'
/usr/local/lib/libmcve.so: undefined reference to `pthread_mutex_lock'
/usr/local/lib/libmcve.so: undefined reference to `pthread_mutex_init'
configure: failed program was:
#line 39915 "configure"
#include "confdefs.h"
/* Override any gcc2 internal prototype to avoid an error.  */
/* We use char because int might match the return type of a gcc2
    builtin and then its argument prototype would still apply.  */
char mysql_error();

int main() {
mysql_error()
; return 0; }
===========================================================================

I don't seem to be the only one getting this problem:
<http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&q=freebsd...
ab=wg>

Thanks!
Mike

 
 
 

mod_php4: Anyone gotten it to build on 4.7 yet?

Post by Bill Vermilli » Sun, 12 Jan 2003 05:55:56






>>> Well, I tried this and I still get the same error.  I have
>>> run both:
>> What's the actual error again?  I didn't see it in your original
>> post.  Can you post the last few lines that are displayed before it
>> dies?
>===========================================================================
>checking for mysql_close in -lmysqlclient... no
>checking for mysql_error in -lmysqlclient... no
>configure: error: mysql configure failed. Please check config.log for more information.
>===>  Script "configure" failed unexpectedly.

Ah - that rings a bell on something totally different.

I had problems building several ports a few months ago and it was
all in configure.  I looked at the config.log and tried a few
times.

I saw that when configure was being called it also build a
sub-directory but called it with the wrong shell. bison tailed,
tex failed, antthing that was used the gnu configure failed.

I tried on 4 different machines. I found a 5th machine I
maintained that was newer than the others, and things worked as
they should I was running ksh at that time. I got new sources
from AT&T for ksh and things worked perfectly. I had just used the
older compiled ksh binaries on the other machines but the 5th one
was in a colo getting ready to go live and updated the entire OS
and utilities and that's when I spotted the shell difference.

So you might try another shell.  You didn't indicate what you were
using.  This may have no bearing on your problem but I had no
problems the PHP4 when I built it.

Bill
--