Re:

[John_Waller@xxxxxxxxxxxxx]

I have to admit I'm not any good at compiling.
My knowledge is limited to 3 steps;
./configure
make
make install
If I have to add or take away any extra
arguments, I have to blindly follow a doc or someone's advice because I
have no clue what the arguments are or what they do. I did leave out everything
at first and the configure ran through without any errors but the pcre
wasn't part of it. I have no idea what pcre is, only that the apache web
site doc said it was required so I don't know how I would leave that out.
I have already seen so many different docs that have me going in all different
directions to get apache installed that I now have a huge mix of just about
everything that can be installed yet I still can't get apache to install.

So I just blindly followed what you
sent and here's what I get when I use that info.

checking for APR-util... yes
checking for gcc... xlc_r -q64
checking whether the C compiler works...
no
configure: error: in `/home/jwaller/httpd-2.4.7':
configure: error: C compiler cannot
create executables
See `config.log' for more details
lastorecomdev:/home/jwaller/httpd-2.4.7>


No matter who's advice I have followed
or what doc, all I get is errors and I don't get any closer to an actual
installation of apache.
I really would love to see an actual
doc for this instead of having to pull many docs together, cross my fingers
and still hope it just works.
Thanks.
John



From:      
 Eric Covener <covener@xxxxxxxxx>
To:      
 users@xxxxxxxxxxxxxxxx
Date:      
 02/04/2014 04:02 PM
Subject:    
   Re:

---

On Tue, Feb 4, 2014 at 11:53 AM,  <John_Waller@xxxxxxxxxxxxx>
wrote:
> Hi Eric. Thanks for the response. I looked at both web sites and basically
> started all over. I downloaded the pcre packages and installed. Those,
of
> course, complained about dependencies so, after many times downloading
some
> extra dependencies, I finally got back to the point of compiling apache.
> After I use the ./configure command, I still get the error saying
it can't
> find the pcre-config, even though it is pointed to on the command
line. So,
> I'm still stuck at the same point I was last week. Any other ideas?

Have you tried omitting anything about pcre from your ./configure?

When I build similar to the wiki, my configure line is very simple:

My default env:

/usr/local/svnkit/bin:/home/covener/wasbld/mantis/bin:/home/covener/bin:/home/covener/java/jre/bin:/home/covener/java/bin:/usr/bin:/etc:/usr/sbin:/usr/ucb:/usr/bin/X11:/sbin:/usr/java14/jre/bin:/usr/java14/bin:/usr/ccs/bin:/usr/vacpp/bin:/usr/sbin:/usr/local/bin:/opt/freeware/bin:/home/covener/java/bin

What I add during build:

export OBJECT_MODE=64
export CC="xlc_r -q64"
export PATH=/opt/freeware/bin:$PATH
export CONFIG_SHELL=/usr/bin/bash

export lt_cv_path_NM="/usr/bin/nm -B -X64"
export AR="ar -X64"

My configure line from config.nice:

#! /bin/sh
#
# Created by configure

CC="xlc_r -q64"; export CC
"./configure" \
"--enable-mods-shared=all" \
"--prefix=/tmp/httpd-2.4.7/built" \
"--enable-maintainer-mode" \
"CC=xlc_r -q64" \
"$@"

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx




This communication is intended only for the use of the individual or entity
named as the addressee. It may contain information that is privileged and/or
confidential under applicable law. If you are not the intended recipient
or such recipient's employee or agent, you are hereby notified that any
dissemination, copy or disclosure of this communication is strictly prohibited.
If you have received this communication in error, please notify the sender
immediately via email and delete this communication and its attachments
without making any copies. Thank you for your cooperation.