Snow leopard?



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 04/12/2009 at 08:46, xxxxxxxx wrote:

    User Information:
    Cinema 4D Version:   11 
    Platform:      Mac OSX  ; 
    Language(s) :     C++  ;

    ---------
    Hi all,

    does anybody know if there is a recompile necessary for Snow leopard? One of my customers runs R11 on Snow Leopard but the console says "plugin dpit does not support 64bit". Which is nonsense of course, it works fine for my betatesters with 64Bit (don´t know yet if they explicitly run snow leopard though)

    thx



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 04/12/2009 at 14:48, xxxxxxxx wrote:

    Originally posted by xxxxxxxx

    <ADDRESS>
    User Information:
    Cinema 4D Version:   11 
    Platform:     
    Mac OSX  ; 
    Language(s) :    
    C++  ;

    ---------
    </ADDRESS> Hi all,does anybody know if there is a recompile necessary for Snow leopard? One of my customers runs R11 on Snow Leopard but the console says "plugin dpit does not support 64bit". Which is nonsense of course, it works fine for my betatesters with 64Bit (don´t know yet if they explicitly run snow leopard though)thx

    That is not necessary. This message only appears, if the installed plugin doesn't contain the necessary architecture (e.g. universal binary but no ppc64 or no x64 binary included).

    Best regards,

    Wilfried Behne



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 04/12/2009 at 16:25, xxxxxxxx wrote:

    Hi and thanks Wilfried. I already figured it out when my betatester confirmed it´s working fine for him with Snow Leopard. Very strange, I always have all of the available architectures defined. Well, will need to rebuilt it. Pfew, glad it was only this.

    thx anyway for your answer



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 05/12/2009 at 04:43, xxxxxxxx wrote:

    Hi Wilfried,

    ok, I just looked at my build configurations and I seem to have the accorfding architectures set as I thought. these are the ones I have defined:

    ppc
    ppc64
    x86_64
    i386

    So that should cover it right? So I don´t understand why my user gets the according message. Any clue? thanks again



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 05/12/2009 at 06:02, xxxxxxxx wrote:

    Just to add a bit more information, one of my betatesters is using R11 on SnowLeopard in 64-Bit mode (just like my customer) on a MAC Pro and he has no problems running my plugin. Any idea what could cause this? (I am still waiting for the customer to send me his exact computer specs)



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 05/12/2009 at 10:06, xxxxxxxx wrote:

    Originally posted by xxxxxxxx

    Just to add a bit more information, one of my betatesters is using R11 on SnowLeopard in 64-Bit mode (just like my customer) on a MAC Pro and he has no problems running my plugin. Any idea what could cause this? (I am still waiting for the customer to send me his exact computer specs)

    - damaged installation

    assuming that you had versions (before) without 64 bit binaries:
    - old dylib with just 32 bit binaries and new one (with 64 bit) installed

    - customer put (or installed) the new plugin version in the wrong location

    Best regards,

    Wilfried Behne



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 05/12/2009 at 11:01, xxxxxxxx wrote:

    Originally posted by xxxxxxxx

    • damaged installation

    assuming that you had versions (before) without 64 bit binaries:
    - old dylib with just 32 bit binaries and new one (with 64 bit) installed

    - customer put (or installed) the new plugin version in the wrong location

    Best regards,

    Wilfried Behne

    Hi Wilfried,

    thanks again. Point 2 and 3 were the first things I checked with the customer. All fine (I told him to search the whole c4d installation folder including subfolders for any .dylib files and the according plugin dylib was single. Also he removed all plugins and only installed mine. Still no luck unfortunately. Also there was no 32-bit only version available before, included 32/64 bit from the day of release.). He also said, he just cleanly installed snow leopard and C4D.

    Concerning point 1, the file structure seemed absolutely fine (he showed me screenshots) and he redownloaded my plugin archives several times (with me providing him the correct links), also with several browsers (Safari and Firefox).

    I´m really lost as I have absolutely no idea what the problem could be (of course I am worried that other customers may also not be able to run the show, especially the demo, which would be very bad). This is a bit strange. :-( My gut tells me that it maybe is an exceptional case but can´t stop panicing somehow.

    Well, the only thing I can really think of is that the files are somehow corrupted. That would make sense as the rest works fine (installation, folder structure, the fact that it works for my testers and that this never happened before with any other customer).

    Well, ok. If there is anything else you can think of please let me know, otherwise I will double check everything with the customer again. Maybe we missed something *cough*

    Thank you for the quick input
    Samir



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 06/12/2009 at 04:55, xxxxxxxx wrote:

    Originally posted by xxxxxxxx

    Originally posted by xxxxxxxx

    • damaged installation

    assuming that you had versions (before) without 64 bit binaries:
    - old dylib with just 32 bit binaries and new one (with 64 bit) installed

    - customer put (or installed) the new plugin version in the wrong location

    Best regards,

    Wilfried Behne

    Hi Wilfried,thanks again. Point 2 and 3 were the first things I checked with the customer. All fine (I told him to search the whole c4d installation folder including subfolders for any .dylib files and the according plugin dylib was single. Also he removed all plugins and only installed mine. Still no luck unfortunately. Also there was no 32-bit only version available before, included 32/64 bit from the day of release.). He also said, he just cleanly installed snow leopard and C4D. Concerning point 1, the file structure seemed absolutely fine (he showed me screenshots) and he redownloaded my plugin archives several times (with me providing him the correct links), also with several browsers (Safari and Firefox). I´m really lost as I have absolutely no idea what the problem could be (of course I am worried that other customers may also not be able to run the show, especially the demo, which would be very bad). This is a bit strange. :-( My gut tells me that it maybe is an exceptional case but can´t stop panicing somehow.Well, the only thing I can really think of is that the files are somehow corrupted. That would make sense as the rest works fine (installation, folder structure, the fact that it works for my testers and that this never happened before with any other customer).Well, ok. If there is anything else you can think of please let me know, otherwise I will double check everything with the customer again. Maybe we missed something *cough*Thank you for the quick inputSamir

    Unfortunately we don't deliver the exact error code in this case (the end result still is that your plugin doesn't run in 64 bit, but maybe due to a different reason), but I can tell you what happens (and what could go wrong) :

    - On OS X Cinema loads the dylib via dlopen() using the modes (RTLD_LOCAL | RTLD_NOW); this is way before even the c4d_main symbol is inquired or your initcode of the plugin is called.

    - With these modes dlopen() tries to resolve all undefined symbols BEFORE dlopen() returns.

    If either these symbolds can't be resolved (e.g. you're accessing a lib that doesn't have to be installed on that OS version) or the users system installation is damaged (and doesn't contain this lib that it is supposed to be there), or if there is an extension in the users system installed that intercepts dlopen() and dlerror(), the loading of the dylib can fail.

    I'd compare your project settings (check project AND target settings!!) with the settings we've used in r11.5 - use the r11.528 demo (if you don't have r11.5) to get the latest version of the sdk project files.

    Best regards,

    Wilfried Behne



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 06/12/2009 at 08:16, xxxxxxxx wrote:

    Hi Wilfried,

    thank you for the valuable info! I will check the project and target settings as soon as I am in the office again (though afaic remember I checked them to be consistent, but I check out the 11.5 settings accordingly).
    I checked out dlopen() and it says that it´ll return NULL in case of any error. Does C4D maybe store the last dynamic error returned from dlerror() somewhere (I know you said you don´t deliver the exact error code)? Can I call dlerror() myself maybe (though the static error buffer seems to be overwritten with every dlerror call, so this is probably not very valid or too late for being called in my init; if access is possible at all)?

    Anyway, this sounds very much like a damaged system installation could be the reason (as I don´t call any Non-OS libs) but I first make sure that it´s not my target settings being inconsistent. I report back on this.

    Btw. my plugin is not the only thing that is not loaded for the customer. He gets the same console messages for "fbx6", "flashex" and "openexr" he just wrote me. Is this an indication for something maybe?

    thanks



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 06/12/2009 at 10:23, xxxxxxxx wrote:

    Originally posted by xxxxxxxx

    Hi Wilfried,thank you for the valuable info! I will check the project and target settings as soon as I am in the office again (though afaic remember I checked them to be consistent, but I check out the 11.5 settings accordingly). I checked out dlopen() and it says that it´ll return NULL in case of any error. Does C4D maybe store the last dynamic error returned from dlerror() somewhere (I know you said you don´t deliver the exact error code)? Can I call dlerror() myself maybe (though the static error buffer seems to be overwritten with every dlerror call, so this is probably not very valid or too late for being called in my init; if access is possible at all)? Anyway, this sounds very much like a damaged system installation could be the reason (as I don´t call any Non-OS libs) but I first make sure that it´s not my target settings being inconsistent. I report back on this.Btw. my plugin is not the only thing that is not loaded for the customer. He gets the same console messages for "fbx6", "flashex" and "openexr" he just wrote me. Is this an indication for something maybe?thanks

    No you can't access dlerror() - that is called inside of the kernel before your plugin would be initialized (which it isn't in this case) and there are a lot of additional dlopen calls later on. I'll have to add a few lines of code (in a future version) to deliver a more detailed error message.

    The console messages about fbx6, flashex and openexr are as expected, as they really don't contain 64 bit code (and therefore dlopen() fails).

    Best regards,

    Wilfried Behne



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 07/12/2009 at 06:39, xxxxxxxx wrote:

    thanks, some more detailed error code in future versions sounds very useful.

    And my customer now got it working! He reinstalled Cinema 4D from scratch and also reinstalled my plugin and now it works fine. So I assume something had indeed been corrupted in some way.

    thank you again for the quick help


Log in to reply