[RkWard-devel] R cant find the rkward backend

[Colin Kiegel]

Good news.
(./configure && make && make install) worked perfectly.

I had to remove /usr/lib/R/library/00LOCK (probably created by the ebuild). 
Otherwise "make install" failed with:

ERROR: failed to lock directory '/usr/lib/R/library' for modifying
Try removing '/usr/lib/R/library/00LOCK'
make[3]: [install] Fehler 3 (ignoriert)

But after I removed this directory, everything worked (thank you very much).

My next step was to "make uninstall" it again. I then ran "ebuild 
rkward-0.3.6.ebuild compile" to compile the sourcecode via the ebuild. To 
check, whether the R-rkward backend was built, I switched into the work-dir 
of the ebuild and just called "make install". It worked again.

So I can now tell, that the module gets build by the ebuild, but not 
installed. But I wasn't able to fix it.

The gentoo way to install a package is

./configure (..)
make
make install DESTDIR=${D}

but this way, the backend doesn't get installed (neither to ${D}, nor anywhere 
else) - at least on my system.

It would be best if "make install DESTDIR=${D}" just worked the way it's 
supposed to.

Kind regards. :)

Colin

 
Thomas Friedrichsmeier wrote:
> Hi Colin,
>
> On Monday 19 June 2006 23:15, Colin Kiegel wrote:
> > https://sourceforge.net/forum/message.php?msg_id=3786435
> >
> > The following files got installed by the rkward ebuild:
>
> [...]
>
> in fact, the files relevant to this problem are missing from the list
> (those would probably go to /usr/lib/R/something), so something goes wrong
> during build or installation. Eventually we'll need to track down, what
> exactly goes wrong with the ebuild. Before that, to diagnose the problem,
> could you try building without the .ebuild?
>
> ./configure
> make
> make install
>
> (maybe also check the instructions in the INSTALL file, in case there are
> obvious errors during the configure stage). If this works, we'll know
> the .ebuild file itself is at fault, not some specifics of your system. If
> it does not work, or you encounter problems, please write back with more
> info.
>
> I'm sorry, I can't come up with a solution just yet, as I do not understand
> what exactly causes the problem, yet, but I'm fairly certain, we'll be able
> to track this down after a few more tries at most.
>
> Thanks for your patience
> Thomas