[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference turris::c_plus_plus

Title:C++
Notice:Read 1.* and use keywords (e.g. SHOW KEY/FULL KIT_CXX_VAX_VMS)
Moderator:DECCXX::AMARTIN
Created:Fri Nov 06 1987
Last Modified:Thu Jun 05 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:3604
Total number of notes:18242

3522.0. "-Hf does not compile template instantiations" by ANNECY::LAROCHE_P (Ne Suze que si l'on Sancerre) Tue Apr 01 1997 05:25

Hello,

I am using DEC C++ V5.5-004 on Digital UNIX (Alpha) and I am trying to
build a standalone library containing template instantations object.

I followed the advices given in the "Using DCE C++ for Digital Unix Systems"
book, section 5.2.9 and used the -Hf flag to compile template instantiations
(note that I  do NOT use the -c flag.

The problem is that the .cxx and .cmd files related to the template
instantiations are generated in the ./cxx_repository directory, but not the .o
files.

Here is my compilation command:

cxx  -Itmp/  -Iinclude/ -I/cd10/lcom/pbc/include  -I/usr/kits/rogue \
-I/usr/include/cxx -O0 -threads -verbose -g -DDEBUG -Hf \
-o tmp/CLcomServer.o /cd10/lcom/build/src/CLcomServer.cxx

Here is one of the .cxx files generated:

#include <iostream.h>
#include "CLcomTryCatch.hxx"
#include "CLcomExecutorMgr.hxx"
typedef RWTIsvSlist<RWTPtrSlink<CLcomProcess > > __dummy_;

Here is the corresponding .cmd file:

-signed -member_alignment -g2 -O0 -inline none -cpp -show header -show source 
-readonly_strings -ansi_alias -verbose -weak_volatile -thread_safe 
-ptr./cxx_repository -ptsuf.cxx.CXX.C.cc.CC.cpp.c -D_REENTRANT 
-D_PTHREAD_USE_D4 -DDEBUG -Itmp / -Iinclude/ -Icxx_repository/ 
-I/cd10/lcom/pbc/include -I/usr/kits/rogue -I/usr/include/cxx 
-Xsd/cd10/lcom/build/src/

Any idea?

Thanks in advance,
Pierre
T.RTitleUserPersonal
Name		DateLines
3522.1I don't know why this makes a difference...DECC::J_WARDWed Apr 02 1997 09:4813
I think if you change:

-o tmp/CLcomServer.o 

to

-o CLcomServer.o

it will work, i.e. the .o file needs to be specified as ending
up in the current directory.

This seems like a bug in the cxx driver.
3522.2Work around is OK!ANNECY::LAROCHE_PNe Suze que si l&#039;on SancerreWed Apr 02 1997 10:594
Thank you for the work around: I just generate the .o file into the current
directory and then move it to its final destination.

Pierre
3522.3DECCXX::COLEENWed Apr 02 1997 17:007
I reported this as a driver bug in our bug database.  Hopefully,
the workaround will suffice for now.

Thanks for reporting it,
Coleen Phillimore
DEC C++ development
3522.4Any news on this ?FURKA::&quot;[email protected]&quot;Pascal PederivaWed May 21 1997 11:3512
Hi,

I have a customer complaining exactly about the same problem - are there
any news regarding this -Hf problem ?

Thanks for your interest,

Pascal Pederiva
Unix Support Switzerland


[Posted by WWW Notes gateway]
3522.5DECCXX::COLEENTue Jun 03 1997 18:156
Which user?  We have 2 clds on this apparently and 2 people working
on it.  We'll let you know.


Coleen
3522.6DECCXL::KAOWed Jun 04 1997 11:456
Re .0 and .4 
Please verify what is the compiler version that your are using.
It works on my DEC C++ V5.5-004.
Apparently, there is a bug introduced at a later version.

Shi-Jung
3522.7ANNECY::LAROCHE_PNe Suze que si l&#039;on SancerreWed Jun 04 1997 11:5311
re: .4 - Work around given in previous notes works OK.
re: .6 - Versions of cxx compiler and OS are:

# cxx -V:
cxx  (cxx)
DEC C++ V5.5-004 on Digital UNIX (Alpha)
# uname -a
OSF1 arbois.aeo.dec.com V4.0 386 alpha

Pierre
3522.8Using 5.5-004 and 5.5-010FURKA::&quot;[email protected]&quot;Pascal PederivaThu Jun 05 1997 06:0014
Hi,

the customer is using V5.5-010  under Digital Unix 3.2g.
I think I had the same symptoms under 5.5-004 , Du 4.0B
when I tried to reproduce the problem locally.

I got a workaround thru the IPMT which I forwarded to the customer
and await his response.

Thanks,

Pascal Pederiva

[Posted by WWW Notes gateway]
3522.9It has been fixed in V5.6DECCXL::KAOThu Jun 05 1997 09:407
Thanks for all the information.
I have found the problem, and checked in the fix to our code.
The fix will be in our DEC C++ V5.6 future release.

The bug exists on V5.5-004 and later versions too. (It might happen 
on eariler versions. At one time, I had problem to reproduce it 
on V5.5-004.)