php-install Digest 17 May 2002 12:05:02 -0000 Issue 839

Topics (messages 7008 through 7014):

Re: Send mail Server Error
        7008 by: Jason Reid

Uninstall of PHP Source Version
        7009 by: Grant Furick

Re: problems installing ldap
        7010 by: Grant Furick

Re: Upgrading RH 7.2 RPMS
        7011 by: Grant Furick

Help. Strange behavior with imap, php and apache
        7012 by: Sergio Tirado

Problem with PHP-4.2.1 installation
        7013 by: Andrew Afliatunov

PHP 4.2.1 build problems on Solaris (plus fix)
        7014 by: Joerg Prante

Administrivia:

To subscribe to the digest, e-mail:
        [EMAIL PROTECTED]

To unsubscribe from the digest, e-mail:
        [EMAIL PROTECTED]

To post to the list, e-mail:
        [EMAIL PROTECTED]


----------------------------------------------------------------------
--- Begin Message ---
Can you send email to any other address from this server? If not, it is most
likely a error in the configuration of sendmail in php.ini.

----- Original Message -----
From: "Salvador Gil" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, May 16, 2002 4:45 PM
Subject: [PHP-INST] Send mail Server Error


> I´m sending a mail and recieve the following message:
> Warning:  Server Error in d:\seguros2002\email.phtml on line
> <b>41</b><br>
>
> the instruction in question is:
>
>  mail($to, $subject, $message, $headers);
>
> where:
> $to:[EMAIL PROTECTED]
> $headers:
>  MIME-Version: 1.0
> Content-type: text/html; charset=iso-8859-1
> From: Estrategas en Proteccion <[EMAIL PROTECTED]>
>
> when I send mail to my mail [EMAIL PROTECTED] it works FINE.
>
> Any idea about this?
>
>
> Thank´s in advance.
>
> --
> PHP Install Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php

--- End Message ---
--- Begin Message ---
I downloaded, compiled, and installed PHP 4 from source as a DSO with
Apache.  In also installed apache from source.

I would like to move away from the source install and use rpms with my
Redhat 7.2, soon to be 7.3 box.  What is the best/cleanest way to remove php
from the system so that I can install it from rpm along with the rpm version
of apache?

I realize it is just a DSO that needs to be removed from apache but there
seem to be some files in /usr/local/lib/php/ .  Should I just remove the
module from the Apache config file and delete the php directory and the
php.ini file?  Are there are other things to remove?

Grant


--- End Message ---
--- Begin Message ---
Jim,
I you may want to look closer at your webserver configuration file and make
sure that indeed it is pointing to the right place for the nsapi for php.
The ldap_start_tls message leads me to believe that ssl is involved with
ldap and that maybe there is some issue there.

These are just guesses.

"Jim Harle" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> I'm installing php for the first time and have managed to slog thorigh
> most of the oddities (some imposed bu php, some by my configuration).  I
> noticed that most of the ldap questions in this newsgroup have gone
> unanswered.  I hope that someone at least will point me to a place that
> gets me further.
>
> Please don't stop reading because you see that I am using the iplanet
> server.  I don't think that has direct bearing on my problem.  Also, I
> don't think the problem is related to the fact that I am doing this on a
> Solaris 8 box.
>
> I am building php 4.2.0.  I used the following to configure it:
>
> ./configure --enable-ftp --with-ldap=/usr/local/src/ldap/netscSDK4
> --with-nsapi=/www/webdevel/iplanetserver --without-mysql
> --enable-track-vars --enable-force-cgi-redirect --with-gettext
> --with-imap --with-xml --with-pspell
>
> The directory /usr/local/src/ldap/netscSDK4 contains everything from the
> latest Netscape/iPlanet/Sun C SDK for Solaris.
>
> When I start the iplanet server, I get the following:
>
> conf_init: Error running init function load-modules: dlopen of
> /www/webdevel/iplanetserver/bin/libphp4.so failed (ld.so.1: ns-httpd:
> fatal: relocation error: file
> /www/webdevel/iplanetserver/bin/libphp4.so: symbol ldap_start_tls_s:
> referenced symbol not found)
>
> One caveat: I first configured and make'd with a plain --with-ldap (no
> =/path ) and got the same results.
>
> Thanks for anything that will get me further along.
>
>   --Jim Harle
>


--- End Message ---
--- Begin Message ---
you can do rpm -u for upgrade of a package via rpm.


