| Git Clone URL: | https://aur.archlinux.org/lib32-libcdio.git (read-only, click to copy) |
|---|---|
| Package Base: | lib32-libcdio |
| Description: | GNU Compact Disc Input and Control Library (32-bit) |
| Upstream URL: | https://www.gnu.org/software/libcdio/ |
| Licenses: | GPL3 |
| Submitter: | arojas |
| Maintainer: | rodrigo21 |
| Last Packager: | rodrigo21 |
| Votes: | 5 |
| Popularity: | 0.000000 |
| First Submitted: | 2018-03-12 09:25 (UTC) |
| Last Updated: | 2021-12-29 18:00 (UTC) |
The pkgbuild is broken for a modern compiler. To fix, add "-fpermissive" flag to each of the var exports on line 29-31:
export CC="gcc -m32 -fpermissive"
export CXX="g++ -m32 -fpermissive"
export PKG_CONFIG_PATH="/usr/lib32/pkgconfig"
Credit goes to the person posting about this here: https://bbs.archlinux.org/viewtopic.php?id=300561
I'm having the same issue with the lseek64 function when building. I'm unable to run some GE-Proton apps because this is a dependency of gst-libav.
Still failing to build:
_cdio_generic.c: In function 'cdio_generic_lseek':
_cdio_generic.c:63:20: error: implicit declaration of function 'lseek64'; did you mean 'lseek'? [-Wimplicit-function-declaration]
63 | #define CDIO_LSEEK lseek64
| ^~~~~~~
I guess the gcc version changed or something and warnings got upgraded
I had problem building this package because it tried to use lseek64 without correctly including the needed header file. (You need to define _LARGEFILE64_SOURCE before including <sys/types.h>)
I "fixed" it by adding --disable-largefile to ./configure in the PKGBUILD
Does anyone know why this failed for me? The code hasn't changed in years.
Originally I was maintaining the package mostly for lib32-gst-plugins-bad for wine, but things like proton-GE-bin is a better option, I'll orphan this project for guys who really need it.
Running gpg as described in the pinned post results
gpg --recv-keys 1A8DE5008275EC21
gpg: keyserver receive failed: No name
What do I need to do?
@Norgra do you still have troubles installing the package? It's fine for me, adding the respective public key to trusted keys allows to install it without issues.
@frealgagu
gpg: key 1A8DE5008275EC21: 2 duplicate signatures removed
gpg: key 1A8DE5008275EC21: "R. Bernstein rocky@panix.com" not changed
gpg: Total number processed: 1
gpg: unchanged: 1
@Norgra What appears when you execute gpg --recv-keys 1A8DE5008275EC21 ?
Pinned Comments
frealgagu commented on 2018-03-14 11:55 (UTC)
If you get "FAILED (unknown public key 1A8DE5008275EC21)", add that key to your trusted keys as follow:
gpg --recv-keys 1A8DE5008275EC21
And then try to install/upgrade it again.