For what it's worth, there's been a lot of traffic on the R-devel list in the
past few
months about Windows builds. They are done under cygwin with a kit of tools
(Rtools) from
Duncan Murdoch at UWO who is a longstanding colleague of mine. Very nice work,
but also
very fiddly if you stray from t
On Wed, Oct 27, 2010 at 3:00 PM, Bart Trojanowski wrote:
> On Wed, Oct 27, 2010 at 2:26 PM, piper.guy1 wrote:
>>> Well, ethtool is a linux-specific tool to poke at network devices, so
>>> I actually would expect it to include linux/* headers directly. I
>>> wouldn't hold much hope of compiling
On Wed, Oct 27, 2010 at 2:26 PM, piper.guy1 wrote:
>> Well, ethtool is a linux-specific tool to poke at network devices, so
>> I actually would expect it to include linux/* headers directly. I
>> wouldn't hold much hope of compiling that on windows.
>
> I never said that I'm compiling under Wind
On Wed, Oct 27, 2010 at 1:37 PM, Aidan Van Dyk wrote:
> On Wed, Oct 27, 2010 at 1:20 PM, piper.guy1 wrote:
>
>> '/usr/include/linux' is pretty common. It's in my Ubuntu platform. It
>> includes a very comprehensive collection of header files and folders
>> of header files. So why does it appear
On Wed, Oct 27, 2010 at 1:20 PM, piper.guy1 wrote:
> '/usr/include/linux' is pretty common. It's in my Ubuntu platform. It
> includes a very comprehensive collection of header files and folders
> of header files. So why does it appear sometimes and not others?
/usr/include/linux should contain t