"Brian Speck" <[EMAIL PROTECTED]> wrote in message
000001c1f061$714a1920$3200a8c0@freeze1">news:000001c1f061$714a1920$3200a8c0@freeze1...
> I was wondering if Anyone has experience upgraded from 4.0.6 ( RH 7.2
> RPMS)
> To the New 4.2..
> If so Can someone Advised me what to do..
>
> Do I have to remove the RPMS and then do a standard Install like I would
> from scratch.. or is thre an Upgrade?
>
>
> Brian Speck
>
>


--- End Message ---
--- Begin Message ---

I just installed Red Hat 7.3 with Apache and PHP. I ran a simple script
to test the imap_open function and it doesn't work when using the values
for my server. 

http://www.gym.itesm.mx/imap.php

However, if the mailbox I request to open is on another server, it does work. 

The strange thing is that a friend of mine has the same script running on his 
server (http://pollux.icon.net.mx/~antonio/imap.php) and he can read a mailbox 
from my server as well as any other.

When I run the script on my server and try to access a local mailbox I get the
following error:

Warning: Couldn't open stream {www.gym.itesm.mx:143}INBOX in 
/home/campus/html/imap.php on line 5

I just don't know what could be wrong. Help is appreciated.

Here is the script:

<?php

function test_imap($mbx,$uid,$pwd)
{
  if (!$mbox = imap_open ($mbx, $uid, $pwd))
  {
    echo "<br /><br />";
    echo "<span style='font size: x-large;color:red;'>Password incorrecto</span>";
    echo "<br /><br />";
    echo "<pre>";
    echo "<b>Mailbox.:</b> $mbx<br />";
    echo "<b>Cuenta..:</b> $uid<br />";
    echo "<b>Password:</b> $pwd<br />";
    echo "<b>Error...:</b> "; echo imap_last_error();
    echo "</pre>";
  } else {
    echo "Password correcto: $mbx";
    imap_close($mbox);
  }
}

if (!isset($mbx1))  $mbx1 = "{www.gym.itesm.mx:143}INBOX";
if (!isset($uid1))  $uid1 = "gsoberon";
if (!isset($pwd1))  $pwd1 = "mypass";

if (isset($test)) {
  test_imap($mbx1,$uid1,$pwd1);
}

?>
<html>
  <body>
    <hr>
    <form action="imap.php" method="get">
      <p>
        mailbox: <input type=text name=mbx1 value="<?echo $mbx1;?>"><br />
        usuario: <input type=text name=uid1 value="<?echo $uid1;?>"><br />
        passwd: <input type=text name=pwd1 value="<?echo $pwd1;?>"><br />
        <br />
        <input type=submit name="test" value="Test">
      </p>
    </form>
  </body>
</html>

--
Sergio T.
--- End Message ---
--- Begin Message ---
Hi!

I'm using apache-1.3.22 with PHP-4.1.2 on SunOS-5.7 machine. Now I want
to upgrade PHP to 4.2.1. So, 'configure' prints a few lines like this
--
checking for unix.h... grep: can't open conftest.out
yes
--
but it completes without errors. Then I run 'make' I get this:
--
>make
Making all in Zend
/bin/sh ../libtool --silent --mode=compile gcc -DHAVE_CONFIG_H -I. -I.
-I../maic
In file included from zend_compile.h:24,
                 from zend_language_parser.c:147:
zend.h:55: unix.h: No such file or directory
*** Error code 1
make: Fatal error: Command failed for target `zend_language_parser.lo'
Current working directory /var/tmp/php/php-4.2.1/Zend
*** Error code 1
make: Fatal error: Command failed for target `all-recursive'
--

My question is - what the hell is unix.h, why PHP 'configure' detects
file that is missing and how for all that can I compile PHP-4.2.1?



--- End Message ---
--- Begin Message ---
Hi,

I got into trouble building PHP 4.2.1 with the option 
'--with-openssl=[myopenssldir]' on Solaris 2.8. The 'configure' 
script failed with

checking for OpenSSL version... configure failed: openssl > 0.9.5 is required

even if a correct version of openssl 0.9.6c exists. This is
a bug because PHP 4.2.0 will build without any problems using 
exactly the same 'configure' parameters.

I discovered the build failure is due to the change of the autoconf version 
from PHP 4.2.0 to PHP 4.2.1 that created the 'configure' script.

The result is that PHP 4.2.1 builds may fail on Solaris.

Here is my fix. You have to install the latest GNU m4/autoconf/automake 
utilities from ftp.gnu.org on your Solaris machine and re-run 
'autoconf' in the  PHP 4.2.1 build directory to re-create a 
correct 'configure' script.

I installed
    GNU m4 1.4
    GNU Autoconf 2.53
    GNU Automake 1.6

Now, 'configure' will work as expected.

If this can be confirmed, a note in the INSTALL file would be appreciated.

Jörg Prante

--- End Message ---

Reply via email to