> On 12 May 2016, at 9:09 PM, Chanki Gogia <[email protected]> wrote:
>
> It had worked now. I have reinstalled python3.4.2, apache2.4.12 and
> mod_wsgi4.4.2 and again done similar steps and it worked.
>
> Error logs contains mod_wsgi configured line
I actually stumbled today across another way of possibly solving this whole
problem of not finding the correct library. I can’t remember if I have seen
this feature in Apache before and forgot, or if I have totally overlooked it
until now.
Apache has a LoadFile directive which can be given a path to a loadable object
file that can be force linked into Apache at startup, before any other Apache
modules are loaded.
One can possibly say:
LoadFile /opt/rh/rh-python34/root/lib64/libpython3.4m.so.rh-python34-1.0
Would just need to check that loading by path name like this, is enough to
satisfy the dynamic link loader or not. If it isn’t and wrong library would
have been loaded, generally the first library loaded to define a symbol still
wins. Although in this case the dynamic linker wasn’t finding the library,
which is where not sure if this will work or not.
I will need to experiment with this some time or suggest it be tried the next
time see someone with this sort of problem.
Graham
--
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/modwsgi.
For more options, visit https://groups.google.com/d/optout.
