libera #monero-dev

4 Nov 2021

Official repo: github.com/monero-project/monero || Don’t ask to ask, just ask:) || Monero GUI dev is at #monero-gui || Monero website dev is at #monero-site || Non-dev questions -> #monero, please || No fork help, you’re on your own

• 06:42
  merope
  Getting some weird errors while trying to compile the latest release-v0.17 tag:
• 06:42
  merope
  `make[3]: *** No rule to make target '/usr/lib/x86_64-linux-gnu/libprotolib.a', needed by 'bin/monero-blockchain-prune-known-spent-data'. Stop.`
• 06:42
  merope
  `make[3]: *** No rule to make target '/usr/lib/x86_64-linux-gnu/libprotolib.a', needed by 'bin/monero-blockchain-mark-spent-outputs'. Stop.`
• 06:56
  merope
  (Last time I compiled and ran successfully was after commit `24813330ece3bc31d4b5b84759560d5f59736f6e`)
• 07:02
  merope
  (Correction: last known good commit was `2243318000b8fa746a4d874ad62984d6ce25d494`)
• 07:03
  merope
  Currently compiling on Ubuntu 21.04 x86_64
• 07:25
  merope
  Ah nvm, looks like I just had to `make clean` and start from scratch
• 15:25
  mj-xmr[m]
  .merges
• 15:25
  xmr-pr
  8021 8023 8031 8032 8037
• 15:34
  RustyLumberjack[
  how come when calling sync_info on the monerod rpc it says moo
• 15:34
  RustyLumberjack[
  "next_needed_pruning_seed": 0,
• 15:34
  RustyLumberjack[
  "overview": "[mooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo]",
• 15:35
  UkoeHB
  lmao
• 15:36
  moneromooo
  Each character represents a set of blocks in a download queue when you're syncing.
• 15:36
  moneromooo
  . means a set that's been requested
• 15:37
  moneromooo
  o means it's been received
• 15:37
  moneromooo
  m means it's been received and matches what we need next
• 15:37
  moneromooo
  There are a few other less used characters.
• 15:37
  LyzaLittle
  well that's fun
• 15:38
  moneromooo
  So moooooo means you're not blocked, and have several sets of data lined up for processing.
• 15:38
  moneromooo
  The overview above is very good. You won't block on network for a while.
• 15:48
  RustyLumberjack[
  lmaooooo okay thankyou for that clarification
• 19:35
  chaser[m]
  is support in Trezor One a question of engineering, or is it physically impossible?
• 20:43
  dEBRUYNE
  chaser[m]: I think the device has insufficient memory to create Monero transactions
• 21:53
  wfaressuissia
  "mcudev.github.io/trezor-model-t-dev-kit/index.html", "st.com/en/microcontrollers-microprocessors/stm32f427-437.html" 256Kbytes of SRAM
• 21:53
  wfaressuissia
  "mcudev.github.io/trezor-dev-kit/index.html", "st.com/en/microcontrollers-microprocessors/stm32f205rg.html" 128KBytes of SRAM
• 21:54
  wfaressuissia
  "is support in Trezor One a question of engineering ..." likely yes
• 22:42
  chaser[m]
  thank you
• 22:45
  chaser[m]
  could Seraphis, or the ring size increases that come after it, require more than 128 kB?
• 22:52
  UkoeHB
  It shouldn’t