20:32:02 <lvlinux> mc_ does 4.3 only compile on Erlang 19 or will it work on later?
20:32:28 <mc_> lvlinux: i think i've seen 22 used
20:32:48 <mc_> not sure that 23 would work, there are breaking changes that either kazoo or a 3rd party dep break on
20:32:54 <mc_> forget which
20:33:04 <lvlinux> I installed OTP25 (default from erlang solutions) on a Debian 10 box, and it failed in: src/app_utils.erl: error in parse transform 'lager_transform':
20:33:13 <lvlinux> Ah ok so i should go back at least to 22
20:33:49 <lvlinux> i'll have to figure out how to revert lol
20:35:41 <lvlinux> Do you recommend that I do 22 or earlier like 19?
20:52:45 <mc_> lvlinux: 19.3 is "recommended" but i think 21 for sure still works, and 22 may work
20:52:52 <mc_> i use kerl to manage OTP installations locally
20:52:58 <mc_> rather than packages
20:53:01 <mc_> but up to you
21:01:41 <lvlinux> k thx
21:03:50 <lvlinux> mc_ I can compile in one version like 19/20/21, on say, debian, and then move an application ebin file to a centos system running from official repo packages, right? Or do I have to compile on a matching system?
21:16:59 <mc_> in general, OTP is compat for 2 major versions
21:17:05 <mc_> but we don't really test that too far
21:17:24 <mc_> so ideally you run on a VM compiled for the same BEAM version 
21:19:49 <lvlinux> k
21:20:54 <lvlinux> I installed v22.2.7 and it failed build at a different place (building cowboy), so I guess I'll try kerl and do v19. 
23:56:49 <lvlinux> src/cowboy_http.erl:388: variable '_Stacktrace' is unbound
23:56:54 <lvlinux> Hmm...