Skip to main content
Visitor II
February 3, 2006
Question

COSMIC linker error

  • February 3, 2006
  • 15 replies
  • 2447 views
Posted on February 03, 2006 at 04:47

COSMIC linker error

    This topic has been closed for replies.

    15 replies

    pete3Author
    Visitor II
    January 31, 2006
    Posted on January 31, 2006 at 12:09

    I've also uninstalled all previous versions of the compiler and reinstalled the 16K version. This has had no effect. I notice that by default the registry key linking to the libraries has not been used; I have therefore manually added this which again has no effect. If I manually move the libraries around the error message changes to ''Could not open libfs.st7'', so obviously the file is there. I wonder if the file could have been corrupted, perhaps during the download? Even MD5 isn't infallible. Do you have a current version you could post to this forum?

    Visitor II
    January 31, 2006
    Posted on January 31, 2006 at 12:27

    I am using the full version which will be a differant number.

    I do know of a few customers who are using the 16K version with no problems, is there no way of you uploading a testcase to look at ?

    Regards

    sjo

    pete3Author
    Visitor II
    January 31, 2006
    Posted on January 31, 2006 at 13:01

    Well, the library compiles fine in another program I wrote specifically to test this functionality so it appears the problem is something to do with this application. Sorry sjo, even though you appear to be an FAE for ST I just can't release this code. I will contact COSMIC and see if they have any suggestions.

    Thanks for all your help.

    Visitor II
    February 1, 2006
    Posted on February 01, 2006 at 06:05

    Peter,

    it might actually be an error in the 16k version.

    Please contact me at luca dot ubiali at cosmic do fr so that we can make sure what the problem is and fix it if necessary.

    Regards,

    Luca (Cosmic)

    Visitor II
    February 3, 2006
    Posted on February 03, 2006 at 04:47

    for those who have been following this thread, the problem was due to a missing module in the libraries within the 16k compiler.

    This has now been fixed.

    Regards,

    Luca (Cosmic)