R devel - Mar 2015 - Notes on building a gcc toolchain for Rtools (but not multilib)

On Mon, Mar 9, 2015 at 3:50 AM, Duncan Murdoch <murdoch.duncan at
gmail.com> wrote:
> On 08/03/2015 10:02 PM, Hsiu-Khuern Tang wrote:
>> Hi,
>>
>> [This is a follow-up to the "New version of Rtools for
Windows" thread
>> in January, but I just subscribed and don't know how to reply to an
>> old thread -- my apologies.]
>
> I am planning to put a new Rtools online today that uses a different
> build of gcc 4.9.2.  I will be concentrating on getting it to work with
> all the external libraries before the 3.2.0 release next month.  I'm
not
> planning to try to get it to work with R-patched, and I expect it
won't:
>  I needed to make a number of patches to R-devel for compatibility.
I also worked off R-devel (I said wrongly that it was R-patched in my
original post) and benefited from your compatibility changes.

I look forward to the new Rtools and will test it by compiling some packages.

- Hsiu-Khuern

On Mon, Mar 9, 2015 at 11:07 AM, Hsiu-Khuern Tang <tangoh at gmail.com>
wrote:
> I also worked off R-devel (I said wrongly that it was R-patched in my
> original post) and benefited from your compatibility changes.
Hsiu-Khuern, using your suggest filter in NM, I was able to build Rcpp
in the R_devel compiled with Gcc 4.9.2/win32/seh last night, and I saw
around a 10%-15% speedup in Rcpp performance (and R performance in
general) from the 3.1.2 version I compiled with Rtool 4.6.3. That may
be related to inherent optimizations in 4.9.2 vs 4.6.3, it may be
related to seh vs sjlj, or it may be related to passing gnu++11
instead of gnu++0x, I don't know. I do know it was the same code on
the same machine, for what it is worth.

Thank you,

Avi

On 09/03/2015 11:07 AM, Hsiu-Khuern Tang wrote:
> On Mon, Mar 9, 2015 at 3:50 AM, Duncan Murdoch <murdoch.duncan at
gmail.com> wrote:
> > On 08/03/2015 10:02 PM, Hsiu-Khuern Tang wrote:
> >> Hi,
> >>
> >> [This is a follow-up to the "New version of Rtools for
Windows" thread
> >> in January, but I just subscribed and don't know how to reply
to an
> >> old thread -- my apologies.]
> >
> > I am planning to put a new Rtools online today that uses a different
> > build of gcc 4.9.2.  I will be concentrating on getting it to work
with
> > all the external libraries before the 3.2.0 release next month. 
I'm not
> > planning to try to get it to work with R-patched, and I expect it
won't:
> >  I needed to make a number of patches to R-devel for compatibility.
>
> I also worked off R-devel (I said wrongly that it was R-patched in my
> original post) and benefited from your compatibility changes.
>
> I look forward to the new Rtools and will test it by compiling some
packages.
It's now on the main site at CRAN, and should propagate to the mirrors 
reasonably quickly.  I'm hoping that tomorrow's R-devel build will use 
it, but there may be some last minute problems.

Duncan Murdoch

On 09/03/2015 1:40 PM, Duncan Murdoch wrote:
> On 09/03/2015 11:07 AM, Hsiu-Khuern Tang wrote:
> > On Mon, Mar 9, 2015 at 3:50 AM, Duncan Murdoch <murdoch.duncan at
gmail.com> wrote:
> > > On 08/03/2015 10:02 PM, Hsiu-Khuern Tang wrote:
> > >> Hi,
> > >>
> > >> [This is a follow-up to the "New version of Rtools for
Windows" thread
> > >> in January, but I just subscribed and don't know how to
reply to an
> > >> old thread -- my apologies.]
> > >
> > > I am planning to put a new Rtools online today that uses a
different
> > > build of gcc 4.9.2.  I will be concentrating on getting it to
work with
> > > all the external libraries before the 3.2.0 release next month. 
I'm not
> > > planning to try to get it to work with R-patched, and I expect it
won't:
> > >  I needed to make a number of patches to R-devel for
compatibility.
> >
> > I also worked off R-devel (I said wrongly that it was R-patched in my
> > original post) and benefited from your compatibility changes.
> >
> > I look forward to the new Rtools and will test it by compiling some
packages.
>
> It's now on the main site at CRAN, and should propagate to the mirrors
> reasonably quickly.  I'm hoping that tomorrow's R-devel build will
use
> it, but there may be some last minute problems.
I think R-devel will have some trouble finding the compilers if they 
aren't in the default install locations in c:\Rtools.  This should be 
fixed in a few days, probably by requiring an environment variable to 
specify where Rtools is installed.

