Skip to content
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.

Debian #3802

Closed
drandreaskrueger opened this issue Jun 4, 2018 · 13 comments
Closed

Debian #3802

drandreaskrueger opened this issue Jun 4, 2018 · 13 comments

Comments

@drandreaskrueger
Copy link

Please support Debian

./eosio_build.sh 

	Beginning build version: 1.2
	Mon  4 Jun 15:13:36 UTC 2018
	git head id: 0961a56007d40fe6d897b7d726fe5005acf06162
	Current branch: master

	ARCHITECTURE: Linux

	Unsupported Linux Distribution. Exiting now.

uname -a
Linux ... 4.9.0-6-amd64 #1 SMP Debian 4.9.88-1+deb9u1 (2018-05-07) x86_64 GNU/Linux

Thanks.

@pacificcode
Copy link
Contributor

@drandreaskrueger Debian is not currently accounted for in our installation procedure. Other options would include Ubuntu or Linux Mint.

@drandreaskrueger
Copy link
Author

drandreaskrueger commented Jun 5, 2018

Great way of treating this request /irony.

Debian is not currently accounted for in our installation procedure.

yes ... I noticed that. I did. Your script had told me that already.

Odd project - a DAO-sized amount of Ether taken in, but not enough money to support more than Ubuntu? Sad. And not at all a Linux approach. There is not only Ubuntu. Debian is one of the main distros.

@pacificcode closed this 17 hours ago

Just closing a valid issue is bad style IMHO. How would I now think it makes sense to even start contributing here ... if you are of that project-type that keeps on closing issues within an hour, to just get them out of the way?

Possible alternative responses could have been:

  • answering "... not currently accounted for", but leaving the issue open
  • assigning a label "feature request"
  • "... have a look at stackexchange, there might be others with the same question"
  • "... not yet, sorry, but I know that John Smith is running Debian too, perhaps he can help. @ john?"
  • " ... Ubuntu/Mint are based on Debian, so the differences cannot be big. If you find a solution please pull-request, and inform us here, thanks."
  • "... thanks for the suggestion, I have added it to our list of milestones"
  • just leaving it fricking open. I am sure you are not the only developer here, right?

A closed issue is now helping no one - apart from keeping your open issues count low. However, an open issue could become a possible gathering place for Debian devs helping each other to fix this (probably-simple-to-solve) shortcoming.

my 2billion cents

@gotope
Copy link

gotope commented Jun 8, 2018

@DanailMinchev

I'm compiling on debian jessie too, many error encountered,
sad, support ubuntu and no debian, what's the problem?

@niclash
Copy link
Contributor

niclash commented Jun 8, 2018

We are compiling successfully on Debian Testing and managed to set it up to run on Debian Stretch (stable).

For the build changes, see github.com/eosgermany/eos. It is only the eosio_build.sh and the Ubuntu build in scripts/.
For production, need to allow libtinfo6 to be installed from Debian testing, by setting up /etc/apt/preferences.

Could have been some additional things that slipped my mind right now.

I wouldn't count on getting it working on Jessie

@gotope
Copy link

gotope commented Jun 8, 2018

failed at 78% on Jessie(llvm 6),
may be I need to upgrade to Stretch to go on.

@drandreaskrueger@niclash
compile success on debian 9 Stretch,

  1. clang-4.0 install from llvm.org source.
  2. cmake clang-4.0 must compile with -DLLVM_ENABLE_RTTI=1
    make install clang
  3. export LLVM_DIR=/path/llvm-4.0
  4. cd /path/to/eos to run eos build.

@DanailMinchev
Copy link
Contributor

@gotope I guess you wanted to tag @pacificcode
and I do agree with @drandreaskrueger that closing the issues without at least tagging them or moving to some future milestone is not very professional for the project like EOS!

@drandreaskrueger
Copy link
Author

drandreaskrueger commented Jun 9, 2018

managed to set it up to run on Debian Stretch

compile success on debian 9 Stretch

Fantastic. Well done.

And actually ... apologies for my grumpy OP. But perhaps it was good that I complained - now there is a solution.

About the Debian version: Due to its heavy focus on stability, and thus conservative versioning of packages, I don't think many cryptocurrency / blockchain developers can afford to still run Debian Jessie. Many of us will run Debian Stretch by now, it's been stable since last summer. So if you have found the way to install EOS to Debian Stretch, you're already the heros of the week.

Please create a pull request for your ./eosio_build.sh - thanks.

@brdelphus
Copy link

Hi can I get the results of make test on debian stretch ? I'm having 6 failures I can't get rid off

@gituser
Copy link

gituser commented Oct 4, 2018

@drandreaskrueger

About the Debian version: Due to its heavy focus on stability, and thus conservative versioning of packages, I don't think many cryptocurrency / blockchain developers can afford to still run Debian Jessie. Many of us will run Debian Stretch by now, it's been stable since last summer. So if you have found the way to install EOS to Debian Stretch, you're already the heros of the week.

No, Debian Jessie is a good choice and MOST cryptocurrencies compile just fine on Debian Jessie.

Sure you can use Debian Stretch but it's newer and might contain more issues. If you have issues with building on Debian Jessie you can use Ubuntu Xenial 16.04 (though not sure how long it will be supported).

Overall, I completely agree Debian should be supported!

@MikeC-BC
Copy link

still an absolute nightmare trying to build on Debian 9 Stretch

@matthewdarwin
Copy link

Until Debian is supported, it does work to compile Ubuntu 18.04 and run the binary on Debian 10.

@MikeC-BC
Copy link

The same applies to Ubuntu 16.04 and Debian 9.

@drandreaskrueger
Copy link
Author

Thanks for continuing to fiddle with this. EOS is not on the top of my list at the moment. But keep me (i.e. this issue) in the loop. Thanks.

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

No branches or pull requests

9 participants