These should also not be required:
export
CFLAGS="-I${PRODUCT_DIR}/lib/python2.7/site-packages/mod_wsgi_httpd-2.4.23.1-py2.7-linux-x86_64.egg/mod_wsgi_packages/httpd/include"
export CFLAGS="$CFLAGS
-I${PRODUCT_DIR}/lib/python2.7/site-packages/mod_wsgi_httpd-2.4.23.1-py2.7-linux-x86_64.egg/mod_wsgi_packages/httpd/include/apr-1"
Graham
> On 7 Dec 2016, at 9:10 PM, Graham Dumpleton <graham.dumple...@gmail.com>
> wrote:
>
> One thing that is wrong is that you should not be setting:
>
> export
> PATH=${PRODUCT_DIR}/lib/python2.7/site-packages/mod_wsgi_httpd-2.4.23.1-py2.7-linux-x86_64.egg/mod_wsgi_packages/httpd/bin:${PATH}
> I don’t know if that could be confusing things.
>
>> On 7 Dec 2016, at 8:42 PM, Michael Graber <michigra...@gmail.com
>> <mailto:michigra...@gmail.com>> wrote:
>>
>>
>> Thanks, it's good to know, that we are not doing anything unreasonable ..
>>
>> We do not have pip in our package management system. So before going along
>> the path of adding it:
>>
>> mod_wsgi-apxs -q APR_CONFIG
>>
>> returns a path in the build directory:
>>> + mod_wsgi-apxs -q APR_CONFIG
>>> /des002/devel/eeups/ci_build_desbuild/EupsBuildDir/Linux64/modWSGI-4.5.7+0/modWSGIhttpd-2.4.23.1/build/httpd/bin/apr-1-config
>>> + mod_wsgi-apxs -q APU_CONFIG
>>> /des002/devel/eeups/ci_build_desbuild/EupsBuildDir/Linux64/modWSGI-4.5.7+0/modWSGIhttpd-2.4.23.1/build/httpd/bin/apu-1-config
>>
>> Can you explain why this is the case?
>>
>> This could be problematic, right?
>>
>> Thanks!
>> Michael
>>
>>
>>
>>
>> On Wednesday, December 7, 2016 at 10:20:25 AM UTC+1, Graham Dumpleton wrote:
>> The general approach that you use works for me on MacOS X, so I am not sure
>> what you are doing different that is problem and I don’t think should be
>> different for Linux.
>>
>> Instead of using:
>>
>> python setup.py build
>> mkdir -p ${PRODUCT_DIR}/lib/python2.7/site-packages
>> export PYTHONPATH=$PRODUCT_DIR/lib/python2.7/site-packages:$PYTHONPATH
>> python setup.py install --prefix=$PRODUCT_DIR
>> Use a pip style install instead.
>>
>> pip install —prefix=$PRODUCT_DIR modWSGIhttpd-2.4.23.1.tar.gz
>>
>> Graham
>>
>>> On 7 Dec 2016, at 7:57 PM, Michael Graber <michi...@ <>gmail.com
>>> <http://gmail.com/>> wrote:
>>>
>>>
>>> May I kindly ask again regarding the interpretation of the requested
>>> outputs?
>>>
>>> Thanks,
>>> Michael
>>>
>>>
>>>
>>>
>>> On Friday, December 2, 2016 at 11:22:51 AM UTC+1, Michael Graber wrote:
>>>
>>> ok, i included the call for the two commands into the build file debug
>>> steps, in order to investigate in the adequate configuration.
>>>
>>> here is the output:
>>>
>>>
>>> + ls -las /des002/devel/eeups/ci_build_desbuild/Linux64/modWSGI/4.5.7+0/bin
>>> total 0
>>> 0 drwxrwxrwx 2 buildbot desdm 512 Dec 2 04:00 .
>>> 0 drwxrwxrwx 4 buildbot desdm 512 Dec 2 04:00 ..
>>> 0 -rwxrwxrwx 1 buildbot desdm 399 Dec 2 04:00 mod_wsgi-apxs
>>> + echo
>>> /des002/devel/eeups/ci_build_desbuild/Linux64/modWSGI/4.5.7+0/lib/python2.7/site-packages/mod_wsgi_httpd-2.4.23.1-py2.7-linux-x86_64.egg/mod_wsgi_packages/httpd/bin:/des002/devel/eeups/ci_build_desbuild/Linux64/modWSGI/4.5.7+0/bin:/des002/devel/eeups/ci_build_desbuild/Linux64/modWSGIhttpd/2.4.23.1
>>>
>>> <http://2.4.23.1/>+0/bin:/des002/devel/eeups/ci_build_desbuild/Linux64/tcl/8.5.17+0/bin:/des002/devel/eeups/ci_build_desbuild/Linux64/tk/8.5.17+1/bin:/des002/devel/eeups/ci_build_desbuild/Linux64/sqlite/3080002+0/bin:/des002/devel/eeups/ci_build_desbuild/Linux64/python/2.7.9+1/bin:/usr/local/bin:/bin:/usr/bin:/des002/devel/eeups/eups_desbuild/1.2.30/bin
>>> /des002/devel/eeups/ci_build_desbuild/Linux64/modWSGI/4.5.7+0/lib/python2.7/site-packages/mod_wsgi_httpd-2.4.23.1-py2.7-linux-x86_64.egg/mod_wsgi_packages/httpd/bin:/des002/devel/eeups/ci_build_desbuild/Linux64/modWSGI/4.5.7+0/bin:/des002/devel/eeups/ci_build_desbuild/Linux64/modWSGIhttpd/2.4.23.1
>>>
>>> <http://2.4.23.1/>+0/bin:/des002/devel/eeups/ci_build_desbuild/Linux64/tcl/8.5.17+0/bin:/des002/devel/eeups/ci_build_desbuild/Linux64/tk/8.5.17+1/bin:/des002/devel/eeups/ci_build_desbuild/Linux64/sqlite/3080002+0/bin:/des002/devel/eeups/ci_build_desbuild/Linux64/python/2.7.9+1/bin:/usr/local/bin:/bin:/usr/bin:/des002/devel/eeups/eups_desbuild/1.2.30/bin
>>> + echo
>>> /des002/devel/eeups/ci_build_desbuild/Linux64/modWSGI/4.5.7+0/bin/mod_wsgi-apxs
>>> /des002/devel/eeups/ci_build_desbuild/Linux64/modWSGI/4.5.7+0/bin/mod_wsgi-apxs
>>> + which apxs
>>> /des002/devel/eeups/ci_build_desbuild/Linux64/modWSGI/4.5.7+0/lib/python2.7/site-packages/mod_wsgi_httpd-2.4.23.1-py2.7-linux-x86_64.egg/mod_wsgi_packages/httpd/bin/apxs
>>> + which mod_wsgi-apxs
>>> /des002/devel/eeups/ci_build_desbuild/Linux64/modWSGI/4.5.7+0/bin/mod_wsgi-apxs
>>> + mod_wsgi-apxs -q APR_CONFIG
>>> /des002/devel/eeups/ci_build_desbuild/EupsBuildDir/Linux64/modWSGI-4.5.7+0/modWSGIhttpd-2.4.23.1/build/httpd/bin/apr-1-config
>>> + mod_wsgi-apxs -q APU_CONFIG
>>> /des002/devel/eeups/ci_build_desbuild/EupsBuildDir/Linux64/modWSGI-4.5.7+0/modWSGIhttpd-2.4.23.1/build/httpd/bin/apu-1-config
>>> + set +x
>>>
>>>
>>> so it appears as if the location of these two outputs would rather be on
>>> the build path of mod_wsgi-httpd than the install path .. is this a problem?
>>>
>>>
>>>
>>>
>>> the entire build log can again be found at:
>>> http://desbuild.cosmology.illinois.edu/eeups/webservice/dashboard/products/modWSGI/4.5.7%2B0/desbuild/build/build.log
>>>
>>> <http://desbuild.cosmology.illinois.edu/eeups/webservice/dashboard/products/modWSGI/4.5.7%2B0/desbuild/build/build.log>
>>>
>>>
>>>
>>>
>>>
>>> On Friday, December 2, 2016 at 10:50:03 AM UTC+1, Graham Dumpleton wrote:
>>> What does the following output:
>>>
>>> mod_wsgi-apxs -q APR_CONFIG
>>> mod_wsgi-apxs -q APU_CONFIG
>>>
>>>> On 2 Dec 2016, at 8:43 PM, Michael Graber <michi...@gmail.com <>> wrote:
>>>>
>>>>
>>>> yes it does:
>>>>
>>>> -bash-4.1$ ls -la
>>>> /des002/devel/eeups/ci_build_desbuild/Linux64/python/2.7.9+1/bin
>>>> total 48
>>>> drwxr-xr-x 2 buildbot desdm 512 May 25 2016 .
>>>> drwxrwxrwx 6 buildbot desdm 512 May 25 2016 ..
>>>> -rwxrwxrwx 1 buildbot desdm 151 May 25 2016 2to3
>>>> -rwxrwxrwx 1 buildbot desdm 149 May 25 2016 idle
>>>> -rwxrwxrwx 1 buildbot desdm 134 May 25 2016 pydoc
>>>> lrwxrwxrwx 1 buildbot desdm 7 May 25 2016 python -> python2
>>>> lrwxrwxrwx 1 buildbot desdm 14 May 25 2016 python-config ->
>>>> python2-config
>>>> lrwxrwxrwx 1 buildbot desdm 9 May 25 2016 python2 -> python2.7
>>>> lrwxrwxrwx 1 buildbot desdm 16 May 25 2016 python2-config ->
>>>> python2.7-config
>>>> -rwxr-xr-x 1 buildbot desdm 9856 May 25 2016 python2.7
>>>> -rwxr-xr-x 1 buildbot desdm 1737 May 25 2016 python2.7-config
>>>> -rwxrwxrwx 1 buildbot desdm 18597 May 25 2016 smtpd.py
>>>> -bash-4.1$
>>>>
>>>> mi
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Friday, December 2, 2016 at 1:20:33 AM UTC+1, Graham Dumpleton wrote:
>>>> Does this exist:
>>>>
>>>> /des002/devel/eeups/ci_build_desbuild/Linux64/python/2.7.9+1/bin/python
>>>>
>>>> Graham
>>>>
>>>>> On 1 Dec 2016, at 6:55 PM, Michael Graber <michi...@ <>gmail.com
>>>>> <http://gmail.com/>> wrote:
>>>>>
>>>>>
>>>>>
>>>>> ${PRODUCTI_DIR}
>>>>>
>>>>> is
>>>>>
>>>>> /des002/devel/eeups/ci_build_desbuild/Linux64/modWSGI/4.5.7+0
>>>>>
>>>>>
>>>>> here is the requested info:
>>>>>
>>>>>
>>>>> -bash-4.1$ pwd
>>>>> /des002/devel/eeups/ci_build_desbuild/Linux64/modWSGI/4.5.7+0/bin
>>>>> -bash-4.1$ ls -la
>>>>> total 8
>>>>> drwxrwxrwx 2 buildbot desdm 512 Nov 29 02:47 .
>>>>> drwxrwxrwx 4 buildbot desdm 512 Nov 29 02:47 ..
>>>>> -rwxrwxrwx 1 buildbot desdm 399 Nov 29 02:47 mod_wsgi-apxs
>>>>> -bash-4.1$ cat mod_wsgi-apxs
>>>>> #!/des002/devel/eeups/ci_build_desbuild/Linux64/python/2.7.9+1/bin/python
>>>>> # EASY-INSTALL-ENTRY-SCRIPT:
>>>>> 'mod-wsgi-httpd==2.4.23.1','console_scripts','mod_wsgi-apxs'
>>>>> __requires__ = 'mod-wsgi-httpd==2.4.23.1'
>>>>> import sys
>>>>> from pkg_resources import load_entry_point
>>>>>
>>>>> if __name__ == '__main__':
>>>>> sys.exit(
>>>>> load_entry_point('mod-wsgi-httpd==2.4.23.1', 'console_scripts',
>>>>> 'mod_wsgi-apxs')()
>>>>> )
>>>>>
>>>>>
>>>>> thx!
>>>>> michael
>>>>>
>>>>>
>>>>>
>>>>> On Wednesday, November 30, 2016 at 5:49:20 AM UTC+1, Graham Dumpleton
>>>>> wrote:
>>>>> What does:
>>>>>
>>>>> ${PRODUCT_DIR}/bin/mod_wsgi-apxs
>>>>>
>>>>> contain after mod_wsgi-httpd is installed?
>>>>>
>>>>> What are the permissions on the file?
>>>>>
>>>>> Graham
>>>>>
>>>>>> On 29 Nov 2016, at 7:54 PM, Michael Graber <michi...@ <>gmail.com
>>>>>> <http://gmail.com/>> wrote:
>>>>>>
>>>>>>
>>>>>> I introduced the suggested debugging steps. This is its output:
>>>>>>
>>>>>>
>>>>>>
>>>>>> + ls -las
>>>>>> /des002/devel/eeups/ci_build_desbuild/Linux64/modWSGI/4.5.7+0/bin
>>>>>> total 0
>>>>>> 0 drwxrwxrwx 2 buildbot desdm 512 Nov 29 02:47 .
>>>>>> 0 drwxrwxrwx 4 buildbot desdm 512 Nov 29 02:47 ..
>>>>>> 0 -rwxrwxrwx 1 buildbot desdm 399 Nov 29 02:47 mod_wsgi-apxs
>>>>>> + echo
>>>>>> /des002/devel/eeups/ci_build_desbuild/Linux64/modWSGI/4.5.7+0/lib/python2.7/site-packages/mod_wsgi_httpd-2.4.23.1-py2.7-linux-x86_64.egg/mod_wsgi_packages/httpd/bin:/des002/devel/eeups/ci_build_desbuild/Linux64/modWSGI/4.5.7+0/bin:/des002/devel/eeups/ci_build_desbuild/Linux64/modWSGIhttpd/2.4.23.1
>>>>>>
>>>>>> <http://2.4.23.1/>+0/bin:/des002/devel/eeups/ci_build_desbuild/Linux64/tcl/8.5.17+0/bin:/des002/devel/eeups/ci_build_desbuild/Linux64/tk/8.5.17+1/bin:/des002/devel/eeups/ci_build_desbuild/Linux64/sqlite/3080002+0/bin:/des002/devel/eeups/ci_build_desbuild/Linux64/python/2.7.9+1/bin:/usr/local/bin:/bin:/usr/bin:/des002/devel/eeups/eups_desbuild/1.2.30/bin
>>>>>> /des002/devel/eeups/ci_build_desbuild/Linux64/modWSGI/4.5.7+0/lib/python2.7/site-packages/mod_wsgi_httpd-2.4.23.1-py2.7-linux-x86_64.egg/mod_wsgi_packages/httpd/bin:/des002/devel/eeups/ci_build_desbuild/Linux64/modWSGI/4.5.7+0/bin:/des002/devel/eeups/ci_build_desbuild/Linux64/modWSGIhttpd/2.4.23.1
>>>>>>
>>>>>> <http://2.4.23.1/>+0/bin:/des002/devel/eeups/ci_build_desbuild/Linux64/tcl/8.5.17+0/bin:/des002/devel/eeups/ci_build_desbuild/Linux64/tk/8.5.17+1/bin:/des002/devel/eeups/ci_build_desbuild/Linux64/sqlite/3080002+0/bin:/des002/devel/eeups/ci_build_desbuild/Linux64/python/2.7.9+1/bin:/usr/local/bin:/bin:/usr/bin:/des002/devel/eeups/eups_desbuild/1.2.30/bin
>>>>>> + echo
>>>>>> /des002/devel/eeups/ci_build_desbuild/Linux64/modWSGI/4.5.7+0/bin/mod_wsgi-apxs
>>>>>> /des002/devel/eeups/ci_build_desbuild/Linux64/modWSGI/4.5.7+0/bin/mod_wsgi-apxs
>>>>>> + which apxs
>>>>>> /des002/devel/eeups/ci_build_desbuild/Linux64/modWSGI/4.5.7+0/lib/python2.7/site-packages/mod_wsgi_httpd-2.4.23.1-py2.7-linux-x86_64.egg/mod_wsgi_packages/httpd/bin/apxs
>>>>>> + which mod_wsgi-apxs
>>>>>> /des002/devel/eeups/ci_build_desbuild/Linux64/modWSGI/4.5.7+0/bin/mod_wsgi-apxs
>>>>>> + set +x
>>>>>>
>>>>>> .. to me it seems things look ok up the here, no?
>>>>>>
>>>>>>
>>>>>> the entire build log can be found here :
>>>>>>
>>>>>> http://desbuild.cosmology.illinois.edu/eeups/webservice/dashboard/products/modWSGI/4.5.7%2B0/desbuild/build/build.log
>>>>>>
>>>>>> <http://desbuild.cosmology.illinois.edu/eeups/webservice/dashboard/products/modWSGI/4.5.7%2B0/desbuild/build/build.log>
>>>>>>
>>>>>>
>>>>>> thanks,
>>>>>> michael
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Tuesday, November 29, 2016 at 1:49:23 AM UTC+1, Graham Dumpleton
>>>>>> wrote:
>>>>>> Can you add debugging steps between installing mod_wsgi-httpd and
>>>>>> installing mod_wsgi whereby you do:
>>>>>>
>>>>>> set -x
>>>>>>
>>>>>> ls -las ${PRODUCT_DIR}/bin
>>>>>>
>>>>>> echo $PATH
>>>>>> echo $APXS
>>>>>>
>>>>>> which apxs
>>>>>> which mod_wsgi-apxs
>>>>>>
>>>>>> set +x
>>>>>>
>>>>>> BTW. I don’t see in your script output where you are setting APXS. Are
>>>>>> you sure it was set in the script which was run?
>>>>>>
>>>>>> Graham
>>>>>>
>>>>>>> On 28 Nov 2016, at 10:12 PM, Michael Graber <michi...@ <>gmail.com
>>>>>>> <http://gmail.com/>> wrote:
>>>>>>>
>>>>>>>
>>>>>>> Thanks Graham for your reply! .. and sorry for the late response.
>>>>>>>
>>>>>>> So, first of all I get from our conversation so far, that in principle
>>>>>>> you think our approach should work in principle and not be too
>>>>>>> complicated, right?
>>>>>>>
>>>>>>> How can we verify that mod_wsgi-httpd is installed correctly? What
>>>>>>> tests can we do?
>>>>>>> .. we do not get any build errors.
>>>>>>>
>>>>>>> Now I tried your suggestion:
>>>>>>>
>>>>>>> export APXS=${PRODUCT_DIR}/bin/mod_wsgi-apxs
>>>>>>>
>>>>>>>
>>>>>>> .. but again get the same error:
>>>>>>>
>>>>>>> http://desbuild.cosmology.illinois.edu/eeups/webservice/dashboard/products/modWSGI/4.5.7%2B0/desbuild/build/build.log
>>>>>>>
>>>>>>> <http://desbuild.cosmology.illinois.edu/eeups/webservice/dashboard/products/modWSGI/4.5.7%2B0/desbuild/build/build.log>
>>>>>>>
>>>>>>>
>>>>>>> So maybe, indeed, the mod_wsgi-httpd installation is not working
>>>>>>> properly. Again, how can we verify this?
>>>>>>>
>>>>>>> Thanks in advance,
>>>>>>> Michael
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Friday, November 18, 2016 at 2:09:20 AM UTC+1, Graham Dumpleton
>>>>>>> wrote:
>>>>>>> The error you are getting indicates that the mod_wsgi-apxs program was
>>>>>>> not found in the PATH when a search was made when installing mod_wsgi.
>>>>>>> It therefore fell back to trying to use apxs/apr-1-config/apu-1-config
>>>>>>> and the latter were not present.
>>>>>>>
>>>>>>> If you are sure that it is being installed correctly, try instead
>>>>>>> setting:
>>>>>>>
>>>>>>> export APXS=${PRODUCT_DIR}/bin/mod_wsgi-apxs
>>>>>>>
>>>>>>> prior to building mod_wsgi.
>>>>>>>
>>>>>>> Graham
>>>>>>>
>>>>>>>> On 18 Nov 2016, at 3:23 AM, Michael Graber <michi...@ <>gmail.com
>>>>>>>> <http://gmail.com/>> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> So far we've been using the pattern you presented on your series of
>>>>>>>> blog posts (around http://blog.dscpl.com.au/search?q=runmodwsgi
>>>>>>>> <http://blog.dscpl.com.au/search?q=runmodwsgi>) for the deployment of
>>>>>>>> django apps using mod_wsgi-express and the associated django command
>>>>>>>> runmodwsgi.
>>>>>>>>
>>>>>>>> This worked great and we would like to continue to do so. Are there
>>>>>>>> any better options?
>>>>>>>>
>>>>>>>> We are not doing pip install mod_wsgi but rather have to install
>>>>>>>> mod_wsgi through our own package management system.
>>>>>>>> Apache does not come as a standard with our container platform that's
>>>>>>>> why we wanted to install it through mod_wsgi-httpd ..
>>>>>>>>
>>>>>>>> Would you rather recommend using a platform (CentOS7) provided apache
>>>>>>>> version?
>>>>>>>>
>>>>>>>> Thanks a lot for your tools and our help!
>>>>>>>> Michael
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Tuesday, November 15, 2016 at 9:42:38 PM UTC+1, Graham Dumpleton
>>>>>>>> wrote:
>>>>>>>> How are you eventually running mod_wsgi? Are you using
>>>>>>>> mod_wsgi-express, or are you trying to integrate this with your
>>>>>>>> existing system Apache installation?
>>>>>>>>
>>>>>>>> Why aren’t you just using any existing system Apache installation when
>>>>>>>> doing ‘pip install mod_wsgi’, rather than also installing the
>>>>>>>> ‘mod_wsgi-httpd’ package?
>>>>>>>>
>>>>>>>> Graham
>>>>>>>>
>>>>>>>>> On 15 Nov 2016, at 11:08 PM, Michael Graber <michi...@ <>gmail.com
>>>>>>>>> <http://gmail.com/>> wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Hi!
>>>>>>>>>
>>>>>>>>> In our rather astronomy collaboration we are using mod_wsgi to host
>>>>>>>>> some of our django-based webapplications.
>>>>>>>>>
>>>>>>>>> Currently we are in the process of updating to the latest version
>>>>>>>>> (mod_wsgi 4.5.7, mod_wsgi 2.4.23.1). Here I encounter some problems:
>>>>>>>>>
>>>>>>>>> For scientific integrity reasons we have our own package management
>>>>>>>>> system (eups) with our own distributed version of python (2.7.9).
>>>>>>>>> mod_wsgi (and mod_wsgi-httpd) has to be installed through this
>>>>>>>>> package management system and against this python version.
>>>>>>>>> Our substrate os for webapplications (not all platforms need to be
>>>>>>>>> covered here) is typically CentOS7.
>>>>>>>>>
>>>>>>>>> This actually worked fine for mod_wsgi 4.4.13 and mod_wsgi-httpd
>>>>>>>>> 2.4.12.6. I cannot get the latest version to work.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> First, it would be helpful to get general advice if we do anything
>>>>>>>>> unreasonable overall. Here is how we proceed.
>>>>>>>>>
>>>>>>>>> 1. install python 2.7.9 through our package management system. setup
>>>>>>>>> the paths to use our versions.
>>>>>>>>>
>>>>>>>>> 2. i downloaded with 'pip download' the source code for the mod_wsgi
>>>>>>>>> and the mod_wsgi-httpd package. we distribute them through a
>>>>>>>>> fileserver.
>>>>>>>>>
>>>>>>>>> 3. we download these tars to the target machine (centos7).
>>>>>>>>>
>>>>>>>>> 4. we install mod_wsgi-httpd first, basically using python setup.py
>>>>>>>>> build and then install with our prefix
>>>>>>>>>
>>>>>>>>> 5. we set some according CFLAGS and then install mod_wsgi through
>>>>>>>>> python setup.py build and install (prepending configure (setting
>>>>>>>>> --with-apxs accordingly), make was not successful either)
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Please find the build script below.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Does this make sense overall?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Now, this does not work. Even though apparently mod_wsgi-httpd builds
>>>>>>>>> correctly i suspect that we actually already there create a / the
>>>>>>>>> problem. Here is the build log:
>>>>>>>>>
>>>>>>>>> http://desbuild.cosmology.illinois.edu/eeups/webservice/dashboard/products/modWSGI/4.5.7%2B0/desbuild/build/build.log
>>>>>>>>>
>>>>>>>>> <http://desbuild.cosmology.illinois.edu/eeups/webservice/dashboard/products/modWSGI/4.5.7%2B0/desbuild/build/build.log>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Any hints are very much appreciated!
>>>>>>>>> Thanks,
>>>>>>>>> Michael
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> build script:
>>>>>>>>> ---------------------------------------------------------------
>>>>>>>>>
>>>>>>>>> #!/usr/bin/env bash
>>>>>>>>>
>>>>>>>>> wget
>>>>>>>>> http://desbuild.cosmology.illinois.edu/eeups/webservice/resources/modWSGIhttpd/modWSGIhttpd-2.4.23.1.tar.gz
>>>>>>>>>
>>>>>>>>> <http://desbuild.cosmology.illinois.edu/eeups/webservice/resources/modWSGIhttpd/modWSGIhttpd-2.4.23.1.tar.gz>
>>>>>>>>> tar xzf modWSGIhttpd-2.4.23.1.tar.gz
>>>>>>>>> cd modWSGIhttpd-2.4.23.1
>>>>>>>>> python setup.py build
>>>>>>>>>
>>>>>>>>> mkdir -p ${PRODUCT_DIR}/lib/python2.7/site-packages
>>>>>>>>> export PYTHONPATH=$PRODUCT_DIR/lib/python2.7/site-packages:$PYTHONPATH
>>>>>>>>> python setup.py install --prefix=$PRODUCT_DIR
>>>>>>>>>
>>>>>>>>> cd ..
>>>>>>>>>
>>>>>>>>> # now we take care of the modWSGI / mod_wsgi installation
>>>>>>>>> wget $EXTERNAL/$PRODUCT/$PRODUCT-$VERSION.tar.gz
>>>>>>>>> tar xzf $PRODUCT-$VERSION.tar.gz
>>>>>>>>> cd $PRODUCT-$VERSION
>>>>>>>>>
>>>>>>>>> export
>>>>>>>>> CFLAGS="-I${PRODUCT_DIR}/lib/python2.7/site-packages/mod_wsgi_httpd-2.4.23.1-py2.7-linux-x86_64.egg/mod_wsgi_packages/httpd/include"
>>>>>>>>> export CFLAGS="$CFLAGS
>>>>>>>>> -I${PRODUCT_DIR}/lib/python2.7/site-packages/mod_wsgi_httpd-2.4.23.1-py2.7-linux-x86_64.egg/mod_wsgi_packages/httpd/include/apr-1"
>>>>>>>>> export PATH=${PRODUCT_DIR}/bin:${PATH}
>>>>>>>>> export
>>>>>>>>> PATH=${PRODUCT_DIR}/lib/python2.7/site-packages/mod_wsgi_httpd-2.4.23.1-py2.7-linux-x86_64.egg/mod_wsgi_packages/httpd/bin:${PATH}
>>>>>>>>>
>>>>>>>>> #./configure
>>>>>>>>> --with-apxs=${PRODUCT_DIR}//lib/python2.7/site-packages/mod_wsgi_httpd-2.4.23.1-py2.7-linux-x86_64.egg/mod_wsgi_packages/httpd/bin/apxs
>>>>>>>>> #make
>>>>>>>>>
>>>>>>>>> python setup.py build
>>>>>>>>> python setup.py install --prefix=$PRODUCT_DIR
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> You received this message because you are subscribed to the Google
>>>>>>>>> Groups "modwsgi" group.
>>>>>>>>> To unsubscribe from this group and stop receiving emails from it,
>>>>>>>>> send an email to modwsgi+u...@ <>googlegroups.com
>>>>>>>>> <http://googlegroups.com/>.
>>>>>>>>> To post to this group, send email to mod...@ <>googlegroups.com
>>>>>>>>> <http://googlegroups.com/>.
>>>>>>>>> Visit this group at https://groups.google.com/group/modwsgi
>>>>>>>>> <https://groups.google.com/group/modwsgi>.
>>>>>>>>> For more options, visit https://groups.google.com/d/optout
>>>>>>>>> <https://groups.google.com/d/optout>.
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> You received this message because you are subscribed to the Google
>>>>>>>> Groups "modwsgi" group.
>>>>>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>>>>>> an email to modwsgi+u...@googlegroups.com <>.
>>>>>>>> To post to this group, send email to mod...@googlegroups.com <>.
>>>>>>>> Visit this group at https://groups.google.com/group/modwsgi
>>>>>>>> <https://groups.google.com/group/modwsgi>.
>>>>>>>> For more options, visit https://groups.google.com/d/optout
>>>>>>>> <https://groups.google.com/d/optout>.
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> You received this message because you are subscribed to the Google
>>>>>>> Groups "modwsgi" group.
>>>>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>>>>> an email to modwsgi+u...@googlegroups.com <>.
>>>>>>> To post to this group, send email to mod...@googlegroups.com <>.
>>>>>>> Visit this group at https://groups.google.com/group/modwsgi
>>>>>>> <https://groups.google.com/group/modwsgi>.
>>>>>>> For more options, visit https://groups.google.com/d/optout
>>>>>>> <https://groups.google.com/d/optout>.
>>>>>>
>>>>>>
>>>>>> --
>>>>>> You received this message because you are subscribed to the Google
>>>>>> Groups "modwsgi" group.
>>>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>>>> an email to modwsgi+u...@googlegroups.com <>.
>>>>>> To post to this group, send email to mod...@googlegroups.com <>.
>>>>>> Visit this group at https://groups.google.com/group/modwsgi
>>>>>> <https://groups.google.com/group/modwsgi>.
>>>>>> For more options, visit https://groups.google.com/d/optout
>>>>>> <https://groups.google.com/d/optout>.
>>>>>
>>>>>
>>>>> --
>>>>> You received this message because you are subscribed to the Google Groups
>>>>> "modwsgi" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send an
>>>>> email to modwsgi+u...@googlegroups.com <>.
>>>>> To post to this group, send email to mod...@googlegroups.com <>.
>>>>> Visit this group at https://groups.google.com/group/modwsgi
>>>>> <https://groups.google.com/group/modwsgi>.
>>>>> For more options, visit https://groups.google.com/d/optout
>>>>> <https://groups.google.com/d/optout>.
>>>>
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google Groups
>>>> "modwsgi" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send an
>>>> email to modwsgi+u...@googlegroups.com <>.
>>>> To post to this group, send email to mod...@googlegroups.com <>.
>>>> Visit this group at https://groups.google.com/group/modwsgi
>>>> <https://groups.google.com/group/modwsgi>.
>>>> For more options, visit https://groups.google.com/d/optout
>>>> <https://groups.google.com/d/optout>.
>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "modwsgi" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to modwsgi+u...@googlegroups.com <>.
>>> To post to this group, send email to mod...@googlegroups.com <>.
>>> Visit this group at https://groups.google.com/group/modwsgi
>>> <https://groups.google.com/group/modwsgi>.
>>> For more options, visit https://groups.google.com/d/optout
>>> <https://groups.google.com/d/optout>.
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "modwsgi" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to modwsgi+unsubscr...@googlegroups.com
>> <mailto:modwsgi+unsubscr...@googlegroups.com>.
>> To post to this group, send email to modwsgi@googlegroups.com
>> <mailto:modwsgi@googlegroups.com>.
>> Visit this group at https://groups.google.com/group/modwsgi
>> <https://groups.google.com/group/modwsgi>.
>> For more options, visit https://groups.google.com/d/optout
>> <https://groups.google.com/d/optout>.
>
--
You received this message because you are subscribed to the Google Groups
"modwsgi" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to modwsgi+unsubscr...@googlegroups.com.
To post to this group, send email to modwsgi@googlegroups.com.
Visit this group at https://groups.google.com/group/modwsgi.
For more options, visit https://groups.google.com/d/optout.
