Fwd: Xvfb MIA

[Jack Howarth]

---------- Forwarded message ----------
From: Jack Howarth <howarth.at.macports at gmail.com>
Date: Thu, Feb 12, 2015 at 7:33 PM
Subject: Re: Xvfb MIA
To: Jeremy Huddleston Sequoia <jeremyhu at macports.org>


Jeremy,
       Okay. it is working now. I did a quick and dirty test by
hacking the existing xorg-server Portfile  to append the additional
configure flags...

--disable-xquartz --disable-glx --disable-dri --disable-launchd
--enable-kdrive --disable-xsdl --enable-xnest --enable-xvfb

and 'sudo port -d build xorg-server' to generate a Xvfb binary.
        Copying the resulting Xvfb as well as the attached xvfb-run
script into /opt/local/bin followed by installing the MacPorts auth
and getops packages was sufficient to make xvfb-run operational. I was
also able to build the problematic rNMR 1.1.8 release by changing the
rNMR Portfile to use xvfb-run like we do on fink...

 build {
     file mkdir ${worksrcpath}/pkg
-    system -W ${worksrcpath} "${prefix}/bin/R CMD INSTALL -l pkg
--byte-compile --build ${distpath}/[lindex ${distfiles} 0]"
+    system -W ${worksrcpath} "`which xvfb-run` ${prefix}/bin/R CMD
INSTALL -l pkg --byte-compile --build ${distpath}/[lindex ${distfiles}
0]"
 }

I'll take a stab at creating a xvfb subport tomorrow but am rather
confused about how much of the xorg-server Portfile has to be
duplicated in the subport section.
             Jack

On Thu, Feb 12, 2015 at 7:08 PM, Jack Howarth
<howarth.at.macports at gmail.com> wrote:
> Jeremy,
>       That gets me further. If I append
>
>
> On Thu, Feb 12, 2015 at 5:23 PM, Jeremy Huddleston Sequoia
> <jeremyhu at macports.org> wrote:
>> Try this:
>> --disable-xquartz --disable-glx --disable-dri --disable-launchd --enable-kdrive --disable-xsdl --enable-xnest --enable-xvfb
>>
>>> On Feb 12, 2015, at 12:13, Jack Howarth <howarth.at.macports at gmail.com> wrote:
>>>
>>> Jeremy,
>>>     Exactly what needs to be passed to configure in the xorg-server
>>> Portfile to trigger Xvfb to build? I see...
>>>
>>>  --enable-xvfb           Build Xvfb server (default: yes)
>>>
>>> in the output of './configure --help' in the build directory but the
>>> config.log left behind only shows...
>>>
>>> configure:28382: checking whether to build Xvfb DDX
>>> configure:28384: result: no
>>>
>>>      Jack
>>>
>>> On Thu, Feb 12, 2015 at 1:13 PM, Jeremy Huddleston Sequoia
>>> <jeremyhu at macports.org> wrote:
>>>>
>>>>> On Feb 12, 2015, at 08:58, Jack Howarth <howarth.at.macports at gmail.com> wrote:
>>>>>
>>>>> Jeremy,
>>>>>   So I take it that it is impossible to use MacPort's Xvfb
>>>>
>>>> There is no port for Xvfb.  That's the only issue. If you want it, I suggest you make a subport of xorg-server to provide it.
>>>>
>>>>> without
>>>>> abandoning the use of the Xquartz server in /opt/local/X11?
>>>>
>>>> I'm not sure where you got that idea, but certainly that is not the case.
>>>>
>>>> Also, it's not in /opt/local/X11.
>>>>
>>>>> That is
>>>>> rather unfortunate as my experience in packaging over 500 cran modules
>>>>> for fink was that at least 26 needed to have R CMD INSTALL passed
>>>>> through xvfb-run as those trigger accesses to the X server.
>>>>>        Jack
>>>>>
>>>>> On Wed, Feb 11, 2015 at 10:49 PM, Jeremy Huddleston Sequoia
>>>>> <jeremyhu at macports.org> wrote:
>>>>>> Xvfb is part of xorg-server.  MacPorts only installs the XQuartz DDX from the xorg-server and xorg-server-devel ports.
>>>>>>
>>>>>>> On Feb 11, 2015, at 18:48, Jack Howarth <howarth.at.macports at gmail.com> wrote:
>>>>>>>
>>>>>>> Jeremy,
>>>>>>>     Where is the Xvfb binary hidden in MacPorts? It is part of
>>>>>>> Xquartz so I assume we must have it hidden in one of the xorg
>>>>>>> packages. I ask because I need to leverage Xvfb and the xvfb-run
>>>>>>> script borrowed from fink in order to update the rNMR package to 1.1.8
>>>>>>> (which attempts to access the X11 server during the R CMD INSTALL
>>>>>>> step). In fink, we saw the same issue but solved it by passing the R
>>>>>>> command in question to the modified Debian xvfb-run script. Assuming
>>>>>>> that MacPorts has Xvfb buried in some package, I can package up the
>>>>>>> xvfb-run script for general use.
>>>>>>>      Jack
>>>>>>> <xvfb-run>
>>>>>>
>>>>
>>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: xvfb-run
Type: application/octet-stream
Size: 5457 bytes
Desc: not available
URL: <https://lists.macosforge.org/pipermail/macports-dev/attachments/20150212/e03651b0/attachment-0001.obj>