rbrunner grumblemobile your guys' comments about binary_archive surprised me so I went back to look at binary_archive, because I didn't think it was epee format. I just confirmed, it is not epee binary format and is something seperate

it's a known issue that the gui wallet will not start monerod with the zmq-rpc-bind-port enabled?

jeffro256[m]: didnt check IRC yesterday - I've been referring to the "other" serialization technique in `src/serialization` as "cryptonote" and the one in `contrib/epee` as "epee"

the cryptonote serialization could be difficult for either of our proposals because there is some custom code in ringct for arrays

I mean, either could handle it afaik, but theres a bit more customization to provide optimal size in the output in places

customization per type I meant

Im getting my serialization branch working with json, and dropping the bulk of the macro changes as it seems like its going to be less painful in the end

I've found a way to forward declare some stuff though, and Im hoping that drops compile times a bit but not certain yet

it definitely moves the template expansions in some files at least

the technique should work with either my proposal or jeffro256[m], but not sure about perfect's daemons approach atm

it might be possible to do this with the existing solution, but it would have to be done in a slightly different way I think

*forward declare some stuff while leaving the serialization macros in the header/struct/class declaration

Hello, I am compiling monerod on an Debian machine and it works perfectly, however if i try running it on another computer it says:

`error while loading shared libraries: libzmq.so.5: cannot open shared object file: No such file or directory`

ZeroMQ is installed on the compiling machine, but not on the machine running monerod.

I am compiling with `make release-static`.

Build libmzq statically (or install a prebuilt one from your OS repo).

Then you likely have to delete any CMakeCache.txt in build before making again.

make release-static will use shared libs if a static one isn't found. Not sure if by design or not.

Thank you for being supportive, i didn't notice the "Building portable statically linked binaries" section in the readme.md

Also ldd monerod when done, and do the same for any remaining libs (stuff like libm, libdl, etc are fine).

But stuff like boost, for example, or unbound, you want to have static.

moneromooo: What does LDD mean?

nvm it's a linux command

when i do `make release-static-linux-x86_64` to statically compile librarie it fails at around 80% with this error:... (full message at <libera.ems.host/_matrix/media/r0/do…5c234bfb932e2bd9648f54f8e903e3feb01>)

when i do `make release-static-linux-x86_64` to statically compile librarie it fails at 85% with this error:... (full message at <libera.ems.host/_matrix/media/r0/do…06df30d08ff4164c636defd6e171da6a96d>)

when i do `make release-static-linux-x86_64` to statically compile librarie it fails at 85% with this error:... (full message at <libera.ems.host/_matrix/media/r0/do…06df30d08ff4164c636defd6e171da6a96d>)

Link against libevent. And then post a patch.

It's happened before, and I guess whoever had that didn't post a patch.

And libnettle as well apparently.

Best if you work out what libs monero uses they're a dep of. Possibly 0mq.

libgmp ? wtf.

Oh, possibly boost bignums...

Oh, it says nettle is from libunbound.

So look for "NORM" in a CMakeLists.txt. It's an optional libzmq dep.

Do the same thing for libnettle/libevent and libundound.

And libgmp. Weird it's in there.

moneromooo: and what should i do? erase any line in cmakelists containing norm?

moneromooo: CMakeLists.txt does not contain libgmp

No. "Do the same" is the opposite of "undo" :)

Yes. That's why "do hte same" as with norm.

undo what exactly?

Nevermind.

i'll try compiling with the dockerfile

I mean something like paste.debian.net/1254379

But also for libevent and libgmp.

I guess this is another time to moan about cmake not using pkg-config, which would probably have avoided this

I guess this is another time to moan about cmake

moan about cmake

I added these lines to CMakeLists.txt at line 1173:... (full message at <libera.ems.host/_matrix/media/r0/do…09a783b40674ef11a0e00fe78af01e98432>)

do subaddresses still "provide weaker protection against malicious counterparties"?

* malicious counterparties" vs separate seeds?

duggavo[m]: monero-project/monero #8439

r4v3r23[m]: yes, likely won't be fixed before Seraphis

selsta: and it applies to accounts vs new seed as well?

selsta: oh maybe now i understand everything

selsta: thanks

Do you *really* mean the same error log persists, or only some of them ?

when i do "make depends target=x86_64-linux-gnu" it prints A TON of errors. Why? It seems it's because the directory i am building monero at contains a space in its name, and maybe something doesn't work because of this

Second, you're building static. Packages on monero distros will install shared libs but not static libs by default if you do not specify.

i am building in `/media/duggavo/hard disk/monero` and maybe it doesn't like that the "hard disk" folder includes spaces

And not all packagers ship static libs.

er, re-reading, I meant modern distros, not monero distros. Muscle memory.

