Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

osx support #110

Open
tofutim opened this issue Nov 15, 2024 · 4 comments
Open

osx support #110

tofutim opened this issue Nov 15, 2024 · 4 comments

Comments

@tofutim
Copy link

tofutim commented Nov 15, 2024

Feature request type

sample request

Is your feature request related to a problem? Please describe

What prevents PaddleSharp from working on Mac OSX (Intel or Apple Silicon)? Is it a hard problem?

Describe the solution you'd like

It works!

Describe alternatives you've considered

No response

Additional context

No response

@n0099
Copy link
Contributor

n0099 commented Nov 16, 2024

The underlaying PaddlePaddle isn't supporting it.

@grinay
Copy link

grinay commented Dec 18, 2024

@n0099 this is not true.@ @tofutim I'm working on product where we use paddlepaddle. And I' using it on my osx m3. The only thing it works only on CPU, and I had to build it on my own. You can use my package PaddleInference.runtime.osx-arm64 along with paddlesharp.

@kwasak
Copy link

kwasak commented Jan 31, 2025

@n0099 this is not true.@ @tofutim I'm working on product where we use paddlepaddle. And I' using it on my osx m3. The only thing it works only on CPU, and I had to build it on my own. You can use my package PaddleInference.runtime.osx-arm64 along with paddlesharp.

Hey. I'm using your package PaddleInference.runtime.osx-arm64 and can't seem to get it to work. I'm getting segmentation fault (Code 139), when using Mkldnn or Openblas. MLKDNN also says "Please compile with MKLDNN first to use MKLDNN". What device did you use? M1 Mac.

@grinay
Copy link

grinay commented Feb 1, 2025

@kwasak hi. Yes, I’m using it on two different apple silicon devices m1 and m3.
Let’s try to understand the issue.
What .net version are you using.
Also let’s print some debugging
Set this env variable for running your application it will give you insights about what libs actually loaded.
export DYLD_PRINT_LIBRARIES=1
export DYLD_PRINT_LIBRARIES_POST_LAUNCH=1
export DYLD_PRINT_RPATHS=1

Or run in console something like this DYLD_PRINT_LIBRARIES=1 dotnet yourapp.dll

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants