CVS build error with new sort

[John W. Eaton]

On  7-Feb-2008, Thomas Treichl wrote:

| 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)

Will you please go back to the current sources without any of your
local modifications and send the output from doing

  nm pic/Array-b.o | grep octave_sort

and

  nm pic/Sparse-b.o | grep octave_sort

?

Thanks,

jwe