File is not a valid dynamic library

Increasing the amount of RAM available ensured that the program could work. There were some useful responses from others namely slm who provided useful commands to check that each of the libraries existed, and lgeorget who suggesting trying the strace command.

Can you post some of the libraries that it does link to from the original system? You might just need to install some missing libraries. Knowing this, on the original system, you can run this command to figure out what package provides this library:.

At this point, you have two choices. If you can recompile it which I doubt, if I understand well your case , it will run because it will be relinked with compatible libraries. Otherwise, you could try to build a kind of sandbox, an VM running with an old version of GNU libraries for example, to run the application in.

In Arch Linux , if the file is bit elf, you can install libgcc-libs from multilib repository to solve the problem. Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group.

Create a free Team What is Teams? Learn more. Asked 8 years, 8 months ago. Active 2 years, 2 months ago. Viewed 85k times. Packages required libSM Improve this question.

Anthon 74k 41 41 gold badges silver badges bronze badges. Carl Carl 1 1 gold badge 4 4 silver badges 9 9 bronze badges. At least that's what the uname-a command tells me yes?

Carl Out of curiosity, what does strace. That may give us an hint about what is missing first. Carl Ok, so it doesn't even go to the point at which it tries to load some libraries. How are we doing? Please help us improve Stack Overflow. Take our short survey.

Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Asked 5 years, 9 months ago. Active 8 months ago. Viewed 24k times. What am I doing wrong, or do I need to wait a bit more for a better release. Improve this question. Graham Graham 6, 19 19 gold badges 60 60 silver badges bronze badges. Add a comment. Active Oldest Votes.

The specified embedded framework does not contain an Info. The specified binding library contains an embedded framework, but Xamarin. Please set the deployment target in the Info.

This error means that the managed linker encountered an unexpected error, e. More information about the exact error will be part of the build log, e. It is important to file a bug report for such issues. In most case a workaround can be provided until a proper fix is published. This generally indicates that there is a problem with your Xamarin.

Please try reinstalling Xamarin. Projects that were using this old provider and now build with the newer appletls one. This means there is an error on the custom XML linker configuration file you provided, please review your file.

The assembly mentioned in the error message is loaded from multiple locations. Make sure to always use the same version of an assembly. The root assembly could not be loaded. Please verify that the path in the error message refers to an existing file, and that it's a valid.

NET assembly. Something unexpected occurred when trying to optimize generated binding code. The element causing the issue is named in the error message. To fix this issue the assembly named or containing the type or method named will need to be provided in a new issue on github along with a complete build log with verbosity enabled i. Something unexpected occurred when trying to remove user resources.

The assembly causing the issue is named in the error message. To fix this issue the assembly will need to be provided in a new issue on github along with a complete build log with verbosity enabled i. User resources are files included inside assemblies as resources that needs to be extracted, at build time, to create the application bundle. This includes:. Something unexpected occurred when trying to set the default HttpMessageHandler for the application.

Please file a new issue on github along with a complete build log with verbosity enabled i. Something unexpected occurred when trying to remove code from BCL shipping with the application. Something unexpected occurred when trying to seal types or methods final or when devirtualizing some methods. Something unexpected occurred when trying to reduce the metadata from the application. Something unexpected occurred when trying to mark NSObject subclasses from the application.

Something unexpected occurred when trying to inline code from the application. In order to fix this issue the assembly will need to be provided in a new issue on github along with a complete build log with verbosity enabled i. Something unexpected occurred when trying to mark the conversion methods for smart enums from the application. An invalid assembly reference was encountered when processing the method mentioned in the error message. See Mixed native and managed assemblies for more information on mixed-mode assemblies.

This generally indicates a bug in the AOT compiler. Please file a new issue on github with a project that can be used to reproduce the error. Sometimes it's possible to work around this by disabling incremental builds in the project's iOS Build option but it's still a bug, so please report it anyways.

Debugging is not supported when LLVM is enabled. If you need to debug the app, disable LLVM first. This typically occurs when an assembly references another version of a platform assembly usually the.

NET 4 version of mscorlib. This is not supported, and may not build or execute properly the assembly may use API from the. An error occurred when generating main. If you believe Xamarin. This currently only happens with one type: System. This occurs when the registrar encounter a type in a signature with the mentioned characteristics. The registrar might need to create new instances of the type, and in this case it requires a constructor with the IntPtr, bool signature - the first argument IntPtr specifies the managed handle, while the second if the caller hands over ownership of the native handle if this value is false 'retain' will be called on the object.

Failed to compile the generated code for the registrar. The build log will contain the output from the native compiler, explaining why the code isn't compiling. This is always a bug in Xamarin. This error indicates a bug in Xamarin.

This occurs when subclassing a framework type, and trying to implement a 'retain', 'release' or 'dealloc' method:. It is however possible to override these methods if the class isn't the first subclass of the framework type:. In this case Xamarin. The name of an Objectice-C class can't contain whitespace, which means that the Register attribute on the corresponding managed class can't have a Name parameter can't contain whitespace either.

Please verify that the Register attribute on the managed class mentioned in the error message does not contain any whitespace. This error most likely indicates a bug in Xamarin. Please check the reported error message for the underlying cause. Please make sure the type in the BindAs attribute matches the type of the member it's attached to. This is a bug in Xamarin. If you run into this while developing a binding project for a native library, we're open to adding support for new combinations of types.

If this is the case, please file an enhancement request on github with a test case and we'll evaluate it. This happens when the native linker cannot find a symbol that is referenced somewhere. There are several reasons this may happen:. If you're the author of the third-party binding, or have access to its source, modify the binding's [LinkWith] attribute to include the framework it needs:. Remember that this must be done for every project configuration. If you're the author of the third-party binding, or have access to its source, modify the binding's [LinkWith] attribute to set the IsCxx flag:.

If you can't modify the third-party binding, or you're linking manually with a third-party library, you can set the equivalent flag by passing -cxx to mtouch this is done by modifying the additional mtouch arguments in the project's iOS Build options page.