Re: setup-gcc.sh

2013-06-07 Thread eles
On Friday, 7 June 2013 at 16:07:46 UTC, Iain Buclaw wrote: On 7 June 2013 16:28, eles wrote: On Friday, 7 June 2013 at 14:07:27 UTC, Iain Buclaw wrote: On 7 June 2013 13:26, eles wrote: So you must remove these by hand. If it doesn't give that error to you, let me know. =) Shouldn't b

Re: setup-gcc.sh

2013-06-07 Thread Iain Buclaw
On 7 June 2013 16:28, eles wrote: > On Friday, 7 June 2013 at 14:07:27 UTC, Iain Buclaw wrote: >> >> On 7 June 2013 13:26, eles wrote: >> >> The gcc/d folder is symlinked to the gdc sources, so any updates in >> gdc will reflect in the gcc/d tree. > > > I think there is a confusion. The code that

Re: setup-gcc.sh

2013-06-07 Thread eles
On Friday, 7 June 2013 at 14:07:27 UTC, Iain Buclaw wrote: On 7 June 2013 13:26, eles wrote: The gcc/d folder is symlinked to the gdc sources, so any updates in gdc will reflect in the gcc/d tree. I think there is a confusion. The code that I quoted used to workk with gcc-4.8 (4.8.0) sourc

Re: setup-gcc.sh

2013-06-07 Thread Iain Buclaw
On 7 June 2013 13:26, eles wrote: > Hello, > > What is the purpose of this code in setup-gcc.sh? > > # 1. Remove d sources from d_gccsrc if already exist > test -h "$d_gccsrc/gcc/d" && rm "$d_gccsrc/gcc/d" > test -d "$d_gccsrc/libphobos" && rm -r "$d_gccsrc/libphobos" > if test -e "$d_gccsrc/gcc/

Re: setup-gcc.sh

2013-06-07 Thread Joseph Rushton Wakeling
On 06/07/2013 04:05 PM, Iain Buclaw wrote: > You should run setup-gcc.sh with --update. That skips applying the > patches (again) Cool, thanks. :-)

Re: setup-gcc.sh

2013-06-07 Thread Iain Buclaw
On 7 June 2013 13:55, Joseph Rushton Wakeling wrote: > Slightly different question about setup-gcc.sh. > > If you run it on the gcc-4.8.1 sources, having run it previously, you get the > following error message: > > Reversed (or previously applied) patch detected! Assume -R? [n] > > ... w

Re: setup-gcc.sh

2013-06-07 Thread Joseph Rushton Wakeling
Slightly different question about setup-gcc.sh. If you run it on the gcc-4.8.1 sources, having run it previously, you get the following error message: Reversed (or previously applied) patch detected! Assume -R? [n] ... what's the correct response here? :-)