1 |
On Tuesday 26 Apr 2016 18:50:41 Dale wrote: |
2 |
|
3 |
--->8 |
4 |
|
5 |
> I synced again and was hoping I either caught the tree in the middle of |
6 |
> some change over with the last sync or whatever it is would have a fix |
7 |
> by now. Well, still the same error as before. |
8 |
> |
9 |
> Anyone have any ideas on the cause of this? Any tricks that I could |
10 |
> try? Could this be a bug that I need to report? I've tried skipfirst |
11 |
> and such but it seems to be a hard stop on this package. |
12 |
|
13 |
After googling for one of those linker errors, it looks to me like a bug in |
14 |
the order in which libraries are being called to be linked in. I'm no coder |
15 |
any more though (that was 40 years ago). |
16 |
|
17 |
HTH. HaND. :) |
18 |
|
19 |
-- |
20 |
Rgds |
21 |
Peter |