Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

date.c:(.text.date_main+0x2b6): undefined reference to `stime' #51

Closed
adrianmace opened this issue Sep 27, 2020 · 6 comments
Closed

date.c:(.text.date_main+0x2b6): undefined reference to `stime' #51

adrianmace opened this issue Sep 27, 2020 · 6 comments

Comments

@adrianmace
Copy link

image

Seems to be occurring on both master and devel as of today's commits.

Ubuntu 20.04 LTS.

@phicoh
Copy link

phicoh commented Sep 28, 2020

Please check the git commit in probe-busybox. It should be 1c80e1953a5794660d39c731d0fdac77f34aed9b, which is version where stime is removed.

@snh
Copy link

snh commented Sep 28, 2020

@phicoh RIPE-NCC/ripe-atlas-probe-measurements@fb8bc97 appears to be the current tip of master (the default branch), with only devel containing RIPE-NCC/ripe-atlas-probe-measurements@1c80e19.

Do you know if this going to move to master soon so that this will be picked up automatically for those cloning ripe-atlas-software-probe?

@phicoh
Copy link

phicoh commented Sep 28, 2020

The problem is that when we do a release, we sign the centos binaries (and the firmware for the hardware probes). Due to corona, nobody is going to the office to do the signing. And the changes are not really big enough. Though I understand that the current situation is annoying for people running ubuntu. I have to see if we can do a release that is just source code.

@h289072
Copy link

h289072 commented Mar 13, 2021

So is there a workaround? I've deliberately upgraded to ubuntu 20.04 before installing the software probe.

@h289072
Copy link

h289072 commented Mar 13, 2021

So is there a workaround? I've deliberately upgraded to ubuntu 20.04 before installing the software probe.

Ah ok... checking out 142acd3673051769debd8fd7261b121fb7b4f609 will do it

@PhilipHomburg
Copy link
Collaborator

Fixed in master

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants