501200+ entries in 0.31s
mircea_popescu: this is seriously a bigger deal
than whatever obama fucking derped
today.
mircea_popescu: "/home/stas/bitcoin-v0_5_3_1/ourlibs/include/boost/asio/detail/impl/socket_ops.ipp:2900: warning: Using 'getaddrinfo' in statically linked applications requires at runtime
the shared libraries from
the glibc version used for linking"
☟︎ mircea_popescu: in general
this is
the golden pill
to defeat "general purpose" poisoned compiler,
that auto-pulls
the magic diddled dependency : put a x = "hash" in
the code, compile, see if it included it.
mircea_popescu: the only reasonable way
to go forward at
this point would be a) edit
the source of
the ssl we intend
to use
to include a magic string ; b) make ; c) strings on
the binary.
mircea_popescu: <asciilifeform> cannot possibly work for static build. <<
this.
decimation: dynamic libraries are
the depressing result of
the c-machine's sad attempt
to have a global namespace
mod6: yeah,it's weird. it seemed
to puke on
this:
mod6: there is another error beyond
that one??
mod6: next part here... in your email, it seems
that you apply your patch "asciilifeform-kills-integer-retardation.patch", and
this doesnt seem
to completely solve it...
BingoBoingo: <asciilifeform> which is one of
the penalties for going static <<
The most important part of a
turkey sandwich is
the ham
mod6: so need
to run in gdb and disassemble.
mod6: yeah i get nothing from
these: root@debian-test:~/release-test/bitcoin-v0_5_3_1/bitcoin/src# readelf -a bitcoind | grep -i ssl
mod6: asciilifeform: is
there a definitive way
to check
the binary for which SSL is linked in?
mod6: my hunch is
that
this is not working as expected. I need alf
to verify for me.
ben_vulpes: the version of openssl you and alf found
to not wedge bitcoind?
ben_vulpes: isn't
that
the release date of 1.0.1g?
mod6: alf might know. i bet it's
the wrong goddamn one
mod6: I don't know for sure
though.
mod6: 'OpenSSL 1.0.1g 7' << is probably referring
to
the output seen here: OpenSSL 1.0.1g 7 Apr 2014
ben_vulpes: i don't know how
to read xxd output at all
ben_vulpes: mod6: how does
that dpaste indicate
the system ssl?
mod6: obviously, i don't have a clue as
to what's going on
there.
mod6: so if
that's not working as expected, I (we) need help getting
the makefile in order so
that it does
this correctly &
the auto.sh script if
that's part of
the problem also.
assbot: Pushing
the soft
tender flesh of a friend against
the sharp rotating blades of
the immutable machine. pe
Trilema - Un blog de Mircea Popescu. ... (
http://bit.ly/1DqoKb6 )
mircea_popescu: mothefucker.
the
two results lead
to... referneces, without actual link, of
the original.
mod6: my deb machine was installed in december, but maybe
the system wide OpenSSL 1.0.1g was upgraded in feb.
The version
the system wide gives me is April 7 2014.
The xxd output looks like its indicating
the one from
the system.
jurov: no
that's fine, just put short clearsigned comment what are
the other attachments about
jurov: asciilifeform sigh. it expects a clearsigned
text, not just attachments with detached sigs
mod6: we can change
that up.
that's easy enough.
mod6: fair assessment. i
thought
the same
thing at first, and even had all
the libs on our site.
then started
thinking conversely about it.
mircea_popescu: the reason i proposed
that is because i have no doubt
the "originators" will sooner or later run away with
the code.
mod6: so
that's why
that isthe way it is.
mod6: someone also mentioned
that we (the bitcoin foundation) should host
the openssl, bdb, and boost libs on our website for dl. i decided against
that as i like someone
to feel like
they're getting a copy from
the originator. (this is from yesterday)
mircea_popescu: i am happy
to announce
that for
the fy 2014 serenissima ran a whopping 5798796857967496834% deficit
mircea_popescu: fuck
that shit, obama is
the blessed child of
the heavens, can run deficits ?
assbot: Logged on 01-04-2015 22:43:56; ben_vulpes: <mircea_popescu> we could readily employ
thousands. << you and what budget?!
hanbot: asciilifeform> maybe hanbot can
try? gentoo box? << would love
to help out, unfortunately i haven't managed
to get it working quite yet.
mod6: i can
take a look at mine in xxd, just a moment.
mircea_popescu: so it wouldn't have an openssl other
than what auto.sh makes
mod6: <+mircea_popescu> mod6 i
thought you
tested it in vms ? << yup. one virtual box deb 6 vm, one aws deb6 AMI and a friend had a separate deb6 ami. my gentoo
testing was on gentoo aws AMI also.
assbot: Yanis Varoufakis: "Greece
to Adopt
the Bitcoin If Eurogroup Doesn't Give Us a Deal" | GreekReporter.com ... (
http://bit.ly/1G5NtSo )
mod6: <+mircea_popescu>
the idea is, for someone wanting
to copy your environment,
to be able
to do so with minimal work << i
think going forward
this is
the only
thing we'll support/build from/work on, something
that we agree is "good"
assbot: Logged on 01-04-2015 22:26:52; funkenstein_: i don't see
this giant
mod6: <+ascii_field> has any of you lot checked
to see
that
the executable resulting from
this build ACTUALL contains
the openssl built by auto.sh ? << i never did,
this could be a problem
too
mircea_popescu: asciilifeform what's
the peculiarities of said boxes ?
mircea_popescu: people derping about how "bitcoin will fail because
tis or
that" are such fucking idiots, incidentally. COMPUTING NEVER WORKED.
mircea_popescu: asciilifeform incidentally, ever published
the recipe
to obtain
that "statically linked is not statically linked" error ?
mircea_popescu: the only way
to find out is
to hammer
the
things
that worked until we know why
the fuck
they worked.
mircea_popescu: asciilifeform why i'd kinda like
to get
to
the bottom of
this.