httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Felt <mamf...@gmail.com>
Subject Re: [RESULTS] [VOTE] Release httpd 2.3.4-alpha
Date Thu, 10 Dec 2009 15:13:08 GMT
Tom, thanks. Please check my new post. I made a new build system after all.

On Thu, Dec 10, 2009 at 3:53 PM, Tom Evans <tevans.uk@googlemail.com> wrote:

> On Thu, Dec 10, 2009 at 12:45 PM, Michael Felt <mamfelt@gmail.com> wrote:
> > well, for an alpha build I dont want to modify my standard build system
> too
> > much.
> >
> > So, if I understand you correctly I will have to run a make install for
> pcre
> > before this will have any chance to work.
> >
> > On Thu, Dec 10, 2009 at 2:38 PM, Tom Evans <tevans.uk@googlemail.com>
> wrote:
> >>
> >> On Thu, Dec 10, 2009 at 12:26 PM, Michael Felt <mamfelt@gmail.com>
> wrote:
> >> > michael@x054:[/data/prj/pcre-8.00]ls bin
> >> > ls: 0653-341 The file bin does not exist.
> >> > michael@x054:[/data/prj/pcre-8.00]mkdir bin
> >> > michael@x054:[/data/prj/pcre-8.00]ls *config
> >> > pcre-config
> >> > michael@x054:[/data/prj/pcre-8.00]ln *config bin
> >> > michael@x054:[/data/prj/pcre-8.00]
> >> >
> >> > * that seems to have solved the ./configure problem, but I suspect the
> >> > build
> >> > will not succeed. -lpcre is not in /usr/local/lib - it is still, at
> >> > best, in
> >> > the directory area of the project source.
> >> >
> >> > What does the --with-pcre=.... actually mean? I would hope it is not
> >> > just to
> >> > find the config program, that is no (longer?) stored in the ./bin/
> >> > directory
> >> > as expected.
> >> >
> >> > michael@x054:[/data/prj/alpha/httpd-2.3.4-alpha]grep pcre nohup.out
> >> > checking for pcre-config... false
> >> > configure: Using external PCRE library from
> >> > /data/prj/pcre-8.00/bin/pcre-config
> >> >   setting PCRE_LIBS to "-L/usr/local/lib -lpcre"
> >> > michael@x054:[/data/prj/alpha/httpd-2.3.4-alpha]find /usr/local/lib
> >> > /data/prj/pcre* | grep libpcre
> >> > /data/prj/pcre-8.00/libpcreposix.la
> >> > /data/prj/pcre-8.00/libpcrecpp.pc.in
> >> > /data/prj/pcre-8.00/libpcre.pc.in
> >> > /data/prj/pcre-8.00/libpcreposix.pc.in
> >> > /data/prj/pcre-8.00/.libs/libpcre.exp
> >> > /data/prj/pcre-8.00/.libs/libpcre.so.0
> >> > /data/prj/pcre-8.00/.libs/libpcre.a
> >> > /data/prj/pcre-8.00/.libs/libpcre.lai
> >> > /data/prj/pcre-8.00/.libs/libpcre.la
> >> > /data/prj/pcre-8.00/.libs/libpcreposix.exp
> >> > /data/prj/pcre-8.00/.libs/libpcreposix.so.0
> >> > /data/prj/pcre-8.00/.libs/libpcreposix.a
> >> > /data/prj/pcre-8.00/.libs/libpcreposix.lai
> >> > /data/prj/pcre-8.00/.libs/libpcreposix.la
> >> > /data/prj/pcre-8.00/libpcre.pc
> >> > /data/prj/pcre-8.00/libpcreposix.pc
> >> > /data/prj/pcre-8.00/libpcrecpp.pc
> >> > /data/prj/pcre-8.00/libpcre.la
> >> >
> >>
> >> --with-pcre=<arg> is expecting pcre to be installed to the prefix arg.
> >> Typically, if you want to install/use software that is not part of
> >> your os, you would configure pcre with something like:
> >>
> >>  ./configure --prefix=/opt
> >> make all install
> >>
> >> and then configuring apache is simply ./configure --with-pcre=/opt
> >>
> >> HTH
> >>
> >> Tom
> >
> >
>
> Only if you want --with-pcre to work in configure. You could also
> specify the include paths for pcre by setting the CFLAGS environment
> variable, the linker flags for pcre in LDFLAGS, etc.
>
> I would just install it tbh.
>
> Cheers
>
> Tom
>

Mime
View raw message