Github messages for voidlinux
 help / color / mirror / Atom feed
From: loreb <loreb@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] anacron fails to start due to missing symbol
Date: Wed, 09 Sep 2020 23:43:42 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24792@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1282 bytes --]

New issue by loreb on void-packages repository

https://github.com/void-linux/void-packages/issues/24792

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System

* xuname:  
  Void5.8.7_1 x86_64-musl
* package:  
  cronie-1.5.5_3 with musl-obstack-1.2_1

### Expected behavior
anacron runs

### Actual behavior

> Error relocating anacron:  obstack_free: symbol not found

### Steps to reproduce the behavior
Update musl-obstack to latest version - https://github.com/void-linux/musl-obstack/commit/91923c732016e2d5021c3992eb1eca7779cf8922 "gets rid of" obstack_free;
If I'm reading the patch correctly obstack_free used to be a function and it's now a macro;
anacron is linked dynamically to the old version, so it tries to call a function that no longer exists.

It seems that upstream now includes obstack (https://github.com/cronie-crond/cronie/commit/fd934a8292805fa29a27c0d9c3ee79d1fc1ea9fc);
just recompiling the master branch from there worked and ran on my machine,
so I expect that simply recompiling should work,
and if not updating worked for me(tm).

Please let me know if there's any problem.


             reply	other threads:[~2020-09-09 21:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-09 21:43 loreb [this message]
2020-09-09 22:40 ` ericonr
2020-09-09 22:41 ` ericonr
2020-09-11 16:23 ` ericonr
2020-09-11 16:23 ` ericonr
2020-09-12  0:19 ` [ISSUE] [CLOSED] " the-maldridge

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24792@inbox.vuxu.org \
    --to=loreb@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).