jdg117 at elvis
Jan 28, 2011, 7:47 AM
Views: 278
Permalink
|
In message <B175E5DAA6BE4F4896AD6A8AA534B18701EDE9CF0E [at] AD-MAILBOX01>, =?
iso-8859-1?Q?Kasper_L=F8vschall?= writes:
>Also configuring the runtime linking environment under Solaris 10 often helps
>a lot along with LDFLAGS:
>
>> crle -u -l /usr/sfw/lib
>> crle -u -l /usr/local/lib
If you add the -R flag to the linker (or not set any runtime paths
with -R and instead set them with the LD_RUN_PATH environment) then
you shouldn't need to kludge the Solaris system or user runtime link
environment.
My notes for building 64-bit modperl with httpd 2.2 remind me to
check these build files:
# edit apr_rules.mk and config_vars.mk in /opt/apache2/build
# add "-m64 -xO3" to EXTRA_CFLAGS and "-m64" EXTRA_LDFLAGS
# confirm "-m64 -L/usr/sfw/lib/64 -R/usr/sfw/lib/64"
# edit apr-1-config and apu-1-config in /opt/apache2/bin
# add the same to CFLAGS and LDFLAGS
# confirm "-m64 -L/usr/sfw/lib/64 -R/usr/sfw/lib/64"
BTW with 32-bit Solaris builds one needs to be dilligent about
building httpd and Perl the same as either largefile(5) or not
or modperl will core.
John
groenveld [at] acm
|
Re: VS: build of libapreq2 fails