Tobias Verbeke wrote:
> Hi Ben,
>
>> Tobias Verbeke businessdecision.com> writes:
>>
>>> The resulting package now allows for using an embedded OpenBUGS
>>> on GNU/Linux without relying on WINE. Thanks to all for their helpful
>>> comments.
>>
>> woo-hoo! this is great! Any chance that thi
Hi Ben,
> Tobias Verbeke businessdecision.com> writes:
>
>> The resulting package now allows for using an embedded OpenBUGS
>> on GNU/Linux without relying on WINE. Thanks to all for their helpful
>> comments.
>
> woo-hoo! this is great! Any chance that this will propagate
> to the R2WinBU
Tobias Verbeke businessdecision.com> writes:
> The resulting package now allows for using an embedded OpenBUGS
> on GNU/Linux without relying on WINE. Thanks to all for their helpful
> comments.
woo-hoo! this is great! Any chance that this will propagate
to the R2WinBUGS package at some poi
Hin-Tak Leung wrote:
> Tobias Verbeke wrote:
>
>> Actually, I think Hin-Tak is right about the absolute path. Even when
>> the R code will call the executable that resides in that directory, R
>> will call it from any directory and that (current) directory will be
>> resolved (at least that is
Tobias Verbeke wrote:
> Actually, I think Hin-Tak is right about the absolute path. Even when
> the R code will call the executable that resides in that directory, R
> will call it from any directory and that (current) directory will be
> resolved (at least that is what I observe experimentally
Thank you very much for your input.
In the meantime I was -- thanks to
the pointer to the Rserve Makefile
by Professor Ripley -- able to have
a Makefile that built the package
correctly:
SFILE = ../inst/OpenBUGS/linbugs.c
XFILE = ../inst/OpenBUGS/linbugs
SOFILE = ../src/linbugs.so
all: $(XFILE)
Hin-Tak Leung wrote:
> Prof Brian Ripley wrote:
>> OpenBUGS is distributed under GPL2, so this seems not to apply.
>> It is distributed as source and as binaries: the difficulty is that it
>> is written in Object Pascal for which a compiler is not readily available.
>
> Argh, I just thought of
Prof Brian Ripley wrote:
> OpenBUGS is distributed under GPL2, so this seems not to apply.
> It is distributed as source and as binaries: the difficulty is that it
> is written in Object Pascal for which a compiler is not readily available.
Argh, I just thought of a proper technical reason, and I
OpenBUGS is distributed under GPL2, so this seems not to apply.
It is distributed as source and as binaries: the difficulty is that it is
written in Object Pascal for which a compiler is not readily available.
On Tue, 7 Aug 2007, Hin-Tak Leung wrote:
> Prof Brian Ripley wrote:
>> On Mon, 6 Aug 2
Andrew Clausen wrote:
> Hi Hin-Tak,
>
> On Tue, Aug 07, 2007 at 01:10:36AM +0100, Hin-Tak Leung wrote:
>> GPL-licensed code dlopen()'ing proprietary-licensed binary-only DLL/so
>> is allowed
>
> Do you have any evidence? (eg: something written on www.fsf.org?)
>
> As far as I know, the normal g
Hi Hin-Tak,
On Tue, Aug 07, 2007 at 01:10:36AM +0100, Hin-Tak Leung wrote:
> GPL-licensed code dlopen()'ing proprietary-licensed binary-only DLL/so
> is allowed
Do you have any evidence? (eg: something written on www.fsf.org?)
As far as I know, the normal grounds for allowing GPL code to link w
Prof Brian Ripley wrote:
> On Mon, 6 Aug 2007, Tobias Verbeke wrote:
>>> I presume.
>> Actually, these files appear to differ. The file I referred to
>> was the file ./Manuals/CBugs.html contained in the current OpenBUGS
>> release:
>>
>> http://mathstat.helsinki.fi/openbugs/OpenBUGS.zip
>
> I am
12 matches
Mail list logo
