🚀 go-pugleaf

In article <9204162048.AA26891@.foxtrot.ccmrc.ucsb.edu.>, doug@FOXTROT.CCMRC.UCSB.EDU (Douglas Scott) writes:
|> I have been struggling to port my IV 2.6 code to IV 3.0.1, using the 2.6-compatible  
|> mode as an interim level of progress.  I have a class in my program called 'File',  
|> which is adapted from the old libg++ library class (which is gone now).  I also use the  
|> still-included class, 'String', from the new libg++.  I was able to get everything to  
|> compile, but got three mysterious link errors:
|> 
|> ld: Undefined symbol 
|> 
|>    _search__C8osStringiiPCci 
|> 
|>    ___6osFile 
|> 
|>    ___opPCc__C8osString 
|> 
|> 
|> After much searching, I finally dicovered that IV 3.0.1 redefines a bunch of libg++  
|> symbols in OS/_defines.h.  Can someone explain why this is done, and how can I get  
|> these symbols resolved?

The general approach is that <library/_defines.h> has preprocessor defines to map
<global library name> to <library prefix><global library name>.  The include file
<library/enter-scope.h> and <library/leave-scope.h> can be used to "open" or "close"
the library scope, which effectively defines or undefines the symbols using the _defines.h
or _undefs.h files.

I don't know why you are getting undefined symbols.  You can use nm on the library .o
files to see what the symbol is getting defined as.