it's possible that a space in the path causes issues with depends, can you share the error message?

selsta: > make depends target=x86_64-linux-gnu

prompted a lot of errors with something like

`/media/duggavo/hard not found` and i was compiling in folder `/media/duggavo/hard disk/monero`

s/>//, s/x86_64/x86\_64/

Right now it's compiling now that i changed folder

Yeah that's an obvious space issue, from that message.

Feel free to replace $X with "$X" if you find them.

ok, the compilation just failed

gperf not found

At least when not in more complex expressions.

I fail to see why gperf would be needed. Are you sure it's an *error*, and not a message next to the error ?

gperf is needed

Why ?

grumblemobile: checking for x86_64-linux-gnu-gperf... no

checking for gperf... no

configure: error: *** gperf not found

duggavo[m]: install these dependencies github.com/monero-project/monero/bl…r/.github/workflows/depends.yml#L48

and line 89

oh i never looked into why, it just has always been a dependency for some reason

selsta: python3-zmq??

try without it

why does it require a python package?

I've never seen monero do any kind of profile guided opt, so... I think it's spurious unless proven otherwise.

Though I suppose some other package dep might require it, spuriously...

<selsta> "duggavo: install these dependenc..." <- Weird, installation of these packages fails with... (full message at <libera.ems.host/_matrix/media/r0/do…e1a64ab65f17cda44fae67dfc136e2162dd>)

> <@selsta:libera.chat> duggavo: install these dependencies github.com/monero-project/monero/bl…r/.github/workflows/depends.yml#L48... (full message at <libera.ems.host/_matrix/media/r0/do…ca20e06380381b227847c4c38c9971bce5d>)

which once exactly?

selsta: install-info

even if i didn't include it in the command to install deps

which OS version are you using?

what? it gives the same error even if i do sudo apt-get install curl

which i previously installed successfully

selsta: Ubuntu 22

ok, then it's better if you just try to use `make release-static`, as it says in the readme depends currently only works for 18.04 and 20.04

but no idea what this java error is, does not seem monero related

selsta: It isn't and i fixed it

selsta: make release-static did not work

did you follow what it said in the link I sent?

you have to add 4 libraries, not 3

selsta: to install dependencies? Yes

<selsta> "duggavo: install these dependenc..." <- this one

in fact, that link was to fix issues with depends

that was before I knew you had Ubuntu 22.04

you have to compile it with `make release-static`, or use docker

19:39 <+grumblemobile> Do you *really* mean the same error log persists, or only some of them ?

can you answer this question?

selsta: No

Because it is still compiling

because if only some are left it means a library is missing

If it is still compiling, how do you know the same errors persist ?

grumblemobile: I said that before installing the dependencies selsta suggested

Now I am trying make release-static

the dependencies I suggested were for make depends, not make release-static

Ok, now the error seems shorter

please use paste.debian.net , (easier for IRC users to read)

duggavo[m]: will check if I can get it working in a VM

duggavo[m]: apt does not install static nettle from what i can tell

duggavo[m]: paste.debian.net/hidden/1014cac8 this worked for me on Ubuntu 22.04 + release-static

.merge+ 8420

Added

binaries for v0.18.1.1 are online and kicking. Thanks to all contributors

selsta were you not able to build release-static on a clean Ubuntu 22.04 install after compiling libunbound-dev?

DId you get the same errors as LocalMonero was getting?

This is really stumping me. Idk what I'm doing, but make release-static just works for me on clean installs after dealing with libunbound

yes, exact same error

jeffro256[m]: these were the steps i did paste.debian.net/hidden/1014cac8

Does it work with master if you build libunbound with just a normal ./configure ?

Instead of with all those options

I don't know but I don't see how this should be libzmq related

binaryFate: I think a number of guys that can do gentian builds don't check this IRC everyday. So they miss the fact that v0.18.1.1 binaries are now out and need validation. I would post your message daily until they finally notice.

selsta huzzah! It failed!

So I'm going to try to narrow it down but the ./configure ... in the unbound repo decided if release-static failed or not

does it even enable static by default?

I'm guessing it doesn't, and that --enable-static flag is what is causes the linking to fail

Is it pertinent that a static monero build links a libunbound which itself is linked statically?

you can check ldd monerod

and try the binary on a complete fresh VM

but generally yes, you want your dependencies to be static

<jeffro256[m]> "This is really stumping me..." <- I went through the same thing 😅

Had to reinstall Ubuntu all over again 🙃 to get monero to compile. I hope this gets fixed ASAP or was it fixed in Monero version 0.18.1.1?

* I went through the same thing 😅

Had to reinstall Ubuntu all over again 🙃 to get monero to compile. I hope this gets fixed ASAP or has it been fixed in Monero version 0.18.1.1?