Re: FreeBSD 7.0 + apache 1.3.41 + php 5.2.8 = fail



Chris <c.petrik.sosa@xxxxxxxxx> wrote:
On Fri, 13 Feb 2009 12:32:35 -0600, Cydrome Leader
<presence@xxxxxxxxxxxxxx> wrote:

Chris <c.petrik.sosa@xxxxxxxxx> wrote:
On Fri, 13 Feb 2009 10:19:55 -0600, Cydrome Leader
<presence@xxxxxxxxxxxxxx> wrote:

Helmut Schneider <jumper99@xxxxxx> wrote:
Cydrome Leader <presence@xxxxxxxxxxxxxx> wrote:


[self-compiling apache 1.3.41 and php5.2.8]

The version of apache+apxs from the ports tree DOES work with php
compiled from source, so I suspect it's something with apache, not
php.

Just cause I'm curious, why don't you use ports at all?!

I need to compile in options I want, and I don't want any updates to
the
ports tree stepping on what's in place if I do an upgrade.

Also, compiling from source insures the same behavior across different
platforms.



If you are compiling from ports we can help you if you are not then we
wont waste our time answering questions. The ports system is meant to
be a
easy way of maintaining and upgrading ports. The same funcionality can
be
compiled in modifying the Makefile or adding in make options such as
make
-DWITH_PHP5 or the like.

I think you're missing the point, and that something is different in
Freebsd 7 vs 6,5,4 that makes apache unhappy. Maybe this problem can be
identified/documented/corrected.

Also the port maintainers would appreciate if you email them for issues
as
it will fix it for all of us rather trying to backout the path. Ports in
some way are beta quality and sometimes the ports have issues like all
humans we make mistakes.

I'm not using the ports for apache of php.

I think you also forgor that if the problem is docummented and fixed,
maybe somebody can add this to the ports tree if needed.

Some ports require a little fiddling with to make them work
inexperienced
people will have issues with these types of ports, sending a email
directly to the ports maintainer will have this fix in my experience
most
are eigar to help those in need while others......

Again, I'm not using the ports. I'm using very vanilla software from
source, and historically the freebsd environment has been just as plain
which allows for most things to build correctly.

This has changed.

So, does somebody know what causes with apache 1.3 and freebsd 7?



This is a new FreeBSD 7.1 install with no ports installed on a Virtual Box
VM. I downloaded the following:

Apache 1.3.41
PHP 5.2.8
Gmake (ports)
libtool (ports)
automake (ports)

I added in aspx and some other options and compiled in PHP5 support. and
the compile is fine and everything works, so I am confused as to why you
are complaining it doesn't work?

To recap, I'm complaining because of this:

[root@bsd7 /opt]# /opt/apache_1.3.41/bin/apachectl start
Syntax error on line 205 of /opt/apache_1.3.41/conf/httpd.conf:
Cannot load /opt/apache_1.3.41/libexec/libphp5.so into server:
/opt/apache_1.3.41/libexec/libphp5.so: Undefined symbol "ap_user_id"
/opt/apache_1.3.41/bin/apachectl start: httpd could not be started

That's an error. Errors mean stuff isn't working. When software doesn't
work, it's hard to use.

In case you forgot again, I'm posting because of this error:

[root@bsd7 /opt]# /opt/apache_1.3.41/bin/apachectl start
Syntax error on line 205 of /opt/apache_1.3.41/conf/httpd.conf:
Cannot load /opt/apache_1.3.41/libexec/libphp5.so into server:
/opt/apache_1.3.41/libexec/libphp5.so: Undefined symbol "ap_user_id"
/opt/apache_1.3.41/bin/apachectl start: httpd could not be started

saying this can you give me some compile in options you have, are you

All options used were listed in the top of this thread. They were very
simple.

using any special thread libs, any other info you can tell me so I can
reproduce the issue you are having and possibly give you a fix?

Follow my commands in the first post. It's very easy to repeat.

the 1.3 branch if a legacy release so I don't think they bother to make
sure it works on all OS's but is only what I have seen in my experience.

There's no good reason something like apache should NOT work under a BSD.
I can understand it not working on SCO or OS/2, but not FreeBSD.

Also please note, I think you know this but modules which are compiled for
1.3 don't work for 2.x and vice versa, so if you are adding in any modules
which were previously compiled for 2.x remove them and recompiled them for
the 1.3.41. Why not stick with the 2.2 branch?

My first post explains what I did. There is no confusion over --with-apxs
and --with-apxs2 flags for configure of php.


.



Relevant Pages

  • Re: upgrage from 4.1.2 to 4.3.3+?
    ... > every available RPM for the distro...and there isn't one for PHP. ... > And also, I uh, don't believe I've ever recompiled Apache or PHP. ... Well - You could compile your own version of Apache and PHP and place it ... port number - By this I mean, whenever you visit a website, it defaults ...
    (comp.lang.php)
  • Re: php compile options
    ... On Friday 09 September 2005 11:13, the author Kevin Kinsey contributed to the ... Re: php compile options: ... When php5 is compiled from ports I understand a file is generated to ... Options expressed on the command line for php are normally in lower ...
    (freebsd-questions)
  • RE: Very Annoying PHP Errors
    ... What I did was downgraded the php port to 5.2.0 and just re-compiled php and all of it's extensions to 5.2.0. ... I'm using FreeBSD 6.1 with Apache 2.2.4 and PHP 5.2.0 with Sushion, ipv6 support, and Apache support. ... Is there an easy way to downgrade ports? ... sometimes both but also sometimes both install without errors. ...
    (freebsd-questions)
  • Re: Any problems with php 4.3.8_2
    ... > are uncommented, apache segfaults on startup. ... the structure of the php4 ports parallels the structure ... CONFLICTS thing is about not installing ports that all lay claim to ... the symptom you see of PHP causing apache to segfault ...
    (freebsd-questions)
  • Re: Upgrade PHP
    ... > server in which i have to upgrade PHP from 4 to 5. ... > I've read about the ports, ... Now go ahead and replace all of the php4 modules with their php5 ... You should stop apache before starting on this whole exercise, ...
    (freebsd-questions)