Bug 184967

Summary: graphics/libdrm regression 2.4.17_1 -> 2.4.50 on ia64 11-current
Product: Ports & Packages Reporter: Anton Shterenlikht <as>
Component: Individual Port(s)Assignee: freebsd-x11 (Nobody) <x11>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Latest   
Hardware: Any   
OS: Any   

Description Anton Shterenlikht 2013-12-18 14:50:00 UTC 
$ pkg version -vx libdrm
libdrm-2.4.17_1                    <   needs updating (port has 2.4.50)

Building with poudriere, I get to this:

=======================<phase: package        >============================
===>  Building package for libdrm-2.4.50
pkg-static: Warning: expecting a boolean for the 'enabled' key of the 'FreeBSD' repo,  the value has been correctly converted, please consider fixing
pkg-static: lstat(/wrkdirs/usr/ports/graphics/libdrm/work/stage/usr/local/include/libdrm/intel_aub.h): No such file or directory
pkg-static: lstat(/wrkdirs/usr/ports/graphics/libdrm/work/stage/usr/local/include/libdrm/intel_bufmgr.h): No such file or directory
pkg-static: lstat(/wrkdirs/usr/ports/graphics/libdrm/work/stage/usr/local/include/libdrm/intel_debug.h): No such file or directory
pkg-static: lstat(/wrkdirs/usr/ports/graphics/libdrm/work/stage/usr/local/lib/libdrm_intel.la): No such file or directory
pkg-static: lstat(/wrkdirs/usr/ports/graphics/libdrm/work/stage/usr/local/lib/libdrm_intel.so): No such file or directory
pkg-static: lstat(/wrkdirs/usr/ports/graphics/libdrm/work/stage/usr/local/lib/libdrm_intel.so.1): No such file or directory
pkg-static: lstat(/wrkdirs/usr/ports/graphics/libdrm/work/stage/usr/local/libdata/pkgconfig/libdrm_intel.pc): No such file or directory
*** Error code 1

The full build log:

http://eis.bris.ac.uk/~mexas/libdrm-2.4.50.log
Comment 1 Edwin Groothuis freebsd_committer freebsd_triage 2013-12-18 14:50:09 UTC 
Responsible Changed
From-To: freebsd-ports-bugs->freebsd-x11

Over to maintainer (via the GNATS Auto Assign Tool)
Comment 2 Niclas Zeising freebsd_committer freebsd_triage 2013-12-19 11:08:59 UTC 
This is a known issue, we are working on a fix.
Regards!
-- 
Niclas Zeising
Comment 3 Anton Shterenlikht 2014-01-29 10:58:02 UTC 
Any progress?
Any workaround possible?

This failure blocks most of the other
ports I use, so would be great to find
at least a temp. workaround.

Thanks a lot

Anton
Comment 4 Koop Mast freebsd_committer freebsd_triage 2014-01-31 21:02:33 UTC 
State Changed
From-To: open->closed

Fix committed, thanks for reporting!