[Rcppoctave-user] Apple Blues

[Dominick Samperi]

The log that I sent here shows C++ compilers clang++
and c++ (same as clang++ under Mac OS X), but there
is no change if g++ is used instead.


On Sat, Nov 2, 2013 at 1:00 AM, Dominick Samperi <djsamperi at gmail.com>wrote:

> It appears that octave_end is not called at all under Mac OS X. But it
> is also not called under Linux! I inserted Rprintf statements to check.
>
> Perhaps the explanation is that failing to call octave_end under Linux
> (or Windows?) is non-fatal, but this is fatal under Mac OS X? If this
> is so the Mac OS X behavior is less dangerous...
>
> If I do not use --no-test-load, I get the result in RcppOctave.log
> (attached).
>
> Also, I'm attaching RcppOctave/src/modules/Makefile.in
> with a small edit (the sed script generates a path with an extra '..').
>
>
>
> On Sat, Nov 2, 2013 at 12:19 AM, Renaud Gaujoux <
> renaud at mancala.cbio.uct.ac.za> wrote:
>
>>
>> The --no-test-load option is used because the embedded Octave session
>>> is not terminated properly at test time (during installation), and the
>>> embedded Octave session needs to be explicitly terminated before
>>> leaving the R session using the 'octave_end' entry point.
>>>
>>
>> octave_end is normally called when the package is unloaded in
>> .onUnload as well as when the library is unloaded by in R_init_unload (or
>> something like that).
>> There is no errors on Linux at load test.
>> Can you please post the install logs showing the error?
>>
>> Thanks
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.r-forge.r-project.org/pipermail/rcppoctave-user/attachments/20131102/00ad976f/attachment.html>