345700+ entries in 0.221s
mircea_popescu: but generally, as an aspiring young lord, you don't have either
the
time or
the resources
to spend any
time or resources with any women
that would settle for anything but
the best
they can possibly get.
mircea_popescu: yeah.
the requisite behaviour of
the wife of
the king.
mircea_popescu: i see it lots with online hos, you'd
think
that if you got easy money once, you'd never leave
that place. but not so if you KNOW you're not worth anyone's
time, deep down.
mircea_popescu: asciilifeform i personally don't.
there's a common disease of whores (and no, programmers aren't fundamentally anything else). it manifests like so : should a wolf find a delicious morsel, it will neglect it oft
to
the point of just letting it sit while it draws a perimeter around and inspects for whence it came for and MOAR. meanwhile, a mouse
that found a morsel will grab it and run, never
to return.
assbot: Logged on 24-01-2016 07:46:51; ben_vulpes: it is weekends like
this
that make me reconsider how i spent my youth as a misspend, when i see
trinque and asciilifeform with usable professional non apple
toolchains
assbot: Logged on 24-01-2016 00:05:24; danielpbarron: >> me:
the universe does not guarantee a solution
to
things
that humans perceive as problems. << personification of 'universe'
to replace God
mircea_popescu: nevertheless,
these must be decisions people
take for
themselves.
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.
assbot: Logged on 11-01-2016 03:34:08; asciilifeform: e.g., want x11 emacs ? say hello
to dbus
assbot: Logged on 24-01-2016 14:39:04; mircea_popescu: phf i dunno man, i've been
trying
to unravel in my head what
the issue is/was, can't say i've got very far.
the only
thing i can say is please, insist.
mircea_popescu: "she would never
take a left on west 83rd at 6pm on a
tuesday. i know
this on
the basis of her $word starwars."
mircea_popescu: but
the list of
things he presents is enough
to deduce
they have nothing in common.
mircea_popescu: "About a week ago,
this pretty girl messages me out of
the blue and we hit it off. We
talked
that night up until 5 AM and we have so much
things in common. > She loves Star Wars > Plays video games > All other super nerdy shit > Never met a girl like
that" << holy shit,
this "all
that much" evaluates
to almost 0. wtf is wrong with people.
☟︎ mircea_popescu: phf i dunno man, i've been
trying
to unravel in my head what
the issue is/was, can't say i've got very far.
the only
thing i can say is please, insist.
☟︎ punkman: "As FSF GCC died a silent death from malnutrition, both were (formally) reunited as of version 2.95 in April 1999. With a simple renaming
trick, egcs became gcc now and formally
the split was over"
punkman: Cygnus,
the Linux folks,
the pgcc folks,
the Fortran folks and many others have done development work which has not yet gone into
the GCC2
tree despite years of efforts
to make it possible."
punkman: "Why are we doing
this? It's become increasingly clear in
the course of hacking events
that
the FSF's needs for gcc2 are at odds with
the objectives of many in
the community who have done lots of hacking and improvement over
the years. GCC is part of
the FSF's publicity for
the GNU project, as well as being
the GNU system's compiler, so stability is paramount for
them. On
the other hand,
ben_vulpes: i do envy everyone
the vast panoply of device families apparently covered.
phf: ben_vulpes: of course,
that bsd patch doesn't stand in isolation. it was produced at a certain
time, was since used by several people
to build a version. but
there's nothing
to sign, because
there's only pre-v patch
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: everything else in
there is either cross platform clarification or straight up an #ifdef. it's a
tiny ass patch, if it doesn't build on rotor, linux, etc. it's a bug in a patch
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.
assbot: BitBet - Marco Rubio will be Republicans' 2016 Presidential Nominee :: 0.54 B (54%) on Yes, 0.47 B (46%) on No | closing in 2 months 2 weeks | weight: 39`117 (100`000
to 1) ... (
http://bit.ly/1KJwMN1 )
assbot: Logged on 24-01-2016 03:19:50; polarbeard: do we agree in using an external
tool for
this?
punkman: I suspect
that using
the plog library (after some win32-snipping) would remove more lines
than it adds
assbot: Logged on 05-11-2015 02:44:58;
trinque: ShrinkDebugFile() << lol,
the autism in
this
thing
assbot: Logged on 24-01-2016 03:19:50; polarbeard: do we agree in using an external
tool for
this?
punkman: well
that was a lot of log
phf: mircea_popescu: ok, so i wouldn't say not welcome, but since neither patch was given a courtesy of a smooth
transition, i assumed
that neither are seen as particularly important. спасение утопающих дело рук самих утопающих (tm) (r)
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
pete_dushenski: ben_vulpes: "The correct answer is
that developed and practiced by people who
take personal cryptographic hygenie very seriously" << hygiene
phf: basically
the patch being dropped created bunch of work for me,
that i don't have bandwidth
to pursue. (i.e. produce a v version,
test on stator)
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: well, first v release was migrated by ascii, with all
the patches signed by him, i
think later mod6 signed his?
mircea_popescu: anyway, do i get
the impression you got
the impression your patches aren't welcome or something ?
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.
pete_dushenski: that being said, i've always
thought
that version numbers should "roll over" at a certain point. not like mac os8 went 43372 sub-versions before macos 9 showed up. eh. i guess it really doesn't matter.
pete_dushenski: ben_vulpes: maybe it's just
the coincidence
that's being picked up on my gaydar
then.
mircea_popescu: in random good unix news : shuf -n 1 $file will pop out a random line from
that file.
ben_vulpes: still
trying
to get
the hang of
the m1a1, very much adrift in
the cockpit of a warthog.
pete_dushenski: just noticed
that crapple is pulling
the same version naming strange as bitcoin 'core', ie. v. x.9 followed by x.10, x.11, x.12, etc. (is
this
the equiv. of web 2.12 ?)
ben_vulpes: phf: i have a hunch
that it was my boost compiles
that were failing.
phf: when it was written and submitted it applied cleanly
to
the
tree.
to my knowledge it doesn't interfere with stator build. in fact
the whole point of patch is
to make minimally intrusive changes
to source so
that interested parties don't have
to
track down silly issues when attempting a build on
their own. it's my understanding
that
the patch was simply dropped during v-ification, so of course now it doesn't in any way fits into
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: shit, i even reconsider
the /past
three years/ of
toolchain investment on weekends like
this.
ben_vulpes: it is weekends like
this
that make me reconsider how i spent my youth as a misspend, when i see
trinque and asciilifeform with usable professional non apple
toolchains
☟︎ ben_vulpes: openbsd at least installed, booted
trivially, and ran emacs under x11.
pete_dushenski: ben_vulpes: i
tried 14 for a few days. couldn't believe how laggy it was. haven't
tried 10 (or whatever
the b-a approved one was)
ben_vulpes: guruvan: i am not running my primary os in a container,
thank you very much.
assbot: “They don’t print paper catalogues anymore, everything’s on
their website.” | Contravex: A blog by Pete Dushenski ... (
http://bit.ly/1KxosOd )
guruvan: ben_vulpes: just get you a boot2docker, and
then run whatever
the hell you want - use
the OSX like a hypervisor :D
ben_vulpes: that is how desperate i am
to get off of os x.
ben_vulpes: no you know what i have one more fence
to piss upon
pete_dushenski: i don't
think anything drove me more nutso when using 10.8
than
the inability
to find a file in a folder you ~just~ placed it in moments earlier.
pete_dushenski: it's wild how much more organised 10.6 is
than 10.8.
the latter ~always~ bunged up dates. when
trying
to organise a folder by "date modified",
the latest documents would almost invariably end up in
their own speshul sub-heading waaay at
the bottom of
the list under "no date". but
then once in a while, not. for whatever reason.
ben_vulpes dd's
the 10.6 installer onto
the flash drive one last
time
assbot: Logged on 24-01-2016 02:35:25; adlai: pete_dushenski: more helpful
to say where you encountered
the deadlink :)