CVS build error with new sort

[John Swensen]

On Feb 7, 2008, at 12:24 PM, Thomas Treichl wrote:

> Thomas Treichl schrieb:
> Hi,
>
> I'm back with my problem and I did some analysis of the error  
> output. I can see that there exactly are 4 conflicts producing 1000  
> lines of 'ld: multiple definitions of symbol'. The conflicts are  
> with the files
>
>  sparse-sort.cc <-> Array-i.cc
>  Array-i.cc <-> Array-so.cc
>  Array-C.cc <-> Sparse-C.cc
>  Array-b.cc <-> Sparse-b.cc
>
> I was able to reduce the problem to 3 conflicts by hard doing a
>
>  #undef HAVE_LONG_LONG_INT
>
> in Array-i.cc. So there is no conflict left anymore in Array-i.cc <- 
> > Array-so.cc and number of error outputs reduced to about 500  
> lines. Does this make any sense to you?
>
> The other three conflicts are still there but I can only try some  
> things that I actually don't really understand. They all have to do  
> with 'sort', once again posting some of them
>
> ld: multiple definitions of symbol __ZN11octave_sortIbED1Ev.eh
> pic/Array-b.o definition of absolute __ZN11octave_sortIbED1Ev.eh  
> (value 0x0)
> pic/Sparse-b.o definition of absolute __ZN11octave_sortIbED1Ev.eh  
> (value 0x0)
> ld: multiple definitions of symbol __ZN11octave_sortIbED2Ev
> pic/Array-b.o definition of __ZN11octave_sortIbED2Ev in section  
> (__TEXT,__text)
> pic/Sparse-b.o definition of __ZN11octave_sortIbED2Ev in section  
> (__TEXT,__text)
>
> or
>
> ld: multiple definitions of symbol  
> __ZN11octave_sortIP9vec_indexISt7complexIdEEE8merge_atEi
> pic/Array-C.o definition of  
> __ZN11octave_sortIP9vec_indexISt7complexIdEEE8merge_atEi in section  
> (__TEXT,__text)
> pic/Sparse-C.o definition of  
> __ZN11octave_sortIP9vec_indexISt7complexIdEEE8merge_atEi in section  
> (__TEXT,__text)
> ld: multiple definitions of symbol  
> __ZN11octave_sortIP9vec_indexISt7complexIdEEE8merge_hiEPS4_iS6_i
> pic/Array-C.o definition of  
> __ZN11octave_sortIP9vec_indexISt7complexIdEEE8merge_hiEPS4_iS6_i in  
> section (__TEXT,__text)
> pic/Sparse-C.o definition of  
> __ZN11octave_sortIP9vec_indexISt7complexIdEEE8merge_hiEPS4_iS6_i in  
> section (__TEXT,__text)
>
> What I not do understand is that there is no conflict with Array- 
> d.cc <-> Sparse-d.cc that's why I compared Array-d.cc with Array- 
> C.cc, Sparse-d.cc with Sparse-C.cc and so on. This all is very  
> cryptic for me and I would be happy for every tip you can give me  
> what I could try next because somehow I get out of ideas...
>
>  Thomas

I also am still having the same problem.  However, I am on an IntelMac  
with Leopard and apparently it uses ld64, for which the LDFLAG of '- 
Xlinker -m' has been obsoleted.  I have hunted around in the new sort  
code a little bit, but I have absolutely no idea why this is happening  
either.

John Swensen