ID:               21896
 Updated by:       [EMAIL PROTECTED]
 Reported By:      [EMAIL PROTECTED]
-Status:           Open
+Status:           Feedback
-Bug Type:         Compile Warning
+Bug Type:         Compile Failure
 Operating System: RH linux 7.2
 PHP Version:      4.3.0
 New Comment:

First of all, the warning for mysql part is harmless and
can be ignored. The other one is an error..

Your configure line is broken for starters, you don't 
specify the path for apxs correctly. (notice the space between
--with-apxs= and the path..)

What gcc version you have?

And try this:

# make clean ; rm config.cache
# ./configure --with-apxs=/usr/local/apache/bin/apxs --disable-all
# make

And let us know the result.



Previous Comments:
------------------------------------------------------------------------

[2003-01-27 01:33:26] [EMAIL PROTECTED]

I am  trying to
Upgrade / Install php from php4.2.3 to php4.3.0
System config:
Redhat :Linux 7.2 Kernel 2.4.7-10 , apache 1.2.7 , pgsql 7.3
, Mysql  3.23.41

While i am compiling the source i recve the following error
I have tried to compile on an other machine with same configuration .
The configure script is
<code>
./configure \--with-apxs= /usr/local/apache/bin/apxs  \--enable-bcmath
\--with-zlib \--with-b2z \--enable-sockets \--enable-wddx
\--enable-calendar
\--enable-multibyte \--with-pgsql \--with-gettext

Error is ------------
.lo -lcrypt -lresolv -lm -ldl -lnsl -lcrypt  -o sapi/cgi/php
ext/mysql/libmysql/my_tempnam.o: In function `my_tempnam':
/hdc6/apache/php-4.3.0/ext/mysql/libmysql/my_tempnam.c:103: the use of
`tempnam'
 is dangerous, better use `mkstemp'
/usr/bin/ld: BFD internal error, aborting at elf32-i386.c line 1741 in
elf_i386_
relocate_section

/usr/bin/ld: Please report this bug.

collect2: ld returned 1 exit status
make: *** [sapi/cgi/php] Error 1
------ends here
</code>

Do any one have any idea whats wrong ?????

------------------------------------------------------------------------


-- 
Edit this bug report at http://bugs.php.net/?id=21896&edit=1

Reply via email to