Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 506538 - x11-libs/libxshmfence-1.1 fails with ABI_X86="64 32"
Summary: x11-libs/libxshmfence-1.1 fails with ABI_X86="64 32"
Status: RESOLVED DUPLICATE of bug 506056
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Library (show other bugs)
Hardware: AMD64 Linux
: Normal normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-02 11:34 UTC by Tres 'RiverRat' Melton
Modified: 2014-04-02 13:32 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Attachments
emerge --info (emerge--info.office.txt,15.96 KB, text/plain)
2014-04-02 11:51 UTC, Tres 'RiverRat' Melton 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tres 'RiverRat' Melton 2014-04-02 11:34:46 UTC 
emerging x11-libs/libxshmfence with the ABI_X86="64 32" in make.conf yields:

x11-libs/libxshmfence-1.1  USE="-static-libs" ABI_X86="32 (64) (-x32)"

It fails in the ./configure section with:

checking for linux/futex.h... yes
checking for XPROTO... no
configure: error: Package requirements (xproto) were not met:
           
No package 'xproto' found
--------------------------
re-emerging xproto doesn't work.

This does work:
ABI_X86="64" emerge -av1 x11-libs/libxshmfence

Perhaps disabling the 32 bit API on 64 bit archs which seems a rather common thing to do.  Alternatively you could follow the output of ./configure:

Alternatively, you may set the environment variables XPROTO_CFLAGS
and XPROTO_LIBS to avoid the need to call pkg-config.
Comment 1 Tres 'RiverRat' Melton 2014-04-02 11:44:51 UTC 
Emerge --info:
http://bpaste.net/show/196677/
Comment 2 Tres 'RiverRat' Melton 2014-04-02 11:51:29 UTC 
Created attachment 374084 [details]
emerge --info
Comment 3 Jeroen Roovers (RETIRED) gentoo-dev 2014-04-02 13:32:42 UTC 

*** This bug has been marked as a duplicate of bug 506056 ***