20000+ entries in 0.037s
mod6: rotolinux sounds awesome btw.
☟︎ mod6: on fbsd there is a linuxcompat kernmod -- but it has issues if you make too many i386 syscalls in your linux code. *shrug*
mod6: i'll have to take another crack at rotor after month end.
mod6: it's going slow, but -verifyall and to usbdrive
mod6: ya, mine's sync'ing now.
mod6: mircea_popescu: ok sure. can do.
mod6: ok well.... thanks for setting me straight.
mod6: i agree. i'm just being careful not to create more work for myself/others than necessary.
mod6: so should we still create scripts for people to build without buildroot (i.e. stator.sh/auto.sh) and then host packages for the ability to construct a buildroot with a drop-in of the foundation source?
mod6: yeah I saw that about the eulora thing.
mod6: so i guess there is still a bit of a fork in the road; even if we do all of the hard work of ensuring peoples host dependantcies are installed before any compiling is even attempted, do we even want that to be a thing, as stan said, this is now obsolete. And do we now maintain a lot of other things for buildroot?
mod6: hard, not impossible.
mod6: yeah totally agree. and i can't help but wonder if it's simply because of things that each persons different host has not installed by default. but it's hard to account for all of that.
mod6: the idea was; put out this test bundle and see if we're on the right track and if anyone hits any problems with any of the patches.
mod6: not even for a few months -- even before rotor came out.
mod6: oh no. i wasn't planning on that at all this month anyway.
mod6: but mircea_popescu makes sense.
mod6: which is why he said he wrote that in the first place.
mod6: i think he's as tired of our build script problems as I am.
mod6: trinque: he and i discussed this breifly. and I won't speak for him here. but i wouldn't have said what I said earlier without at least a discussion about that.
mod6: and besides, we haven't exactly had great luck with our own build scripts to date.
mod6: well, i've been pushin pretty hard as far as work load -- what scares me is taking on buildroot and trying to bundle/test the entire thing.
mod6: we need something that people can utilize to make it work. i totally agree with that. and scripts and other widgets to make it work could even be a separate bundle.
mod6: you brought that up the otherday, agree 100%
mod6: exactly what I'm referring to.
mod6: <+trinque> asciilifeform: I don't think he's saying that, merely that aside from the makefile, perhaps the larger build system should be a separate concern << exactly this. Makefile stays ofc.
mod6 takes away shinohai's matches
mod6: That should be something that you use for what we deliver.
mod6: That all being said, I'm super glad that 'rotor' is out there now, and I hope to learn and use it one day myself. Maybe even this week! But that shouldn't be something that we deliver.
mod6: And if someone wants to run a dynamically linked version? Who are we to tell them 'no'?
mod6: If asciilifeform needs a fully deterministic static bitcoind for his use, then sure, he can use whatever means he needs to achieve that.
mod6: And truly none of our business.
mod6: The rest is all secondary.
mod6: We're gonna do what we do, deliver bitcoin source code.
mod6: Trying to create a one-size-fits-all script for everyone to use to build this thing is not going to work. And how does one bundle up something such as 'rotor' and end up not maintaining buildroot and everything else? That's a game that I'm not interested in playing. And it's dangerous for us to go that direction.
☟︎ mod6: Like sourceforge goes away, or OpenSSL gets a million pound shit dropped on its head.
mod6: Only in some sort of catestrophic circumstance will we do such a thing.
mod6: How one builds the source is entire up to the user. There may be preferred way so of doing this, such as 'rotor' and so forth. And we'll participate in creating cookbooks and guides on how to do this. But we no longer are going to fight through these environment problems.
☟︎☟︎ mod6: The Foundation isn't going to ship these builds scripts any more. We're just going to ship source code for bitcoin.
☟︎ mod6: he expects everyone to pull down their own bundles.
mod6: because alf's original stator doens't have that in there.
mod6: anyway, that has nothing to do with anything
mod6: punkman: did you try the line above it first? the first line: boost="
http://sourceforge.net/projects/boost/files/boost" << sets a environment variable. is required for the second part to work: curl -L "$boost/1.52.0/boost_1_52_0.tar.bz2" -s -o distfiles/boost_1_52_0.tar.bz2
mod6: anyway, this is all gonna change.
mod6: i put this in the stator.sh script. it pulls them down, have tried on 3 different environments of my own, and independantly verified 2x otherwise.
mod6: did you enter the line above it first?
mod6: 8de651beb9a48f91f8a797f44966b8f25c3351d6893c1d79969aeb2ded3adeaf8fc14aa9b8a4410081dde9ef155330b41a4982a62b55adde40bb73f0066c74a2 distfiles/boost_1_52_0.tar.gz
mod6: and this is what all of my older v0.5.3.1 builds have pulled down for the .tar.gz:
mod6: curl -L "$boost/1.52.0/boost_1_52_0.tar.bz2" -s -o distfiles/boost_1_52_0.tar.bz2
mod6: i get the same thing on mine -- the (bitcoin-v0_5_4-TEST1.tar.gz has a script that pulls that one via curl command):
mod6: fc512d3bfa6a39a60fee548775c97239271cf757587b8df7ed739c800844a819a359dca172be0e69ad7752753753139bf11f0813d650066d58386662fe32842d distfiles/boost_1_52_0.tar.bz2
mod6: hanbot: prior to stator we used .tar.gz on boost, not sure why alf started using .bz2 at that point.
mod6: i play in 3rd person follow
mod6: jurov: lol, awkward?
mod6: ok, so sometime next week, i'll rebuild again from scratch and paste the full log.
mod6: probably 20 lines of log to wade throgh
mod6: ascii_field: there are a few pastes, it starts here: log.bitcoin-assets.com/?date=28-07-15#1214475
mod6: that was all fine and dandy.
mod6: wont really revisit until after the 1st.
mod6: other than basically trying it out that one time, i've been pretty hammered with other stuff to finish before month end.
mod6: my build failed during the BDB build
mod6: i built mine on a gentoo/nomultilib/glibc x86-64 host
mod6: i ran into the the same problem as trinque with mine. and you told him 'get a computer'
mod6: isn't rotor just 'old-stator' (from a few months ago) + buildroot & openssl patch?
mod6: well, thanks for giving it a try. not sure what's going on there atm.
mod6: are you compiling as yourself or root?
mod6: so better to start fresh and see. only takes a few minutes anyway.
mod6: i looked like to me that maybe something worked well after realpath was installed with boost, but maybe something didn't get copied over correctly with openssl.
mod6: start over 100% since now you hvae realpath installed.
mod6: so feel free to blow way all the build directories etc.
mod6: tell pete_dushenski <+punkman> do you have realpath? << Now that you have `realpath` installed, I'd try rebuilding the entire thing again. Thanks for testing!
mod6: hi pete_dushenski: yeah, did you see my last comment to you?
mod6: congrats btw mike_c :]
mod6: but eventually, im sure they'll live/reside in the wiki itself.
mod6: thx. mainly as I'm kinda still sorta updating 'em, it's easier to update 'em on my side then to push 'em into the wiki every time.
mod6: having a fully deterministic everything is where we want to be. but I can't even get it to build yet myself. imho; we've got quite some time/work ahead of us on that.
mod6: asciilifeform: if folks want to build obsolete crud, it is their business; but i would like to make sure they know that it is obsolete crud, and that i can either try to somehow support it XOR release new stuff ('rotor' etc) << are you infavor of releasing 'rotor'?
☟︎ mod6: ;;later tell pete_dushenski <+punkman> do you have realpath? << Now that you have `realpath` installed, I'd try rebuilding the entire thing again. Thanks for testing!
mod6: <+shinohai> I'm not sure if mod6 finished his last night or not. I quit about 11 p.m. because I was pretty buzzed. << i hit the same problem as trinque
mod6: but what was strange is that none of the bdb libs were copied into ourlibs
mod6: hmm, so after that, i commented out the configure/build parts for openssl/bdb/boost from rotor.sh and re-ran rotor.sh, and it started to compile... failed. couldn't find the BDB stuff.