Re: compatibility with C++ modules
William A. Rowe, Jr. [EMAIL PROTECTED] writes: Doesn't an option --c-plus-plus make more sense than a platform specific link foo option? Shouldn't we just extend libtool to deal with the platform specifics, g++ or whatnot, depending on what's required to support stl and other specifics? extend libtool? gross :) -- Jeff Trawick | [EMAIL PROTECTED] Born in Roswell... married an alien...
Re: compatibility with C++ modules
Andy Cutright [EMAIL PROTECTED] writes: hi, so could you possibly speak those unspeakable hacks you've made to apache to run c++ modules on hp? we're trying to get a c++ module linked into 2.0.39. any help would be appreciated. we can take this particular aspect of the discussion out of this forum, if you'd prefer, cheers andy really ugly... save build output in log file (with LTFLAGS=' ' so the commands issued by libtool are saved) and re-issue the relink of httpd using aCC instead of cc (find the command in the log file and mangle it) note that Apache binbuilds are broken on HP-UX... in the same relink I added the +s loader option (to respect loader environment variable) and converted /path/to/libaprutil.a /path/to/libexpat.a /path/to/libapr.a into -L/path/to -laprutil -lexpat -lapr so that the libraries are found dynamically. Obviously this needs to go in the real Apache build but I didn't have time to do the right thing. -- Jeff Trawick | [EMAIL PROTECTED] Born in Roswell... married an alien...
RE: compatibility with C++ modules
For those interested, on HP-UX, to get a program written in C to recognize C++ objects, the c-program has to be linked with : ON IA64 : -lCsup -lunwind ON PA-RISC : cpprt0_stub.o, -lcl $ cat cpprt0_stub.s .code ; stubs for static constructors in a.out .export __StaticCtorTable_Start,data .export __StaticCtorTable_End,data __StaticCtorTable_Start __StaticCtorTable_End .data ; stubs for static constructors in a.out, compiled with +z/+Z .export __ZStaticCtorTable_Start,data .export __ZStaticCtorTable_End,data __ZStaticCtorTable_Start __ZStaticCtorTable_End -- $ cc -c +z cpprt0_stub.s -Madhu -Original Message- From: John K.Sterling [mailto:[EMAIL PROTECTED]] Sent: Saturday, September 07, 2002 4:34 PM To: [EMAIL PROTECTED] Subject: Re: compatibility with C++ modules On Friday, September 6, 2002, at 04:53 PM, Andy Cutright wrote: hi, so could you possibly speak those unspeakable hacks you've made to apache to run c++ modules on hp? we're trying to get a c++ module linked into 2.0.39. any help would be appreciated. we can take this particular aspect of the discussion out of this forum, if you'd prefer, as mentioned earlier in the thread, http://sourceforge.net/projects/modcplusplus/ can be of some help. It allows you to simply compile your c++ handlers into a separate so that doesn't contain any apache module stuffs also has some example makefiles etc. which may help. sterling
Re: compatibility with C++ modules
On Friday, September 6, 2002, at 04:53 PM, Andy Cutright wrote: hi, so could you possibly speak those unspeakable hacks you've made to apache to run c++ modules on hp? we're trying to get a c++ module linked into 2.0.39. any help would be appreciated. we can take this particular aspect of the discussion out of this forum, if you'd prefer, as mentioned earlier in the thread, http://sourceforge.net/projects/modcplusplus/ can be of some help. It allows you to simply compile your c++ handlers into a separate so that doesn't contain any apache module stuffs also has some example makefiles etc. which may help. sterling
Re: compatibility with C++ modules
So I haven't really looked into how it works, but have you looked at mod_cplusplus? http://sourceforge.net/projects/modcplusplus/ Ryan On 6 Sep 2002, Jeff Trawick wrote: At about the same time recently that I was doing horrible, uncommittable hacks to the build to get Apache 2.0 to support C++ modules on HP-UX, somebody wrote a PR against Apache 1.3 pointing out the same issue I encountered: If httpd is to properly support C++ modules, it may need to be linked with something other than the C compiler front-end, depending on the compiler and the platform. Though we probably don't want to be in the business of pretending to support C++ modules in general, they certainly work with Apache on some platforms and we could at least make it simple for the user to specify the command to invoke to link httpd. This would default to the C compiler, but could be forced by the user to be g++ or aCC or whatever. ? --with-httpd-linker=g++ ? -- ___ Ryan Bloom [EMAIL PROTECTED] 550 Jean St Oakland CA 94610 ---
Re: compatibility with C++ modules
On Fri, Sep 06, 2002 at 11:55:17AM -0400, Jeff Trawick wrote: Though we probably don't want to be in the business of pretending to support C++ modules in general, they certainly work with Apache on some platforms and we could at least make it simple for the user to specify the command to invoke to link httpd. This would default to the C compiler, but could be forced by the user to be g++ or aCC or whatever. ? --with-httpd-linker=g++ ? LD=g++ ./configure ... ?? (I wondered why this didn't Just Work last time I tried it a few months ago, and stuck it on my todo list to fix it...) -aaron
Re: compatibility with C++ modules
[EMAIL PROTECTED] writes: So I haven't really looked into how it works, but have you looked at mod_cplusplus? http://sourceforge.net/projects/modcplusplus/ just took a look, seems neat -- Jeff Trawick | [EMAIL PROTECTED] Born in Roswell... married an alien...
Re: compatibility with C++ modules
Aaron Bannert [EMAIL PROTECTED] writes: On Fri, Sep 06, 2002 at 11:55:17AM -0400, Jeff Trawick wrote: Though we probably don't want to be in the business of pretending to support C++ modules in general, they certainly work with Apache on some platforms and we could at least make it simple for the user to specify the command to invoke to link httpd. This would default to the C compiler, but could be forced by the user to be g++ or aCC or whatever. ? --with-httpd-linker=g++ ? LD=g++ ./configure ... ?? definitely a more appropriate user interface, though it seems optimal not to bring any C++ rtl init/term logic into ab, htpasswd, and friends since it would only be necessary for httpd (I wondered why this didn't Just Work last time I tried it a few months ago, and stuck it on my todo list to fix it...) rules.mk is why it doesn't Just Work :) LINK = $(LIBTOOL) --mode=link $(COMPILE) $(LT_LDFLAGS) $(ALL_LDFLAGS) -o $@ -- Jeff Trawick | [EMAIL PROTECTED] Born in Roswell... married an alien...
Re: compatibility with C++ modules
hi, so could you possibly speak those unspeakable hacks you've made to apache to run c++ modules on hp? we're trying to get a c++ module linked into 2.0.39. any help would be appreciated. we can take this particular aspect of the discussion out of this forum, if you'd prefer, cheers andy Jeff Trawick wrote: At about the same time recently that I was doing horrible, uncommittable hacks to the build to get Apache 2.0 to support C++ modules on HP-UX, somebody wrote a PR against Apache 1.3 pointing out the same issue I encountered: If httpd is to properly support C++ modules, it may need to be linked with something other than the C compiler front-end, depending on the compiler and the platform. -- buy the buddha a beer tell him to move on to the next town -- Borland -- Enabling a new digital world where our customers have the freedom of choice to develop, deploy, and integrate applications across the enterprise and the Internet. http://www.borland.com This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately and permanently delete the original and any copy of any e-mail and any printout thereof.
Re: compatibility with C++ modules
At 11:27 AM 9/6/2002, Jeff Trawick wrote: Aaron Bannert [EMAIL PROTECTED] writes: On Fri, Sep 06, 2002 at 11:55:17AM -0400, Jeff Trawick wrote: Though we probably don't want to be in the business of pretending to support C++ modules in general, they certainly work with Apache on some platforms and we could at least make it simple for the user to specify the command to invoke to link httpd. This would default to the C compiler, but could be forced by the user to be g++ or aCC or whatever. ? --with-httpd-linker=g++ ? LD=g++ ./configure ... ?? definitely a more appropriate user interface, though it seems optimal not to bring any C++ rtl init/term logic into ab, htpasswd, and friends since it would only be necessary for httpd (I wondered why this didn't Just Work last time I tried it a few months ago, and stuck it on my todo list to fix it...) rules.mk is why it doesn't Just Work :) LINK = $(LIBTOOL) --mode=link $(COMPILE) $(LT_LDFLAGS) $(ALL_LDFLAGS) -o $@ Doesn't an option --c-plus-plus make more sense than a platform specific link foo option? Shouldn't we just extend libtool to deal with the platform specifics, g++ or whatnot, depending on what's required to support stl and other specifics? Bill
