I've also tried to test setting the LD_LIBRARY_PATH after connecting to the console of the application.
 
console-3.2#export LD_LIBRARY_PATH=/usr/lib:$LD_LIBRARY_PATH
 
However after doing that, everytime i run any application I get a "Segmentation Fault" error.
 
When I change it back to
 
console-3.2#export  LD_LIBRARY_PATH=/lib
 
all normal applications work ok (ls, ldd, etc.).
 
I've run ldd on the AXP to my webserver (lighttpd) and it shows the following.
 
console-3.2#ldd /usr/sbin/lighttpd
/usr/sbin/lighttpd: /lib/libc.so.6: version "GLIBC_2.7" not found (required by /usr/lib/libcrypto.so.0.9.8)
 
All the library dependencies (from the development machine, OpenSuse11) is copied in the AXP packages in /usr/lib .
 
I've followed the pdf to modify the startup script to load the processes from the newer glibc. My startup script is as follows:
 

#! /bin/sh
# Copyright (c) 1995-2004 SUSE Linux AG, Nuernberg, Germany.
# All rights reserved.
#
# Author: Kurt Garloff
# Please send feedback to http://www.suse.de/feedback/
#
# /etc/init.d/lighttpd
#   and its symbolic link
# /(usr/)sbin/rclighttpd
#
#    This program is free software; you can redistribute it and/or modify 
#    it under the terms of the GNU General Public License as published by 
#    the Free Software Foundation; either version 2 of the License, or 
#    (at your option) any later version. 
# 
#    This program is distributed in the hope that it will be useful, 
#    but WITHOUT ANY WARRANTY; without even the implied warranty of 
#    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the 
#    GNU General Public License for more details. 
# 
#    You should have received a copy of the GNU General Public License 
#    along with this program; if not, write to the Free Software 
#    Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
#
# Template system startup script for some example service/daemon lighttpd
#
# LSB compatible service control script; see http://www.linuxbase.org/spec/
# 
# Note: This template uses functions rc_XXX defined in /etc/rc.status on
# UnitedLinux (UL) based Linux distributions. If you want to base your 
# script on this template and ensure that it works on non UL based LSB 
# compliant Linux distributions, you either have to provide the rc.status
# functions from UL or change the script to work without them.
#
### BEGIN INIT INFO
# Provides:          lighttpd
# Required-Start:    $syslog $remote_fs
# Should-Start: $time ypbind sendmail
# Required-Stop:     $syslog $remote_fs
# Should-Stop: $time ypbind sendmail
# Default-Start:     3 5
# Default-Stop:      0 1 2 6
# Short-Description: lighttpd 
# Description:       Start lighttpd 
### END INIT INFO
# 
# Any extensions to the keywords given above should be preceeded by 
# X-VendorTag- (X-UnitedLinux- X-SuSE- for us) according to LSB.
# 
# Notes on Required-Start/Should-Start:
# * There are two different issues that are solved by Required-Start
#    and Should-Start
# (a) Hard dependencies: This is used by the runlevel editor to determine
#     which services absolutely need to be started to make the start of
#     this service make sense. Example: nfsserver should have
#     Required-Start: $portmap
#     Also, required services are started before the dependent ones.
#     The runlevel editor will warn about such missing hard dependencies
#     and suggest enabling. During system startup, you may expect an error,
#     if the dependency is not fulfilled.
# (b) Specifying the init script ordering, not real (hard) dependencies.
#     This is needed by insserv to determine which service should be
#     started first (and at a later stage what services can be started
#     in parallel). The tag Should-Start: is used for this.
#     It tells, that if a service is available, it should be started
#     before. If not, never mind.
# * When specifying hard dependencies or ordering requirements, you can 
#   use names of services (contents of their Provides: section)
#   or pseudo names starting with a $. The following ones are available
#   according to LSB (1.1):
# $local_fs all local file systems are mounted
# (most services should need this!)
# $remote_fs all remote file systems are mounted
# (note that /usr may be remote, so
# many services should Require this!)
# $syslog system logging facility up
# $network low level networking (eth card, ...)
# $named hostname resolution available
# $netdaemons all network daemons are running
#   The $netdaemons pseudo service has been removed in LSB 1.2.
#   For now, we still offer it for backward compatibility.
#   These are new (LSB 1.2):
# $time the system time has been set correctly
# $portmap SunRPC portmapping service available
#   UnitedLinux extensions:
# $ALL indicates that a script should be inserted
# at the end
# * The services specified in the stop tags 
#   (Required-Stop/Should-Stop)
#   specify which services need to be still running when this service
#   is shut down. Often the entries there are just copies or a subset 
#   from the respective start tag.
# * Should-Start/Stop are now part of LSB as of 2.0,
#   formerly SUSE/Unitedlinux used X-UnitedLinux-Should-Start/-Stop.
#   insserv does support both variants.
# * X-UnitedLinux-Default-Enabled: yes/no is used at installation time
#   (%fillup_and_insserv macro in %post of many RPMs) to specify whether
#   a startup script should default to be enabled after installation.
#   It's not used by insserv.
#
# Note on runlevels:
# 0 - halt/poweroff 6 - reboot
# 1 - single user 2 - multiuser without network exported
# 3 - multiuser w/ network (text mode)  5 - multiuser w/ network and X11 (xdm)
# 
# Note on script names:
# http://www.linuxbase.org/spec/refspecs/LSB_1.3.0/gLSB/gLSB/scrptnames.html
# A registry has been set up to manage the init script namespace.
# http://www.lanana.org/
# Please use the names already registered or register one or use a
# vendor prefix.
 
 
# Check for missing binaries (stale symlinks should not happen)
# Note: Special treatment of stop for LSB conformance
LIGHTTPD_BIN=/usr/sbin/lighttpd
test -x $LIGHTTPD_BIN || { echo "$LIGHTTPD_BIN not installed"; 
if [ "$1" = "stop" ]; then exit 0;
else exit 5; fi; }
 
# Check for existence of needed config file and read it
LIGHTTPD_CONFIG=/etc/sysconfig/lighttpd
test -r $LIGHTTPD_CONFIG || { echo "$LIGHTTPD_CONFIG not existing";
if [ "$1" = "stop" ]; then exit 0;
else exit 6; fi; }
 
# Read config
. $LIGHTTPD_CONFIG
 
# Source LSB init functions
# providing start_daemon, killproc, pidofproc, 
# log_success_msg, log_failure_msg and log_warning_msg.
# This is currently not used by UnitedLinux based distributions and
# not needed for init scripts for UnitedLinux only. If it is used,
# the functions from rc.status should not be sourced or used.
#. /lib/lsb/init-functions
 
# Shell functions sourced from /etc/rc.status:
#      rc_check         check and set local and overall rc status
#      rc_status        check and set local and overall rc status
#      rc_status -v     be verbose in local rc status and clear it afterwards
#      rc_status -v -r  ditto and clear both the local and overall rc status
#      rc_status -s     display "skipped" and exit with status 3
#      rc_status -u     display "unused" and exit with status 3
#      rc_failed        set local and overall rc status to failed
#      rc_failed <num>  set local and overall rc status to <num>
#      rc_reset         clear both the local and overall rc status
#      rc_exit          exit appropriate to overall rc status
#      rc_active        checks whether a service is activated by symlinks
. /etc/rc.status
 
# Reset status of this service
rc_reset
 
# Return values acc. to LSB for all commands but status:
# 0  - success
# 1       - generic or unspecified error
# 2       - invalid or excess argument(s)
# 3       - unimplemented feature (e.g. "reload")
# 4       - user had insufficient privileges
# 5       - program is not installed
# 6       - program is not configured
# 7       - program is not running
# 8--199  - reserved (8--99 LSB, 100--149 distrib, 150--199 appl)
# 
# Note that starting an already running service, stopping
# or restarting a not-running service as well as the restart
# with force-reload (in case signaling is not supported) are
# considered a success.
 
case "$1" in
    start)
echo -n "Starting lighttpd "
## Start daemon with startproc(8). If this fails
## the return value is set appropriately by startproc.
umask ${LIGHTTPD_UMASK:-077}
/usr/lib/ld-linux.so.2 --library-path /usr/lib startproc -e $LIGHTTPD_BIN $LIGHTTPD_PARAMS
 
# Remember status and be verbose
rc_status -v
;;
    stop)
echo -n "Shutting down lighttpd "
## Stop daemon with killproc(8) and if this fails
## killproc sets the return value according to LSB.
 
/usr/lib/ld-linux.so.2 --library-path /usr/lib killproc -TERM $LIGHTTPD_BIN
 
# Remember status and be verbose
rc_status -v
;;
    try-restart|condrestart)
## Do a restart only if the service was active before.
## Note: try-restart is now part of LSB (as of 1.9).
## RH has a similar command named condrestart.
if test "$1" = "condrestart"; then
echo "${attn} Use try-restart ${done}(LSB )${attn} rather than condrestart ${warn}(RH)${norm}"
fi
$0 status
if test $? = 0; then
$0 restart
else
rc_reset # Not running is not a failure.
fi
# Remember status and be quiet
rc_status
;;
    restart)
## Stop the service and regardless of whether it was
## running or not, start it again.
$0 stop
$0 start
 
# Remember status and be quiet
rc_status
;;
    force-reload)
## Signal the daemon to reload its config. Most daemons
## do this on signal 1 (SIGHUP).
## If it does not support it, restart.
 
echo -n "Reload service lighttpd "
## if it supports it:
/usr/lib/ld-linux.so.2 --library-path /usr/lib killproc -HUP $LIGHTTPD_BIN
#touch /var/run/lighttpd.pid
rc_status -v
 
## Otherwise:
#$0 try-restart
#rc_status
;;
    reload)
## Like force-reload, but if daemon does not support
## signaling, do nothing (!)
 
# If it supports signaling:
echo -n "Reload service lighttpd "
/usr/lib/ld-linux.so.2 --library-path /usr/lib killproc -HUP $LIGHTTPD_BIN
#touch /var/run/lighttpd.pid
rc_status -v

## Otherwise if it does not support reload:
#rc_failed 3
#rc_status -v
;;
    status)
echo -n "Checking for service lighttpd "
## Check status with checkproc(8), if process is running
## checkproc will return with exit status 0.
 
# Return value is slightly different for the status command:
# 0 - service up and running
# 1 - service dead, but /var/run/  pid  file exists
# 2 - service dead, but /var/lock/ lock file exists
# 3 - service not running (unused)
# 4 - service status unknown :-(
# 5--199 reserved (5--99 LSB, 100--149 distro, 150--199 appl.)

# NOTE: checkproc returns LSB compliant status values.
/usr/lib/ld-linux.so.2 --library-path /usr/lib checkproc $LIGHTTPD_BIN
# NOTE: rc_status knows that we called this init script with
# "status" option and adapts its messages accordingly.
rc_status -v
;;
    probe)
## Optional: Probe for the necessity of a reload, print out the
## argument to this init script which is required for a reload.
## Note: probe is not (yet) part of LSB (as of 1.9)
 
test /etc/lighttpd/lighttpd.conf -nt /var/run/lighttpd.pid && echo reload
;;
    *)
echo "Usage: $0 {start|stop|status|try-restart|restart|force-reload|reload|probe}"
exit 1
;;
esac
rc_exit

Hello Stan,
It looks like your end goal is to install lighttpd within an AXP application.  Is this correct?  If so, below is some information that may help you.
 
The document you reference above is applicable for AXP 1.0 and 1.1, so I would recommend a different  approach when using AXP 1.5 or later.  There are two feasable options, both have their own advantages.

Option 1:  Use the AXP Reference OS
Assuming the goal is to get lighttpd working, this is the easiest method.  The AXP Reference OS provides GLIBC v2.5-24.  In addition, AXP 1.5 provides a means to install CentOS 5.2 RPM¿s into an application.  To do so, do the following: 

1.       Download the CentOS 5 lighttpd RPM and all RPMs it depends on.  I used http://rpm.pbone.net to find these RPMs.  They are listed below.
    cyrus-sasl-lib-2.1.22-5.el5.i386.rpm
    openldap-2.3.43-3.el5.i386.rpm
    lighttpd-1.4.19-2.el5.kb.i386.rpm
    redhat-logos-4.9.99-11.el5.centos.noarch.rpm
    lua-5.1.2-1.el5.kb.i386.rpm

2.       On your workstation environment, create a directory called <source-dir>/third_party_rpms_repository, where <source-dir> is the source directory you specify to the pkg_build.sh script when building your application.  Put the above RPMs in here.

3.       Create a file called <source-dir>/third_party_rpms_repository/rpm_priority.dat.  This file provides AXP with a depdendency order when installing your RPMs.  My file looks like the following:
 
    > cat build/third_party_rpms_repository/rpm_priority.dat
    :cyrus-sasl-lib-2.1.22-5.el5.i386.rpm:1:
    :openldap-2.3.43-3.el5.i386.rpm:2:
    :lua-5.1.2-1.el5.kb.i386.rpm:3:
    :redhat-logos-4.9.99-11.el5.centos.noarch.rpm:3:
    :lighttpd-1.4.19-2.el5.kb.i386.rpm:4:
 
4.       Package your application as you normally would.  For reference, my application looks like this:
    > ls -1R
    .:
    bin 
    third_party_rpms_repository
 
    ./bin:
    post-install.sh
 
    ./third_party_rpms_repository:
    cyrus-sasl-lib-2.1.22-5.el5.i386.rpm
    lighttpd-1.4.19-2.el5.kb.i386.rpm
    lua-5.1.2-1.el5.kb.i386.rpm
    openldap-2.3.43-3.el5.i386.rpm
    redhat-logos-4.9.99-11.el5.centos.noarch.rpm
    rpm_priority.dat

5.       Install your application.

6.       Once installation is complete, you should be able to connect to the console of your application and run lighttpd.  To run using the default configuration, issue the command:

    (exec-lighttpd)# connect console
    bash-3.2# /usr/sbin/lighttpd -f /etc/lighttpd/lighttpd.conf

7.       You should now have lighttpd running inside your application.
 

Option 2:  Create an AXP User-Defined-Environment
Use this option if your application is dependent on the OpenSUSE environment.  AXP supports generating any linux environment and installing it within an application.  This option is available so you are not limited to the CentOS 5.2 environment AXP provides by default.  For more information on this, refer to the AXP developers guide.  To develop an OpenSUSE environment, you can download OpenSUSE RPM¿s and install them just as described in option 1.