[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: xorgproto replacing lots of fooproto
From: Thomas Klausner <wiz%NetBSD.org@localhost>, Date: Sat, 10 Mar 2018 00:00:18 +0100
> On Fri, Mar 09, 2018 at 04:49:34PM +0000, Martin Husemann wrote:
>> On Wed, Mar 07, 2018 at 01:01:12PM +0100, Thomas Klausner wrote:
>> > I've now switched all packages to use xorgproto.
>> > I've tested this with modular x.org and ~500 affected packages, which
>> > still built as well as before for me (some better, because I fixed
>> > them ;) ).
>> > I did not provide a builtin.mk file because I couldn't think of a
>> > reasonable solution, and the xorgproto package is small and
>> > built-dependency only.
>> > pkgtools/x11-links might need fixes, I hope someone can do that for
>> > native builds.
>> Would this cause pkgs trying to build libX11 from pkgsrc even for
> Someone else also saw this, but I don't understand why that would happen.
I have same problem.
I think native libX11 depends on non-native xorgproto
and this situation cause this problem.
I have half baked builtin.mk for xorgproto in my local tree.
After some improvements, I would like to commit my changes.
>> That is what I see right now trying to build x11/rxvt on mips64-eb.
Ryo ONODERA // ryo%tetera.org@localhost
PGP fingerprint = 82A2 DC91 76E0 A10A 8ABB FD1B F404 27FA C7D1 15F3
Main Index |
Thread Index |