Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [ISSUE] firefox 69 fails build with some options disabled
Date: Fri, 06 Sep 2019 21:57:10 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14269@inbox.vuxu.org> (raw)

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

New issue by svenper on void-packages repository

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

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:  
  firefox-69.0_1: broken, unresolvable shlib `libdbus-glib-1.so.2'
Transaction aborted due to unresolved shlibs.
dmesg: read kernel buffer failed: Operation not permitted
Void 5.2.11_1 x86_64-musl GenuineIntel uptodate hold rrnFFFFFFFFFFF
* package:  
  firefox-69.0_1

### Expected behavior

Firefox can either build without dbus, or does not have dbus optional.

### Actual behavior

Firefox does not build without these template options. References to `dbus::Error::empty`, `dbus::connection::Connection::get_private`, `dbus::connection::Connection::conn_from_ptr`, `dbus::watch::WatchList::new`, etc. fail. Lots of lines of 
```
/usr/bin/ld: DWARF error: mangled line number section (bad file number)
```

Building firefox on my machine is quite slow so I've yet to find exactly what build options cause the fail but it looks like dbus based on the log.

[end of log](https://gist.githubusercontent.com/svenper/93c4ff5f5b78cead49c482ce091abcd2/raw)

### Steps to reproduce the behavior

```
./xbps-src pkg firefox -o alsa,~dbus,~pulseaudio,~sndio,~startup_notification,~wayland,~xscreensaver
```

             reply	other threads:[~2019-09-06 19:57 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-06 19:57 voidlinux-github [this message]
2019-09-06 22:48 ` voidlinux-github
2019-10-01 13:50 ` voidlinux-github
2019-10-01 13:51 ` voidlinux-github
2020-01-25 22:01 ` voidlinux-github
2020-01-25 22:08 ` voidlinux-github
2020-02-22  9:41 ` svenper
2020-02-22 11:09 ` svenper
2020-03-31 19:56 ` svenper
2020-03-31 19:56 ` svenper
2020-05-31 13:30 ` svenper
2020-05-31 13:31 ` svenper
2020-05-31 13:32 ` dylanaraps
2020-05-31 13:51 ` Duncaen
2020-05-31 13:51 ` pullmoll
2020-05-31 14:02 ` svenper
2020-05-31 14:02 ` svenper
2020-05-31 14:04 ` Duncaen
2020-05-31 19:40 ` svenper
2020-05-31 19:40 ` svenper
2020-05-31 19:42 ` svenper
2020-05-31 19:49 ` svenper
2020-05-31 19:50 ` svenper
2020-05-31 19:50 ` svenper
2020-05-31 19:51 ` svenper
2020-12-13 21:48 ` ericonr
2020-12-14 16:22 ` svenper
2020-12-14 16:24 ` svenper
2020-12-14 19:36 ` ericonr
2020-12-14 19:36 ` [ISSUE] [CLOSED] " ericonr

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-14269@inbox.vuxu.org \
    --to=voidlinux-github@inbox.vuxu.org \
    --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).