Re: PGI and C++ templates

2005-03-05 Thread Ralf Wildenhues
Hi Jeff, * Jeff Squyres wrote on Sat, Mar 05, 2005 at 01:07:11AM CET: > Can I impose on the good will of a libtool wizard? I could attempt > this myself, but I don't have a good track record mucking around in the > LT source. ;-) Not true. But let's see what we can do.. > Here's the situa

Re: PGI and C++ templates

2005-03-07 Thread Ralf Wildenhues
Sorry to self-followup. Another thing came to mind: * Ralf Wildenhues wrote on Sat, Mar 05, 2005 at 05:10:31PM CET: > * Jeff Squyres wrote on Sat, Mar 05, 2005 at 01:07:11AM CET: > > > You must now do an extra pre-link step to instantiate all the templates > > used in this library, putting all

Re: PGI and C++ templates

2005-03-07 Thread Jeff Squyres
On Mar 5, 2005, at 11:10 AM, Ralf Wildenhues wrote: For each source file in the library, compile it: $ pgCC -c --one_instantiation_per_object $(YOUR_FLAGS) file.cc Can we issue the `--one_instantiation_per_object' for all C++ source, not just the source with templates in it? I don't see a problem w

Re: PGI and C++ templates

2005-03-07 Thread Jeff Squyres
On Mar 7, 2005, at 3:07 AM, Ralf Wildenhues wrote: Achive or build the shared library as before, except you must include the new hidden templates in the Template.dir directory: $ ar qv lib_mylib.a Template.dir/*.o file1.o file2.o etc. At the moment, Template.dir/ is not cleaned by `make clean'. Th

Re: PGI and C++ templates

2005-03-07 Thread trs
Engineering can confirm 1. You should use the --instantiation_dir flag to keep separate instantiation directories for each library. 2. You should always clean the Template.dir with any changes to the associated library templates. regards, dave > On Mar 7, 2005, at 3:07 AM, Ralf Wild

Re: PGI and C++ templates

2005-03-14 Thread Ralf Wildenhues
Hello everyone, This is a status update on "libtool/pgi/C++ with templates". Skip to the [ Interesting part ] if you are in a hurry. * [EMAIL PROTECTED] wrote on Mon, Mar 07, 2005 at 11:06:50PM CET: > Engineering can confirm > > > 1. You should use the --instantiation_dir flag to >keep sepa

Re: PGI and C++ templates

2005-03-15 Thread Jeff Squyres
On Mar 14, 2005, at 1:49 PM, Ralf Wildenhues wrote: I've long since added my own m4 to my configure scripts to see if the C++ compiler uses a template subdirectory, and if so, add it to CLEANFILES. Can you be bothered to share it with us? Has it hung enough to be considered for Automake? Sure -- i

Re: PGI and C++ templates

2005-03-15 Thread Ralf Wildenhues
Sorry for the self-reply, * Ralf Wildenhues wrote on Mon, Mar 14, 2005 at 07:49:00PM CET: > > This is a status update on "libtool/pgi/C++ with templates". Now here's an improved patch against branch-2-0. Should work for both static and shared uninstalled libraries plus programs linked against t

Re: PGI and C++ templates

2005-03-16 Thread Markus Christen
hi Ralf Wildenhues wrote: Sorry for the self-reply, * Ralf Wildenhues wrote on Mon, Mar 14, 2005 at 07:49:00PM CET: This is a status update on "libtool/pgi/C++ with templates". Now here's an improved patch against branch-2-0. Should work for both static and shared uninstalled libraries plu

Re: PGI and C++ templates

2005-03-17 Thread trs
Ralf, Jeff, and everyone, We looked at what you did, and it appears you understand how things were put together. However, the 6.0 release is about to come out, and the template instantiation mechanism has been totally rewritten for linux targets. All of the template related compiler switches

Re: PGI and C++ templates

2005-03-17 Thread Ralf Wildenhues
Hi Dave, others, * [EMAIL PROTECTED] wrote on Fri, Mar 18, 2005 at 02:08:41AM CET: > Ralf, Jeff, and everyone, > > We looked at what you did, and it appears you understand how > things were put together. > > However, the 6.0 release is about to come out, and > the template instantiation mech