From: unspecd <unspecd@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] cups-filters, libzbar fail to build
Date: Mon, 14 Nov 2022 23:57:45 +0100 [thread overview]
Message-ID: <20221114225745.prAK7dTQJ2lzsdnzzRO1cst3r0UGGGQeC-cf7QzqDpo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40533@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2331 bytes --]
Closed issue by unspecd on void-packages repository
https://github.com/void-linux/void-packages/issues/40533
Description:
### Is this a new report?
Yes
### System Info
Void 6.0.7_1 x86_64-musl GenuineIntel notuptodate FFFF
### Package(s) Affected
cups-filters-1.28.15_2, libzbar-0.23.1_6
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
None.
### Expected behaviour
./xbps-src pkg should build packages
### Actual behaviour
#### cups-filters
```shell
$ ./xbps-src -NE pkg cups-filters
...
CCLD libcupsfilters.la
/usr/bin/ld: /usr/lib64/gcc/x86_64-linux-musl/10.2.1/../../../../lib64/libdbus-1.a(libdbus_1_la-dbus-sysdeps.o): warning: relocation against `stderr' in read-only section `.text'
/usr/bin/ld: /usr/lib64/gcc/x86_64-linux-musl/10.2.1/../../../../lib64/libdbus-1.a(libdbus_1_la-dbus-sysdeps-unix.o): relocation R_X86_64_PC32 against symbol `stdout' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: final link failed: bad value
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:2535: libcupsfilters.la] Error 1
make[2]: Leaving directory '/builddir/cups-filters-1.28.15'
make[1]: *** [Makefile:4853: all-recursive] Error 1
make[1]: Leaving directory '/builddir/cups-filters-1.28.15'
make: *** [Makefile:2086: all] Error 2
```
#### libzbar
```shell
$ ./xbps-src -NE -pkg libzbar
...
CCLD libzbar.la
/usr/bin/ld: /usr/lib64/gcc/x86_64-linux-musl/10.2.1/../../../../lib64/libdbus-1.a(libdbus_1_la-dbus-sysdeps.o): warning: relocation against `stderr' in read-only section `.text'
/usr/bin/ld: /usr/lib64/gcc/x86_64-linux-musl/10.2.1/../../../../lib64/libdbus-1.a(libdbus_1_la-dbus-sysdeps-unix.o): relocation R_X86_64_PC32 against symbol `stdout' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: final link failed: bad value
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:818: libzbar.la] Error 1
make[2]: Leaving directory '/builddir/zbar-0.23.1/zbar'
make[1]: *** [Makefile:1905: all-recursive] Error 1
make[1]: Leaving directory '/builddir/zbar-0.23.1'
make: *** [Makefile:985: all] Error 2
```
### Steps to reproduce
1. `./xbps-src -NE pkg cups-filters`
2. `./xbps-src -NE pkg libzbar`
prev parent reply other threads:[~2022-11-14 22:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 20:47 [ISSUE] " unspecd
2022-11-14 20:54 ` unspecd
2022-11-14 21:41 ` unspecd
2022-11-14 21:45 ` kruceter
2022-11-14 22:05 ` paper42
2022-11-14 22:07 ` paper42
2022-11-14 22:57 ` unspecd
2022-11-14 22:57 ` unspecd [this message]
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=20221114225745.prAK7dTQJ2lzsdnzzRO1cst3r0UGGGQeC-cf7QzqDpo@z \
--to=unspecd@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).