www.digitalmars.com         C & C++   DMDScript  

digitalmars.D.learn - about dsss and "blablablah_initZ previous definition different"

reply Bill Baxter <dnewsgroup billbaxter.com> writes:
I started getting this when I import a given module from two different 
modules.  I have found that I *don't* get the error if I use dsss, but I 
*do* get it if I use rebuild directly.

Gregor if you're reading this, is this the error that you were talking 
about caused you to switch to 1-file-at-a-time compilation in dsss?  Is 
that why dsss is working but rebuild is not?   Is there some way to make 
rebuild to the one-at-a-time thing so that I can use rebuild directly?


For reference here's the full error I'm getting from importing the 
TriMesh_ArrayKernelT file in two different modules:

objs\OpenMesh-Core-Mesh-TriMesh_ArrayKernelT.obj(OpenMesh-Core-Mesh-T
iMesh_ArrayKernelT) 
  Offset 009EFH Record Type 0091
  Error 1: Previous Definition Different : 
_D8OpenMesh4Core4Mesh15FinalMeshItemsT67__T15FinalMeshItemsTTS8OpenMesh4Core4Mesh6Traits13DefaultTraitsVb1Z15FinalMeshItemsT4Refs6__initZ
objs\OpenMesh-Core-Mesh-TriMesh_ArrayKernelT.obj(OpenMesh-Core-Mesh-T
iMesh_ArrayKernelT) 
  Offset 2AD86H Record Type 0091
  Error 1: Previous Definition Different : 
_D8OpenMesh4Core4Mesh15FinalMeshItemsT67__T15FinalMeshItemsTTS8OpenMesh4Core4Mesh6Traits13DefaultTraitsVb1Z15FinalMeshItemsT7ITraits6__initZ


--bb
Aug 31 2007
parent reply Bill Baxter <dnewsgroup billbaxter.com> writes:
Bill Baxter wrote:
 I started getting this when I import a given module from two different 
 modules.  I have found that I *don't* get the error if I use dsss, but I 
 *do* get it if I use rebuild directly.
 
 Gregor if you're reading this, is this the error that you were talking 
 about caused you to switch to 1-file-at-a-time compilation in dsss?  Is 
 that why dsss is working but rebuild is not?   Is there some way to make 
 rebuild to the one-at-a-time thing so that I can use rebuild directly?
Erm... well now the error has gone away with rebuild too. I'm not sure where it went. But this sounds a lot like the weird, hard-to-resolve linker order problems that other people have mentioned here. --bb
Aug 31 2007
parent Downs <default_357-line yahoo.de> writes:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Bill Baxter wrote:
 Erm... well now the error has gone away with rebuild too.
 I'm not sure where it went.
It went thataway!! :points: .. Sorry, had to be said :) --downs -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG2MN2pEPJRr05fBERAqNSAJ9MPQm3RdqfoGaPzdwwCbrXqJdmeACgisUv RBj5jCfsAj4da1qcJNi/9LE= =8V1q -----END PGP SIGNATURE-----
Aug 31 2007