httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 32930] - apxs cannot run from DESTDIR specified in 'make DESTDIR=xyz install'
Date Wed, 05 Jan 2005 06:35:28 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=32930>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=32930





------- Additional Comments From johnk@nstc.nec.com.au  2005-01-05 07:35 -------
(In reply to comment #2)
> You can munge it manually if you really need be; it probably just needs
> the path to config_vars.mk fixing.

I tried. The prefix path is embedded in a moderate number of places in the
perl code of apxs. If I remember rightly, it is all through config_vars.mk
itself. It became a losing proposition.

The next suggestion occurred to me also. It is very pragmatic (tick).

> Alternatively, to generate the binary modules simply build them against
> the properly installed httpd on the build host.

This has the 'down side' of requiring a 'prefix correct' installation of
a 'bootstrap version' what you are currently building (httpd) in place on
the build host.
However after bootstrapping the host things should go smoothly until any
tool in the 'prefix correct' installation and required by a build becomes
out of date.

Unfortunately for me doing this in our development shop has its problems.
Oh well.

> ... not worth increasing the complexity of the build system to cope with
> this obscure case.

The complexity would all be in apxs? It may simply consist of a 'destdir'
value that is prepended to any value normally initialised to the '--prefix'
dir when apxs perl code is generated by the build.

The destdir value could be provided by a command line option, and default
to the empty string if not provided.

Without looking at all the apxs perl this idea could be all wrong, but it
has a shot.

Comment #1 is valid, but doesn't it mean that, on a mod_ by mod_ basis, you
must manually perform the work bundled in apxs?

Presumably http://httpd.apache.org/docs-2.0/dso.html contains all I need to
know.

Does it mean the underlying lib???.so for the mod_??? must be prepared with
libtool rather than just ld? (this question displays ignorance of libtool)


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message