[prev in list] [next in list] [prev in thread] [next in thread]
List: apache-httpd-users
Subject: [users@httpd] Building Apache 2.2.20 "standalone" and the role of server/exports.c
From: John Donnelly <jdonnelly () vmem ! com>
Date: 2015-08-21 21:31:57
Message-ID: D1FD02FB.14157%jdonnelly () vmem ! com
[Download RAW message or body]
Hello.
I am working on a project to update an old version of Apache ( 2.0.65 ) t=
o version 2.2.20 on an PPC embedded Linux platform in a
Cross-compiling environment. This is outside of the autoconfig (./configu=
re) tools +procedure that one would typically use to build Apache.
I am stuck at the linkage phase right now of httpd. I have managed to comp=
ile all of the modules/* and server/*.c but I am not sure what the role o=
f server/exports.c serves in the build . It appears to be generated from an=
awk step in the makefile on a X86 environment. When I generate a exports.c=
in for my build I end getting lots of un-defined references when I link th=
e object files and libs even though the symbols appear in the corresponding=
libapr/libaprutil libraries .
Anyone have experience is building Apache in this type of standalone enviro=
nment outside of autoconfig ?
Suggestions welcomed.
Thank you.
JD
--
[Attachment #3 (text/html)]
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: \
after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, \
sans-serif;"> <div><br>
</div>
<div>Hello.</div>
<div><br>
</div>
<div> I am working on a project to update an old version of Apache ( 2.0.65 ) \
to version 2.2.20 on an PPC embedded Linux platform in a </div> \
<div> Cross-compiling environment. This is outside of the autoconfig \
(./configure) tools +procedure that one would typically use to build \
Apache. </div> <div><br>
</div>
<div> I am stuck at the linkage phase right now of httpd. I have managed to \
compile all of the modules/* and server/*.c but I am not sure what the \
role of server/exports.c serves in the build . It appears to be generated from an awk \
step in the makefile on a X86 environment. When I generate a exports.c in for my \
build I end getting lots of un-defined references when I link the object files and \
libs even though the symbols appear in the corresponding libapr/libaprutil libraries \
.</div> <div><br>
</div>
<div>Anyone have experience is building Apache in this type of standalone environment \
outside of autoconfig ? </div> <div><br>
</div>
<div>Suggestions welcomed.</div>
<div><br>
</div>
<div>Thank you.</div>
<div>JD</div>
<div><br>
</div>
<div>
<div>
<div>-- </div>
<div><br>
</div>
</div>
<div>
<div style="font-family: Consolas;"> </div>
</div>
</div>
</body>
</html>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic