700+ entries in 0.295s
a111: Logged on 2016-09-05 20:27 trinque: to ben_vulpes link, it does not diminish my regard for
openbsd that it is moving towards llvm. considering solely the political aspect, they've previously used their own old (and maintained) fork of gcc.
trinque: to ben_vulpes link, it does not diminish my regard for
openbsd that it is moving towards llvm. considering solely the political aspect, they've previously used their own old (and maintained) fork of gcc.
☟︎ phf: but fwiw even if
openbsd, say, will give you a similar compilation environment, it's not going to give you bash out of the box. it's ksh, so you're back to "least common sh denominator"
phf: it doesn't satisfy our own requirements of fits in head, it goes through a rube goldberg machine in order to produce a specific build for a specific system. "mac os x? fuck you.
openbsd? fuck you". it doesn't succeed at own goal of producing bit identical builds.
mircea_popescu: asciilifeform that's ok, i didn't actually want to say anything @
openbsd.
mircea_popescu: certainly less wrong with
openbsd than... fucking red hat or w/e.
trinque:
openbsd's
httpd doesn't look like that much src to read, while we're still in c-machine hell.
trinque: I'm clutching to hand-compiled driftwood on
openbsd ☟︎ BingoBoingo: Framedragger: If you bsd either NEtBSD or
OpenbsD but make own ports.
trinque: "why does
openbsd use CVS? CVS sucks!11!"
trinque: psa that joe's datacenter will happily stand up an
openbsd box on the cheap
mod6: i have an
openbsd with some custom patches and tweaks.
fromphuctor: if you want visibility you should try openssl, openssh, libressl,
openbsd ssh keys
assbot: Logged on 05-03-2016 16:19:23; BingoBoingo: In other news looks like
OpenBSD Vax is ending at 5.9 as Vax hardware reaches end of operating afterlife.
BingoBoingo: In other news looks like
OpenBSD Vax is ending at 5.9 as Vax hardware reaches end of operating afterlife.
☟︎ phf: node was running fine inside a virtualbox
openbsd though, same one that i built it on.
phf: now that there was a suggestion of treating specific
openbsd version as baseline, i think problem was that i built in on one
openbsd and tried running on another
assbot: Logged on 11-01-2016 05:12:12; phf: ben_vulpes: i'll take at look in the next few days, but one quick comment, fwiw i built it on a 32-bit
openbsd.
BingoBoingo: mircea_popescu: On
OpenBSD. It's the one I chopped together mostly while drunk and still works.
assbot: Logged on 29-02-2016 20:19:25; asciilifeform: anyone ever build a working trb on
openbsd ?
BingoBoingo: <trinque> it doesn't run linux binaries, which would preclude buildroot, wouldn't it? << Last week
Openbsd killed linux_compat on i386 which is the last platform they supported it on
trinque: in
openbsd's case the operating system's version number refers to an entire base system
trinque: actually most of the remote code execution exploits in recent
OpenBSD were the fault of X
trinque: tbh bitching about the
openbsd ports tree is a matter of having missed the point; pester the maintainer or become him if you want something changed.
trinque: in semi-related news, sbcl passes its test suite using --with-sb-thread on
openbsd assbot: Logged on 02-12-2015 04:13:47; BingoBoingo: "On a personal "hate ramen noodles and tuna" level, I agree. But my good-for-project-good-for-the-world side says the
OpenBSD Foundation is more effective at growing the contribution pie and in particular funding the hackathons where great work happens." - Theo De Raadt
assbot: Logged on 16-02-2016 16:36:23; asciilifeform: now the other thing about
openbsd is the incident with theo and that microshit flunkie
mircea_popescu: i would say that
openbsd pre 2014 and
openbsd post 2014 are entirely unrelated entities.
felipelalli: At least they really care about security. I tried to compile Bitcoin Core in
OpenBSD once but I couldn't (in a quick & dirt attempt).
BingoBoingo: <asciilifeform> there is no
openbsd sans the ports. << The userland is enough for a webserver/firewall/etc box
BingoBoingo: felipelalli: alf hates the
OpenBSD ports turdage which has lots of shitgnomery and the occasional userland shitgnomery
trinque: this is distinct from talking about
openbsd assbot: Logged on 24-01-2016 15:13:09; asciilifeform: in principle, i like the lightweight, pedigreed, and 'hackable on' bsd family, e.g., netbsd. but imho
openbsd is something that probably needs to be helped die
BingoBoingo: Early 2014's when you were called a billionaire and saved
openbsd danielpbarron: the point of
openbsd cd is to compare against downloaded version, no?
assbot: Logged on 24-01-2016 08:18:57; phf: as it stands foundation doesn't support
openbsd, and when someone wants to build on
openbsd, i just support them directly
assbot: Logged on 24-01-2016 08:18:57; phf: as it stands foundation doesn't support
openbsd, and when someone wants to build on
openbsd, i just support them directly
assbot: Logged on 14-09-2015 17:42:55; ascii_field: and until it builds x11 emacs without dbus and related idiocy,
openbsd is WORTHLESS to me.
ben_vulpes: i only had the opportunity to test it recently, failed to even build prerequsites and so cannot sign it. i also do not intend to build another
openbsd system in the immediate future.
phf: the ~only~ "script" aspect of the patch is "-Wl,--whole-archive -lpthread -Wl,--no-whole-archive" which is a cross platform gcc argument that ensure that pthread is truly fully statically linked into bitcoind. the issue that some parts of it don't appear consistently with
openbsd gcc ~and also on some of the linux gcc versions~. fucking says so in the original email
assbot: Logged on 24-01-2016 02:26:40; mod6: <+mircea_popescu>
http://log.bitcoin-assets.com/?date=24-01-2016#1383446 << wait, explain this to me ? << the idea is that our makefiles, or whatever build scripts will utilize V to build inside of the rotor (a linux thing) - the source must be compatable with that. phf's
openbsd scripts are not compatible with this.
phf: as it stands foundation doesn't support
openbsd, and when someone wants to build on
openbsd, i just support them directly
☟︎☟︎ phf: otherwise the work needs to be done by other foundation members, and it comes with commitment to support
openbsd build
phf: one of the features of the
openbsd patch is that it should build cleanly on linux, i.e. naive build or a stator build. i did a naive build that work, while i was developing, but since i assume it was not included in stator i can't speak to that.
BingoBoingo: If asciilifeform reads and tests what he signs the
openbsd patch would have been missed. Timestamp may have been overlooked.
phf: mircea_popescu: well,
openbsd and timestamp are written in old diff format, their migration was not done by foundation when majority of patches were moved to vdiff. i interpreted that move as the patches not being needed and an invitation to perform migration myself.
phf:
openbsd patch as written results in a working build on both linux and
openbsd. it introduces necessary ifdefs to ensure cross platform support. the only change that it does to makefile is, at least according to my research, is necessary with some versions of gcc, rather then
openbsd specific (has to do with static linking of pthread). without that change build ~can~ produce broken static bitcoind on both
openbsd and linux. at the time
ben_vulpes:
openbsd at least installed, booted trivially, and ran emacs under x11.
mircea_popescu: but riddle me this : how does user know his
openbsd make process isn't satan's own ?
mod6: <+mircea_popescu> mod6 so basically we can't use our convenient makefiles to build the pressed source ;
openbsd people gotta finagle their own build chain to get the same source to compile and link ? << and further more, they'll never have the same build process like we want.
BingoBoingo: Also
Openbsd base system is complete enough to make internet on mars
mircea_popescu: mod6 so basically we can't use our convenient makefiles to build the pressed source ;
openbsd people gotta finagle their own build chain to get the same source to compile and link ?
mod6: <+mircea_popescu>
http://log.bitcoin-assets.com/?date=24-01-2016#1383446 << wait, explain this to me ? << the idea is that our makefiles, or whatever build scripts will utilize V to build inside of the rotor (a linux thing) - the source must be compatable with that. phf's
openbsd scripts are not compatible with this.
☝︎☟︎ mod6: anyway, getting a buildable
openbsd is a priority of mine. there are just bigger things in front of that for the moment.
ben_vulpes: fwiw i completely failed to get the
openbsd patch to work.
mod6: so either, we need a separate repository for
openbsd patches (not a bad idea), or we should just put the new
openbsd vpatch in the mailing list for those who need it -- let them just add it to their V 'patches' directoriy by hand
mod6: phf: your patch(s) did work for me on
openbsd. i think, once we have all of trinque's makefiles ready to go with the new (forthcoming) version of V, you and I should work together to get a new vpatch of your
openbsd changes submitted.
phf: fwiw
openbsd didn't make it through v-ification either, it was designed to work cross platform, but i believe there were makefile modifications since, that didn't include it. i don't actively run
openbsd, so can't integration test the result