-
Notifications
You must be signed in to change notification settings - Fork 4.9k
Cannot execute dotnet on Debian 8.7 #467
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
Comments
@gkhanna79, @janvorli , Can someone take a look at why we don't just work on 8.7? |
@jinhale This error usually means that one is trying to execute binaries corresponding to an architecture that is not supported on the machine. Can you please confirm that the host machine and binary architectures are the same? That said, please also help confirm the following:
|
@gkhanna79 I'm currently using the i686 version, which may be the problem. I'll try Debian for AMD 64 and let you know if that fixes the problem. I'm not sure how to assess the binary architecture from https://go.microsoft.com/fwlink/?LinkID=835021. That appears to be a 64 bit binary when I tried to download it from my browser. I'm now guessing Microsoft assumes we all use a 64 bit processor and kernel. |
64bit binaries do require a 64bit machine running 64bit OS. Please do share your findings once you have tried the suggestion. |
@jinhale , yes, we have focused our attention on what gets the most people up and running. We haven't gotten to every processor, kernel, c library, etc version of Linux. We are more that happy to work with community members who want to help bring up builds for other things. |
I couldn't get a necessary wireless driver to work with the 64 bit version of Debian, Ubuntu, or CentOS so I abandoned that. I did get dotnet to work on 64 bit Fedora 24. I feel resolved on the issue. I would have liked to know before hand that dotnet was a 64-bit binary on Linux, but maybe I'm the only one that tried to install dotnet on a 32-bit Linux machine without realizing the dotnet binary was 64-bit. |
That is good feedback. Where were you downloading from? This set of pages? https://www.microsoft.com/net/core#linuxdebian |
Nevermind, I see you said that initially. I'll get your feedback to the folks that manage that site. |
@jinhale Please have a look at |
I'm going to close this. I opened an issue internally where the site is built to make sure it gets updated to clarify the x86, x64, etc on download links and instructions. |
I'm on old 32 bit hardware using debian 8, trying to get SOMETHING to run.. |
We don't have an official build of x86 (32-bit) Linux. |
Ahhrghh!! ok do you have any suggestions.. or seen any workarounds by any
chance...
…On Wed, Jul 19, 2017 at 4:23 PM, Peter Marcu ***@***.***> wrote:
We don't have an official build of x86 (32-bit) Linux.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#467 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AGDyiPPUJHz7QkZGBPwgjYzO0TX7kt4dks5sPi2QgaJpZM4L31l6>
.
|
Samsung and the community have been working on building Linux x86. @jyoungyun do you have any advice on how someone could build an x86 linux build or can you point to a place they are being built? |
Sounds interesting..
…On Wed, Jul 19, 2017 at 4:36 PM, Peter Marcu ***@***.***> wrote:
Samsung and the community have been working on building Linux x86.
@jyoungyun <https://github.com/jyoungyun> do you have any advice on how
someone could build an x86 linux build or can you point to a place they are
being built?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#467 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AGDyiD3z50TS-_OZgFb8LoQDoK6iMLWvks5sPjCCgaJpZM4L31l6>
.
|
@janvorli may also be able to give advice. |
Sure
…On Wed, Jul 19, 2017 at 8:40 PM, Peter Marcu ***@***.***> wrote:
@janvorli <https://github.com/janvorli> may also be able to give advice.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#467 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AGDyiAu7b1Gs2A-EeTejdG6RfmWUam6Rks5sPmnTgaJpZM4L31l6>
.
|
Moving from https://github.com/dotnet/cli/issues/5586 on behalf of @jinhale
CLI is Yet Another NetCore App, and underlying platform support is tied to dotnet core as a whole.
Steps to reproduce
Install Debian version 8.7 Linux (debian 3.16.0-4-686-pae #1 SMP Debian 3.16.7-ckt9-2 (2015-04-13) i686 GNU/Linux)
Run the steps from https://www.microsoft.com/net/core#linuxdebian, but use su -c "#command" in place of sudo #command.
Expected behavior
dotnet new should initialize a "Hello world!" CLI application.
Actual behavior
bash: /usr/local/bin/dotnet: cannot execute binary file: Exec format error
Environment data
dotnet --info
output:bash: /usr/local/bin/dotnet: cannot execute binary file: Exec format error
The text was updated successfully, but these errors were encountered: