21600+ entries in 0.035s
mod6: i can't even imagine how long it would take on that POS box i bought. probably 16.
mod6: ok that build is going... should take ~4 hours.
mod6: If this dones't help (i doubt it will), I'll need to make another AMI with a recent stage3 and try to shoehorn in this gcc patch I made.
mod6: looks like many of the much older < 4.3 ebuilds don't allow for hardened (unless I'm mistaken here). I'm gonna try 4.5.4.
mod6: so gcc-3.4.6-r2 will not build with "hardened" set as an option, although uclibc can still be used. we do want "hardened" i would think.
mod6: ok well... i guess that settles that then, i'll build 3.4.6 next.
mod6: if anyone thinks we should try that first.
mod6: there is an ebuild for gcc/uclibc/hardened version gcc-3.4.6-r2
mod6: any strong objectsions against 5.1.0?
mod6: (in sync with what's current)
mod6: if that doens't work, then truly will have to get everything in sync and shoe-horn our own patch while all the stage3 stuff is up to speed.
mod6: might try gcc-5.1.0 next.
mod6: gcc on it's 4th hour of compiling...
mod6: so i'm building gcc 4.9.2 on gentoo with uclibc & hardened (PIE). if it builds ok, then I'll give building v0.5.3.1-RELEASE a try - maybe this version won't have the same issue...
mod6: anyone wanna sell 2 Wooly Mushrooms?
mod6: Going to continue on with this, just an update.
mod6: Anyway, trinque wasn't even able to apply my patch successfully on his side.
mod6: the Gentoo patches for gcc 4.8.4 changed during this interval from v1.5 to v1.6. Nothing special here. Wonder if there are this many changes to old ebuilds all the time?
mod6: So this is interesting: I was able to use my gcc patch successfully against my AWS instance which has an AMI that utilizes a stage3-uclibc-hardened from 20150510. And meanwhile, trinque was helping me test to ensure I'm not doing something totally retarded, and on his side he was using the Physical hardware steps where it says to pull the latest (which should be 20150610) stage3-uclibc-hardened.
mod6: as soon as I can, i'll be sure to patch everything in the order specified and kick off a full regression cycle.
mod6: (same sort of deal as last month)
mod6: i've read the patches and ben's review on his blog. i'll be writing up a summary of my own in the SoBA at the end of the month.
mod6: im hoping I can figure something out with gcc tomorrow. if I don't get anywhere, perhaps time to cut bait and head in a different direction.
mod6: thanks for your work on this asciilifeform!
mod6: ah and it bumps the version too
mod6: ok weird. same exact error as last time after complete nuke. tomorrow i'll nuke again and see if gcc will compile without the patch.
mod6: does that guy have a Matryoshka doll tie?!
mod6: so if we get this one to work, i think that's our best/easiest path, currently.
mod6: so one of the reasons i'm being kidna hard-headed about 4.8.4; i'm worried that with a downlevel version such as 3.7 or whatever, that there might not even exist a set of patches (such as Gentoo/uclibc/PIE) that are required for Gentoo -- might be a whole seperate ball of wax & problems.
mod6: just of the bitwise persuasion :]
mod6: i'm gonna nuke that machine again and try to compile it again with the patch. see if it works. if not, i'll just see if it'll even compile gcc itself.
mod6: maybe something in my few repeated builds hosed something up. the /work/ dir does seem to get blown away every time.
mod6: (have been having to add `#define __STDC_LIMIT_MACROS \ #include <stdint.h>` to the start of net.cpp, util.cpp, and wallet.cpp for some bizzare reason)
mod6: oh, and I keep hitting an additional problem aside from what the "gentoo sanitiy" resolves. i've been holding off submitting a patch for it until I can get this thing actually compiled and working.
mod6: (basically, I'm just saying those patches should have been included in my list above)
mod6: then we can finally go off of a version that we support, etc.
mod6: before we cut a new milestone, i'd like to have this sucker up and running on gentoo with uclibc & patched with the "gentoo sanity" patches as well.
mod6: of course... there is the entire question on the table at this point about the "gentoo sanity" patches.
mod6: if this works out, it'll be my first official gcc hack
mod6: now to find out if it actually /works/ XD
mod6: oh hey, i think my patch built ok...
mod6: let's let ben weigh in here.
mod6: well, there isn't a previous version 5.4 -- stops after 5.3 and goes right to 6... so i guess that could work.
mod6: If we add in (officially the following): { Orphanage Thermonuke, TX Orphanage Amputation, { All DNS Thermonyukyooar Patches } }, I'd say that'd be a new milestone. And I'd propose to call it 0.5.3.2
mod6: The patch we got from that mailing list was from a different version for sure than 4.8.4 -- so i've had to hack it in by hand. gentoo is now applying the patch properly. and it's compiling as we speak. there is one caviat that I need to get over before I can test it though.
mod6: asciilifeform: 1) don't have anything to add to this discussion atm. although, we can have it again if you like. 2) I don't have anything going atm; The working nodes (on deb6) are down because i'm working on the gentoo gcc stuff right now.
mod6: I am the liquor, bobandy.
mod6: it's a shit blizzard, Randy.
mod6: <+mircea_popescu> something about the lock not being bsd or what was it << lol :D
mod6: oh I vote for the trip to magial places on the island.
mod6: the skirts could have a quick "clasp" or some sort of attachment mechinism to keep hands free while cart-wheeling.
mod6: ah, yeah. hmm. didn't consider that.
mod6: girls would have to do cart-wheels to get to a ball on the otherside of the court as opposed to running.
mod6: yeah, that shoes might be the problem. but... war is hell.
mod6: foxtail would command respect for sure.
mod6: re: slutennis "Wouldn't you watch a sport like that ?" << f yes.
mod6: ben_vulpes: & ubuntu?
mod6: ben_vulpes: what version & patches & os?
mod6: check out the /topic & read at least 6 months of logs.
mod6: patch applies manually just fine, seems to choak when used by emerge becuase of directory levels or something. hopefully can overcome this...
mod6: ok, i've got a patch i created myself (post application of patches: gentoo/uclibc/PIE) for gcc... just trying to get it to work with emerge.
mod6: ben_vulpes: you did get Eulora built tho 'eh?!
mod6: << someone put it on reddit twitter or wherever. << done
mod6: ok, well done patching the stuff that can be patched...
mod6: there's about a 0.001% chance this will work.
mod6: lol, this is uglier than I had thought. I patched the gcc-4.8.4 source with all of the patches from /their/ bundle v1.5 (
http://dpaste.com/1NRJTT7.txt), and now i'm in there apply patches by hand, and only 2 out of ~10 files to patch actually exist here (the rest are for pr# files (Problem Report?)). And when I can apply a patch, the surrounding code is slightly different.
mod6: If this doesn't go well, perhaps we'll try a period gcc if we can get it to work with uclibc/hardened AND another caviat here is going to be weather this defect shows up in there as well (since way down level).
mod6: I think I might try to manually implement the changes required if the files in question do exist.
mod6: so trinque & I have discovered that the patch provided by the email mentioned (
https://gcc.gnu.org/ml/gcc-patches/2015-02/msg00410.html ) doesn't patch cleanly at all. Even with some McGuyvering of the patch to ensure the paths are correct etc, there are still a number of files not found. It might be plausible to write our own custom patch for 4.8.4 to resolve the issue.
mod6: soon to be bennifer
mod6: trinque: werd. sounds good.
mod6: anyway, yeah, i think this crud goes all the way back to the start.
mod6: ah, didn't know it had a name.
mod6: whats the wire protocol?
mod6: anyway, i did checkout git tag v0.1.5 and the code there has the external ip stuff too.
mod6: not v0.2.1 may 21st. smh
mod6: oooh. i was super confused. ok the name of the file is "bitcoin-src-21may2012.tar.gz"
mod6: no, MPs email contained v0.2.1
mod6: Unrelated, I downgraded my GPG version from v1.4.13 to v1.4.10 -- incase anyone notices the change in my sigs.