Re: How do I compile and package the X Server code?
On Tue, Feb 12, 2019 at 01:19:51PM -0500, Adam Jackson wrote: > On Tue, 2019-02-12 at 17:22 +0100, Kevin Brace wrote: > > > I am able to compile X Server, although I do not know at this point > > how to install it to my preferred location (I will like to install it > > to /opt for testing purposes). > > https://www.gnu.org/software/autoconf/manual/autoconf-2.63/html_node/Default-Prefix.html > > You will probably also want to override PKG_CONFIG_PATH in the > environment when building drivers against that server. Refer to the > pkgconfig documentation for details, but it's probably something like: > > $ export > PKG_CONFIG_PATH=/opt/xorg/share/pkgconfig:/opt/xorg/lib64/pkgconfig:$PKG_CONFIG_PATH > > That said... in my experience, one of the pleasant features of using a > distribution is that you can reinstall packages. If I ever really do > want to test a new buld of Xorg (the only server where the install path > really matters) I just clobber the existing one, and when I'm done, dnf > reinstall xorg-x11-server-*. > > > How do I install it to my preferred location and run the compiled > > version rather than the existing version? > > If you're invoking the X server by hand, just do: > > # /opt/xorg/bin/Xorg > > Convincing your desktop environment's display manager to invoke that > one instead of the one in /usr/bin depends on the particular display > manager. (Not wanting to remember how to do this is part of the reason > I don't use prefixes...) ftr, I've been installing into /opt/xorg for years, my gdm solution is: $ mv /usr/bin/Xorg /usr/bin/Xorg_old $ ln -s /opt/xorg/bin/Xorg /usr/bin/Xorg That works but if you use SELinux it may require relabelling and other magic. As for the environment, I have this as $HOME/.exportrc.xorg: export PKG_CONFIG_PATH=/opt/xorg/lib/pkgconfig:/opt/xorg/lib64/pkgconfig:/opt/xorg/share/pkgconfig export LD_LIBRARY_PATH=/opt/xorg/lib/:/opt/xorg/lib64 export PATH=/opt/xorg/bin:$PATH export ACLOCAL_PATH="/opt/xorg/share/aclocal" export ACLOCAL="aclocal -I $ACLOCAL_PATH" export MANPATH=/opt/xorg/share/man/:/usr/share/man set up an alias to source that file on command and run it before you you run autotools/meson. The trickiest bit is remembering when --libdir is needed and when not :) Cheers, Peter ___ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: https://lists.x.org/mailman/listinfo/xorg-devel
[PATCH xf86-video-chips] X Server crash fix for non-HiQ Video C devices
Due to a faulty new vgaHW ABI conversion commit, X Server was crashing on non-HiQ Video Chips & Technologies devices. This patch fixes that bug. -- Kevin Brace (1): Fix for a faulty new vgaHW ABI conversion on non-HiQ Video devices src/ct_driver.c | 2 ++ 1 file changed, 2 insertions(+) -- 2.7.4 ___ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: https://lists.x.org/mailman/listinfo/xorg-devel
[PATCH xf86-video-chips] Fix for a faulty new vgaHW ABI conversion on non-HiQ Video devices
Unfortunately, commit 989cf4f1fb2ac57f38d363734b71a5cf749db146 missed inserting a call to vgaHWSetStdFuncs prior to calling vgaHWGetIOBase for non-HiQ Video devices, so this will cause a crash with the X Server. The code has three different chipsPreInit* to handle some aspects of a PreInit callback, but only chipsPreInitHiQV function has the correct code. Added the call to vgaHWSetStdFuncs for chipsPreInit655xx and chipsPreInitWingine functions. This bug was observed on Chips & Technologies 65548. Signed-off-by: Kevin Brace --- src/ct_driver.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/ct_driver.c b/src/ct_driver.c index 6603e6b..b4b8422 100644 --- a/src/ct_driver.c +++ b/src/ct_driver.c @@ -2474,6 +2474,7 @@ chipsPreInitWingine(ScrnInfoPtr pScrn, int flags) return FALSE; hwp = VGAHWPTR(pScrn); +vgaHWSetStdFuncs(hwp); vgaHWGetIOBase(hwp); /* @@ -2940,6 +2941,7 @@ chipsPreInit655xx(ScrnInfoPtr pScrn, int flags) return FALSE; hwp = VGAHWPTR(pScrn); +vgaHWSetStdFuncs(hwp); vgaHWGetIOBase(hwp); /* -- 2.7.4 ___ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: https://lists.x.org/mailman/listinfo/xorg-devel
Re: How do I compile and package the X Server code?
On Tue, 2019-02-12 at 17:22 +0100, Kevin Brace wrote: > I am able to compile X Server, although I do not know at this point > how to install it to my preferred location (I will like to install it > to /opt for testing purposes). https://www.gnu.org/software/autoconf/manual/autoconf-2.63/html_node/Default-Prefix.html You will probably also want to override PKG_CONFIG_PATH in the environment when building drivers against that server. Refer to the pkgconfig documentation for details, but it's probably something like: $ export PKG_CONFIG_PATH=/opt/xorg/share/pkgconfig:/opt/xorg/lib64/pkgconfig:$PKG_CONFIG_PATH That said... in my experience, one of the pleasant features of using a distribution is that you can reinstall packages. If I ever really do want to test a new buld of Xorg (the only server where the install path really matters) I just clobber the existing one, and when I'm done, dnf reinstall xorg-x11-server-*. > How do I install it to my preferred location and run the compiled > version rather than the existing version? If you're invoking the X server by hand, just do: # /opt/xorg/bin/Xorg Convincing your desktop environment's display manager to invoke that one instead of the one in /usr/bin depends on the particular display manager. (Not wanting to remember how to do this is part of the reason I don't use prefixes...) - ajax ___ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: https://lists.x.org/mailman/listinfo/xorg-devel
How do I compile and package the X Server code?
Hi, Since I have done it several times, obviously I am able to archive up the code for OpenChrome and other DDXs, but I am not able to archive the X Server code. I tried archiving X Server using xorg/util/modular's release.sh script, but I am not able to complete the task. I am able to compile X Server, although I do not know at this point how to install it to my preferred location (I will like to install it to /opt for testing purposes). How do I install it to my preferred location and run the compiled version rather than the existing version? Please note that I use Xubuntu 16.04.5 for this. Regards, Kevin Brace Brace Computer Laboratory blog https://bracecomputerlab.com ___ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: https://lists.x.org/mailman/listinfo/xorg-devel
Re: [Mesa-dev] RFC - libglvnd and GLXVND vendor enumeration to facilitate GLX multi-vendor PRIME GPU offload
On 2019-02-11 5:18 p.m., Andy Ritger wrote:
> On Mon, Feb 11, 2019 at 12:09:26PM +0100, Michel Dänzer wrote:
>> On 2019-02-08 11:43 p.m., Kyle Brenneman wrote:
>>>
>>> Also, is Mesa the only client-side vendor library that works with the
>>> Xorg GLX module? I vaguely remember that there was at least one other
>>> driver that did, but I don't remember the details anymore.
>>
>> AFAIK, the amdgpu-pro OpenGL driver can work with the Xorg GLX module
>> (or its own forked version of it).
>
> Maybe the amdgpu-pro OpenGL driver uses a fork of the Xorg GLX module
> (or sets the "GlxVendorLibrary" X configuration option?), but it doesn't
> look to me like the in-tree Xorg GLX module could report anything other
> than "mesa" for GLX_VENDOR_NAMES_EXT, without custom user configuration.
>
> GLX_VENDOR_NAMES_EXT, which client-side glvnd uses to pick the
> libGLX_${vendor}.so to load, is implemented in the Xorg GLX module
> with this:
>
> xserver/glx/glxcmds.c:__glXDisp_QueryServerString():
>
> case GLX_VENDOR_NAMES_EXT:
> if (pGlxScreen->glvnd) {
> ptr = pGlxScreen->glvnd;
> break;
> }
>
> pGlxScreen->glvnd appears to be assigned here, defaulting to "mesa",
> though allowing an xorg.conf override via the "GlxVendorLibrary" option:
>
> xserver/glx/glxdri2.c:__glXDRIscreenProbe():
>
> xf86ProcessOptions(pScrn->scrnIndex, pScrn->options, options);
> glvnd = xf86GetOptValString(options, GLXOPT_VENDOR_LIBRARY);
> if (glvnd)
> screen->base.glvnd = xnfstrdup(glvnd);
> free(options);
>
> if (!screen->base.glvnd)
> screen->base.glvnd = strdup("mesa");
>
> And swrast unconditionally sets pGlxScreen->glvnd to "mesa":
>
> xserver/glx/glxdriswrast.c:__glXDRIscreenProbe():
>
> screen->base.glvnd = strdup("mesa");
>
> Is there more to this that I'm missing?
I don't think so, I suspect we were just assuming slightly different
definitions of "works". :)
--
Earthling Michel Dänzer | http://www.amd.com
Libre software enthusiast | Mesa and X developer
___
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: https://lists.x.org/mailman/listinfo/xorg-devel
Re: 2019 X.Org Board of Directors Elections Nomination period is NOW
So far we've received a couple of nominations for four open spots. The official nomination period ends this Thursday. Please let us know if you'd like to nominate someone including yourself. Harry On 2019-01-31 5:08 p.m., Wentland, Harry wrote: > We are seeking nominations for candidates for election to the X.Org > Foundation Board of Directors. All X.Org Foundation members are eligible for > election to the board. > > Nominations for the 2019 election are now open and will remain open until > 23:59 UTC on 14 February 2019. > > The Board consists of directors elected from the membership. Each year, an > election is held to bring the total number of directors to eight. The four > members receiving the highest vote totals will serve as directors for two > year terms. > > The directors who received two year terms starting in 2018 were Keith > Packard, Bryce Harrington, Eric Anholt, and Harry Wentland. They will > continue to serve until their term ends in 2020. Current directors whose term > expires in 2019 are Rob Clark, Martin Peres, Taylor Campbell and Daniel > Vetter. > > A director is expected to participate in the fortnightly IRC meeting to > discuss current business and to attend the annual meeting of the X.Org > Foundation, which will be held at a location determined in advance by the > Board of Directors. > > A member may nominate themselves or any other member they feel is qualified. > Nominations should be sent to the Election Committee at elections at x.org. > > Nominees shall be required to be current members of the X.Org Foundation, and > submit a personal statement of up to 200 words that will be provided to > prospective voters. The collected statements, along with the statement of > contribution to the X.Org Foundation in the member's account page on > http://members.x.org, will be made available to all voters to help them make > their voting decisions. > > Nominations, membership applications or renewals and completed personal > statements must be received no later than 23:59 UTC on 14 February 2019. > > The slate of candidates will be published 21 February 2019 and candidate Q > will begin then. The deadline for Xorg membership applications and renewals > is 21 February 2019. > > Cheers, Harry Wentland, on behalf of the X.Org BoD > > > > > ___ > memb...@foundation.x.org: X.Org Foundation Members > Archives: https://foundation.x.org/cgi-bin/mailman/private/members > Info: https://foundation.x.org/cgi-bin/mailman/listinfo/members > ___ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: https://lists.x.org/mailman/listinfo/xorg-devel