In the meantime, if you get "gcc not found" errors, you can manually 
edit the etc/*/Makeconf file in the R-devel binary install, and set 
BINPREF to  <Rtools>/gcc492_32/bin/ for *=i386, and set BINPREF64 to 
<Rtools>/gcc492_64/bin/ for *=x64.

Duncan Murdoch

Hi Duncan,

On Mon, Mar 9, 2015 at 10:40 AM, Duncan Murdoch
<murdoch.duncan at gmail.com> wrote:
> On 09/03/2015 11:07 AM, Hsiu-Khuern Tang wrote:
>>
>> On Mon, Mar 9, 2015 at 3:50 AM, Duncan Murdoch <murdoch.duncan at
gmail.com>
>> wrote:
>> > On 08/03/2015 10:02 PM, Hsiu-Khuern Tang wrote:
>> >> Hi,
>> >>
>> >> [This is a follow-up to the "New version of Rtools for
Windows" thread
>> >> in January, but I just subscribed and don't know how to
reply to an
>> >> old thread -- my apologies.]
>> >
>> > I am planning to put a new Rtools online today that uses a
different
>> > build of gcc 4.9.2.  I will be concentrating on getting it to work
with
>> > all the external libraries before the 3.2.0 release next month. 
I'm not
>> > planning to try to get it to work with R-patched, and I expect it
won't:
>> >  I needed to make a number of patches to R-devel for
compatibility.
>>
>> I also worked off R-devel (I said wrongly that it was R-patched in my
>> original post) and benefited from your compatibility changes.
>>
>> I look forward to the new Rtools and will test it by compiling some
>> packages.
>
>
> It's now on the main site at CRAN, and should propagate to the mirrors
> reasonably quickly.  I'm hoping that tomorrow's R-devel build will
use it,
> but there may be some last minute problems.
Is the new Rtools at
http://cran.r-project.org/bin/windows/Rtools/Rtools33.exe?  I'm still
getting "Error 404 object not found".

Thanks,
- Hsiu-Khuern

----- Original Message -----
> From: "Duncan Murdoch" <murdoch.duncan at gmail.com>
> To: "Hsiu-Khuern Tang" <tangoh at gmail.com>, r-devel at
r-project.org
> Sent: Monday, March 9, 2015 10:40:02 AM
> Subject: Re: [Rd] Notes on building a gcc toolchain for Rtools (but not
multilib)
> 
> On 09/03/2015 11:07 AM, Hsiu-Khuern Tang wrote:
> > On Mon, Mar 9, 2015 at 3:50 AM, Duncan Murdoch
> > <murdoch.duncan at gmail.com> wrote:
> > > On 08/03/2015 10:02 PM, Hsiu-Khuern Tang wrote:
> > >> Hi,
> > >>
> > >> [This is a follow-up to the "New version of Rtools for
Windows"
> > >> thread
> > >> in January, but I just subscribed and don't know how to
reply to
> > >> an
> > >> old thread -- my apologies.]
> > >
> > > I am planning to put a new Rtools online today that uses a
> > > different
> > > build of gcc 4.9.2.  I will be concentrating on getting it to
> > > work with
> > > all the external libraries before the 3.2.0 release next month.
> > >  I'm not
> > > planning to try to get it to work with R-patched, and I expect it
> > > won't:
> > >  I needed to make a number of patches to R-devel for
> > >  compatibility.
> >
> > I also worked off R-devel (I said wrongly that it was R-patched in
> > my
> > original post) and benefited from your compatibility changes.
> >
> > I look forward to the new Rtools and will test it by compiling some
> > packages.
> 
> It's now on the main site at CRAN, and should propagate to the
> mirrors
> reasonably quickly.  I'm hoping that tomorrow's R-devel build will
> use
> it, but there may be some last minute problems.
> 
Thanks to you and everyone who worked on this. Is there a way to tell which
toolchain built a given R-devel binary?
If not, can you let us know when there is one on CRAN that was built with the
new Rtools?

Thanks,
Dan

> Duncan Murdoch
> 
> ______________________________________________
> R-devel at r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel
>