Bug 89680 - Hard link exist in Mesa 10.5.1 sources
Summary: Hard link exist in Mesa 10.5.1 sources
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Mesa core (show other bugs)
Version: 10.5
Hardware: All All
: medium normal
Assignee: mesa-dev
QA Contact: mesa-dev
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-19 15:11 UTC by Alexander von Gluck
Modified: 2015-03-28 22:08 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Alexander von Gluck 2015-03-19 15:11:53 UTC
There is a hardlink in the Mesa 10.5.1 sources that needs repaired / converted to a soft link:

On Linux:
$ ls -i src/gallium/state_trackers/egl/x11/dri2.c 
919395 src/gallium/state_trackers/egl/x11/dri2.c
$ ls -i src/glx/dri2.c 
919395 src/glx/dri2.c

On Haiku:
/Builds> tar xf mesa-10.5.1.tar.gz
tar: mesa-10.5.1/src/gallium/state_trackers/egl/x11/dri2.c: Cannot hard link to ‘mesa-10.5.1/src/glx/dri2.c’: Operation not supported
tar: Exiting with failure status due to previous errors

It looks as though this issue was introduced here:
http://cgit.freedesktop.org/mesa/mesa/commit/src/gallium/state_trackers/egl/x11/dri2.c?h=10.5&id=8443efdf2c7772f18e8209b6b6cfc6b19e638423
Comment 1 Matt Turner 2015-03-19 15:24:01 UTC
Probably just want to backport the gallium/egl state tracker removal to 10.5.
Comment 2 Emil Velikov 2015-03-19 18:08:14 UTC
Fear that we have links in src/mesa/drivers/dri/r200, which became hard ones with 10.5 as well. So porting that over will not really cut it.

I will check who exactly is causing this - tar or autotools, and will look into a proper way to handle it.
Comment 3 Emil Velikov 2015-03-28 22:08:24 UTC
Upon closer look the r200 ones are dereferenced upon compression, so a second copy of the files is shipped.

Alexander, 10.5.2 should resolve this bug plus it adds the egl/haiku files, so that you guys actually have the source to actually build stuff :-)

Thanks
Emil


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.