Happy New Year!!!
Great work by great people
-K___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev
Here's a PR to cleanup the warning and pkgconfig nits
(Make the Check-patches output clean)
https://github.com/illumos/gfx-drm/pull/3
On Sat, Dec 31, 2016 at 12:57 AM, Gordon Ross wrote:
> I've been only occasionally available the last couple weeks.
> I see you
I've been only occasionally available the last couple weeks.
I see you committed the pkgconfig, which is fine of course,
but now Check_patches doesn't run "clean"...
I'll need to fix that before the next version bump in libdrm.
BTW, does the upstream (libdrm development) really use
Do we really need the libdrm symlink?
I assumed we could have just .../include/drm
On Wed, Dec 28, 2016 at 4:08 AM, Alexander Pyhalov wrote:
> On 12/28/16 12:03 AM, ran...@sibernet.com wrote:
>>
>>
>>
>> On Tue, 27 Dec 2016, Alexander Pyhalov wrote:
>>
>>>
>>> Gordon, it seems the
Suggesting use of the 2016Q4 Intel release notes as explained in IRC.
Upstream have other thoughts?
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev
On 12/28/16 12:03 AM, ran...@sibernet.com wrote:
On Tue, 27 Dec 2016, Alexander Pyhalov wrote:
Gordon, it seems the following patch fixes the issue:
https://github.com/pyhalov/gfx-drm/commit/b1ebcc82b300cdb4abd4ad83b0b1b832758fb73f
Current patch mechanism in gfx-drm is ugly, so I had to
On Tue, 27 Dec 2016, Alexander Pyhalov wrote:
Gordon, it seems the following patch fixes the issue:
https://github.com/pyhalov/gfx-drm/commit/b1ebcc82b300cdb4abd4ad83b0b1b832758fb73f
Current patch mechanism in gfx-drm is ugly, so I had to update also another
patch, touching *.pc.in files,
Migrate your work to libdrm 2.4.74 and we'll scan it for our compliance review.
~ Ken
On Tuesday, December 27, 2016 7:17 AM, Alexander Pyhalov
wrote:
On 12/27/16 02:02 PM, Alexander Pyhalov wrote:
> On 12/26/16 09:17 PM, Andreas Wacknitz wrote:
>> Hi,
>>
>> I have two
On 12/27/16 02:02 PM, Alexander Pyhalov wrote:
On 12/26/16 09:17 PM, Andreas Wacknitz wrote:
Hi,
I have two kind of problems building and publishing packages with drm.
1. #include fails for several packags now.
I don't know whether this is simply because of a missing include
path or
On 12/26/16 09:17 PM, Andreas Wacknitz wrote:
Hi,
I have two kind of problems building and publishing packages with drm.
1. #include fails for several packags now.
I don't know whether this is simply because of a missing include
path or something else.
Example packages: x11/mesa,
Hi,
i experienced this problems also.
Best regards,
Alex
On 12/26/16 07:17 PM, Andreas Wacknitz wrote:
Hi,
I have two kind of problems building and publishing packages with drm.
1. #include fails for several packags now.
I don't know whether this is simply because of a missing include
Hi,
I have two kind of problems building and publishing packages with drm.
1. #include fails for several packags now.
I don't know whether this is simply because of a missing include
path or something else.
Example packages: x11/mesa, x11/redshift, x11/tigervnc,
x11/xf86-video-ati,
12 matches
Mail list logo