00:03:51 <selsta> BigmenPixel[m]: no, the CPU isn't the issue
00:04:07 <selsta> the Arch package has to be compiled with ARCH="default"
00:04:31 <selsta> https://github.com/monero-project/monero-gui/issues/3782
00:22:11 <ga_1700[m]> chaser: you're welcome to discuss this at #monero:monero.social or #monero-pools:monero.social 
01:57:00 <DeanGuss> chaser[m]: Put proxy=127.0.0.1:9050 in monero.conf
01:57:50 <DeanGuss> and tx-proxy=tor,127.0.0.1:9050 to proxy your outgoing transactions
01:58:21 <DeanGuss> or is that deprecated now?  Is a transaction submission in monero different from how a node exchanges transactions with other nodes?
03:10:05 <selsta> DeanGuss: tx-proxy isn't deprecated
03:10:28 <selsta> it's 2 different things
04:13:29 <BigmenPixel[m]> <selsta> "https://github.com/monero-..." <- hmm ... So for the flatpak package for x86_64 architecture I also need to specify ARCH = "default"?
04:13:45 <BigmenPixel[m]> s///, s///
04:14:42 <selsta> do you maintain the flatpak package?
04:14:51 <BigmenPixel[m]> selsta: yes
04:15:00 <selsta> yes
04:19:24 <BigmenPixel[m]> selsta: What about aarch64? Should it work or not?
04:19:49 <BigmenPixel[m]> There is ARCH=armv8-a
04:20:27 <selsta> should what work?
04:20:45 <BigmenPixel[m]> selsta: monero-gui :)
04:21:25 <selsta> monero-gui runs on aarch64 yes
04:22:21 <BigmenPixel[m]> selsta: thanks 
04:26:43 <selsta> BigmenPixel[m]: basically we used to default to x86-64 arch, we removed it to make it work out of the box on ARM too
04:26:59 <selsta> so now it uses "native" arch
04:27:51 <selsta> which is only useful to run the binary on the same CPU as it was compiled on
04:30:54 <BigmenPixel[m]> Ok, I'll fix it now.
08:27:36 <kayabaNerve> I'm building an old Monero node version and linking is failing. `undefined reference to `bool cryptonote::Blockchain::get_transactions_blobs` where the error is within libcryptonote_core already, which is set to be compiled with blockchain.cpp AFAICT. Anyone have any ideas?
15:30:19 <cornfeedhobo> kayabaNerve: my only suggestion is to look at the dockerfile for what ever version you are compiling. it will have hints about the history of the build process in the most concise format
17:27:12 <selsta> kayabaNerve: are you building debug?
17:27:18 <selsta> with clang?
17:27:45 <selsta> try release instead
17:28:09 <selsta> if you need debug you have to apply a patch
20:40:36 <tevador> https://github.com/monero-project/monero/pull/8110 -> a weekend project...
21:16:32 <crypto_grampy[m]> <tevador> "https://github.com/monero-..." <- Siren: 
21:16:59 <crypto_grampy[m]> * Siren
21:43:53 <dEBRUYNE> tevador: Cool! Presumably it works with hw wallets as well?
21:57:50 <tevador> The HTTP wallet simply calls wallet RPC, so it should work AFAIK. Untested.
22:07:14 <tevador> Btw, it seems that the current master branch fails functional tests.
22:25:44 <ack-j[m]> tevador: Is your fork PoC operational yet? Or is it still a work in progress?
22:26:52 <tevador> which fork PoC?
22:27:56 <ack-j[m]> Did you finish the webserver implementation in this? https://github.com/monero-project/monero/pull/8110 
22:28:25 <ack-j[m]> Can I compile and play around with it, is I guess what I'm asking
22:28:37 <tevador> Yes
22:28:38 <ack-j[m]> s/Can I compile and play around with it, is I guess what I'm asking/Can I compile and play around with it, I guess is what I'm asking/
22:28:47 <ack-j[m]> thanks!
22:29:38 <tevador> It works, but it's not feature-complete. Can have some bugs.
22:29:59 <tevador> if you need some testnet coins, I have plenty...
22:35:14 <tevador> On a side note, the official wallet RPC documentation is pretty outdated. https://www.getmonero.org/resources/developer-guides/wallet-rpc.html
22:47:33 <kayabaNerve> selsta: CMAKE .., make, presumably gcc. I'll try expliticly declaring release
22:57:14 <selsta> might be a different issue then
22:58:00 <selsta> you can try bisecting the commit that fixes it and then manually apply that fix for older versions
22:58:37 <selsta> tevador: https://github.com/monero-project/monero/pull/8103 needs an approval
23:09:54 <kayabaNerve> selsta: I couldn't find any meta on why it was occurring actually. 0 search results about that function in issues/prs. I didn't bother digging through the entire link history.
23:19:02 <kayabaNerve> It ends up being all good though. I got what I needed. Thanks for getting back to me on it though :)