me-tools | small tools , Taobao grab bag xposed module | JSON Processing library

Yesterday I tried to install Ejabberd first through souce code

Just curiosity: what problems did you find, that prefered to use the Ubuntu package?

Did you install from source code? If so, did you later uninstall it? Maybe uninstallation left some files there (there was some bug related to that in make uninstall)... it will help if you can take a look at the installation paths and remove the remaining ejabberd files and directories, specially the file ejabberdctl.

and then with Ubuntu specific packages

Well, it could be that both installations get mixed... or maybe the Ubuntu package has some problem unrelated to your previous installation. Keep all investigation lines open :)

{"init terminating in [do_boot",{undef,[{ejabberd_ctl,start,[],

This error message says that erlang cannot find the file ejabberd_ctl.beam, or that the file doesn't define the function start.

Just a wild idea: maybe you are running the "ejabberdctl" script from source installation (pointing to the old ejabberd beam files), but now you have the ejabberd beam files installed in a different location (by the Ubuntu package).

My first question is, does the order matter here?

Yes, literally from gcc documentation:

-l library

...

It makes a difference where in the command you write this option; the linker searches and processes libraries and object files in the order they are specified. Thus, ‘foo.o -lz bar.o’ searches library ‘z’ after file foo.o but before bar.o. If bar.o refers to functions in ‘z’, those functions may not be loaded.

how to tell the linker(?) that there is a strong definition of the function in another static library, or something along those lines?

Typically in modern embedded:

Can't comment since too low rep, but have you tried adding the -msoft-float flag also where are you running that command/program, like hardware specs? depending on your hardware specs it may be the complete opposite and therefore you should try to avoid the double keyword Could you also share some code?

I had Erlang 23 and RabbitMQ Server 3.8.2 (they are not fully compatible so I decided to upgrade RabbitMQ Server to 3.8.9 because I had some problems running my app)

I have a cluster with one node on AWS EC2 instance of Ubuntu 20.04 (unconfigured yet properly as RabbitMQ advises via plugin - I plan to do it later).

What I did and it worked for me (following commands executed under sudo or root sudo su):

1. It's important to shutdown not just stop_app as Erlang also needs to be stopped and stop_app only stops RabbitMQ Server leaving Erlang on which would later might give you error while starting new version of the RabbitMQ Server - for port 25672 being busy with another app:

   rabbitmqctl shutdown

2. Change in rabbitmq file from old version (I had for some strange reason 3.8.8 instead of 3.8.2 which I run) to a new one - in my case 3.8.9:

   vim /etc/apt/preferences.d/rabbitmq

3. Recheck if dependencies are installed:

   apt-get -y install socat logrotate init-system-helpers adduser

4. Install wget if you don't have it:

   apt-get -y install wget

5. Download latest .deb package of server installation file:

   wget https://github.com/rabbitmq/rabbitmq-server/releases/download/v3.8.9/rabbitmq-server_3.8.9-1_all.deb

6. Install it:

   dpkg -i rabbitmq-server_3.8.9-1_all.deb

7. Remove distro:

   rm rabbitmq-server_3.8.9-1_all.deb

8. Check if server stopped (may be redundant command):

   service rabbitmq-server stop

9. Restart server:

   service rabbitmq-server restart

10. Check server status:

    rabbitmq-server status

11. If it gives you an error BOOT FAILED. Distribution port 25672 is in use by another node, check who uses that port it may be that Erlang uses that port:

    lsof -i :25672

12. Start RabbitMQ app:

    rabbitmqctl start_app

13. Check status of node:

    rabbitmqctl status

You should see upgraded RabbitMQ Server version (in my case 3.8.9) along with you recent Erlang version (in my case 23)

The early 4.4.x kernels do not boot when built with binutils >= 2.31. This was fixed in commit https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=073bb7ddd35ca8f17a170258dacbe384935a43c8 in the 4.4.x stable branch, which was merged in 4.4.124. So any 4.4.x earlier than that, when built with binutils >= 2.31, will not boot.

Go to the page: https://www.erlang-solutions.com/resources/download.html and download the latest version for raspbian buster.

Then in Raspbian type

The packages erlang-ftp and erlang-tftp were introduced in Ubuntu 19.04 (disco), and are thus not present in bionic. Just leave them out of the command; they're not required for RabbitMQ to function.

Match the last two digits as optional and capture the first five, and assign the capture directly

Now we can see how the compiler complains (thanks for the update in the question), it looks as though you have an installation problem.

Here, I get (edited down to remove the less significant parts)