Summary: | Stabilize app-emulation/libdsk-1.2.1 (Was: app-emulation/libdsk-1.1.5 fails to compile due to fail in function 'open') | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Stefano Priore <stefano.priore> |
Component: | [OLD] Keywording and Stabilization | Assignee: | No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it <maintainer-needed> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | stefano.priore |
Priority: | High | Keywords: | PMASKED, STABLEREQ |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 402857 | ||
Bug Blocks: |
Description
Stefano Priore
2009-10-19 15:02:32 UTC
This is a type of bug that becomes exposed when compiling newer compilers. Please try building ~x86 version of libdsk and see if that works for you. You probably should file a separate bug for gpart btw. The upstream for that one seems to be gone, so gentoo maintainers would need to patch it (or else recommend an alternative package that is still being maintained). >/usr/include/bits/fcntl2.h:51: error: call to '__open_missing_mode' declared
>with attribute error: open with O_CREAT in second argument needs 3 arguments
fcntl2.h belongs to glibc. Try re-emerging glibc.
Did you switch from hardened to non-hardened profile?
there is no bug in glibc. the error already tells you exactly the problem and libdsk sucks here, so fix it. newer versions of libdsk have already been fixed, so maybe just stabilize it. Same at home: Solution 1: version bumping Solution 2: src_compile() { econf \ --with-zlib \ --with-bzlib \ --enable-floppy \ $(use_with java jni) \ --with-java-prefix=${JAVA_HOME} \ || die sed -i 's/O_CREAT |//' lib/rpctios.c || die "C" sed -i 's/O_CREAT |//' tools/serslave.c || die "C" emake || die "libdsk make failed!" } It's the solution the upstream develloper choose in libdsk-1.2.1, so it seems right for me, but at this point I didn't checked deep enough to say if they added some integrity test or not. So version bumping is the solution I chose SAm amd64 stable (In reply to comment #5) > amd64 stable sorry, bad bug Remove arches from CC as pacho suggested because of bug 402857 dropped |