ID: 10818
User Update by: [EMAIL PROTECTED]
Old-Status: Feedback
Status: Open
Bug Type: Compile Failure
Operating system: OpenBSD 2.7
PHP Version: 4.0.5
Description: configure error

Unfortunately, I am getting the same error, even with simply './configure'.

Configuring SAPI modules
./configure[2365]: syntax error: `./scripts/config-stubs' unexpected

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

[2001-05-14 08:35:12] [EMAIL PROTECTED]
Hello,

there is some trouble with the HEAD branch regarding the new libtool,
so can you possibly checkout the PHP_4_0_6 branch from cvs:

cvs -d :pserver:[EMAIL PROTECTED]:/repository co -r PHP_4_0_6 php4
cd php4
cvs -d :pserver:[EMAIL PROTECTED]:/repository co -r PHP_4_0_6 co TSRM ZEND
cd ..
./buildconf

This works fine for me on OpenBSD 2.8 with libtool 1.3.3

regards,
Derick

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

[2001-05-11 22:23:37] [EMAIL PROTECTED]
The full error message was what you saw.  Configure went fine up until the SAPI part.  
My configure line was either the full blown one I use with every option I want to 
simply './configure'.  Same error.  But note that 4.0.5 configures and builds with no 
problem.

Here's the config.log:

configure:1202: checking for a BSD compatible install
configure:1255: checking whether build environment is sane
configure:1312: checking whether make sets ${MAKE}
configure:1351: checking for working aclocal
configure:1364: checking for working autoconf
configure:1377: checking for working automake
configure:1390: checking for working autoheader
configure:1403: checking for working makeinfo
configure:1433: checking whether to enable maintainer-specific portions of Makefiles
configure:1462: checking host system type
configure:1490: checking for mawk
configure:1490: checking for gawk
configure:1490: checking for nawk
configure:1524: checking for bison
configure:1558: checking bison version
configure:1571: checking for gcc
configure:1684: checking whether the C compiler (gcc  ) works
configure:1700: gcc -o conftest    conftest.c  1>&5
configure:1726: checking whether the C compiler (gcc  ) is a cross-compiler
configure:1731: checking whether we are using GNU C
configure:1740: gcc -E conftest.c
configure:1759: checking whether gcc accepts -g
configure:1791: checking how to run the C preprocessor
configure:1812: gcc -E  conftest.c >/dev/null 2>conftest.out
configure:1871: checking for AIX
configure:1919: checking for gcc option to accept ANSI C
configure:1972: gcc  -c -g -O2  conftest.c 1>&5
configure:1999: checking for ranlib
configure:2028: checking whether gcc and cc understand -c and -o together
configure:2043: gcc -c conftest.c -o conftest.o 1>&5
configure:2044: gcc -c conftest.c -o conftest.o 1>&5
configure:2049: cc -c conftest.c 1>&5
configure:2051: cc -c conftest.c -o conftest.o 1>&5
configure:2052: cc -c conftest.c -o conftest.o 1>&5
configure:2079: checking whether ln -s works
configure:2103: checking for flex
configure:2137: checking for yywrap in -lfl
configure:2156: gcc -o conftest -g -O2   conftest.c -lfl   1>&5
configure:2180: checking lex output file root
configure:2201: checking whether yytext is a pointer
configure:2220: gcc -o conftest -g -O2   conftest.c  -lfl 1>&5
configure:2244: checking for working const
configure:2298: gcc -c -g -O2  conftest.c 1>&5
configure:2415: gcc -o conftest -g -O2   conftest.c  1>&5
configure:2410: Undefined symbol `_pthread_mutexattr_init' referenced from text 
segment
configure:2411: Undefined symbol `_pthread_create' referenced from text segment
collect2: ld returned 1 exit status
configure: failed program was:
#line 2397 "configure"
#include "confdefs.h"

#include <pthread.h>
#include <stddef.h>

void *thread_routine(void *data) {
    return data;
}

int main() {
    pthread_t thd;
    pthread_mutexattr_t mattr;
    int data = 1;
    pthread_mutexattr_init(&mattr);
    return pthread_create(&thd, NULL, thread_routine, &data);
} 
configure:2435: checking for pthreads_cflags
configure:2468: gcc -o conftest -g -O2 -kthread   conftest.c  1>&5
gcc: unrecognized option `-kthread'
configure:2463: Undefined symbol `_pthread_mutexattr_init' referenced from text 
segment
configure:2464: Undefined symbol `_pthread_create' referenced from text segment
collect2: ld returned 1 exit status
configure: failed program was:
#line 2450 "configure"
#include "confdefs.h"

#include <pthread.h>
#include <stddef.h>

void *thread_routine(void *data) {
    return data;
}

int main() {
    pthread_t thd;
    pthread_mutexattr_t mattr;
    int data = 1;
    pthread_mutexattr_init(&mattr);
    return pthread_create(&thd, NULL, thread_routine, &data);
} 

configure:2468: gcc -o conftest -g -O2 -pthread   conftest.c  1>&5
configure:2497: checking for pthreads_lib


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

[2001-05-11 22:00:01] [EMAIL PROTECTED]
What is the full error message?
What does it say in config.log ?
What was the configure line you used?

--Jani


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

[2001-05-11 21:53:58] [EMAIL PROTECTED]
Thanks, Jani, but I did get a new build today with the same error.  I followed the 
instructions at http://www.php.net/anoncvs.php exactly, since I am not terribly 
familiar with CVS.  The 4.0.5 distribution configures fine.

Thanks again.


-Ken

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

[2001-05-11 20:42:55] [EMAIL PROTECTED]
Get a new checkout. And remember to checkout Zend and TSRM
modules from cvs.zend.com too!

Instructions can be found here:

http://www.php.net/anoncvs.php

And this always: './cvsclean ; ./buildconf' 

--Jani



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

The remainder of the comments for this report are too long.  To view the rest of the 
comments, please view the bug report online.

Full Bug description available at: http://bugs.php.net/?id=10818


-- 
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to