> iain@dm1-oneiric:~/src/gdc/src$ hg status
> ? d/dmd2/cppmangle.c
> ? d/phobos2/std/internal/processinit.d
> ? d/phobos2/std/internal/windows/advapi32.d
>
>
> I shall never learn my lesson of checking and adding new files before upload. :)

Also had to re-setup gdc.
btw, is there a way to do that other than removing gcc-4.6 entirely and doing all the setup-gcc.sh stuff again?

Am 08.12.2011, 20:04 Uhr, schrieb Iain Buclaw <ibuclaw@ubuntu.com>:
> Will also want to get things moving fast on 64bit support passing
> testsuite in same manner as 32bit currently does.  Now I have a new
> capable machine, is all test test test to get that sorted out.

Need help with testing?

God I never even noticed that damn testsuite is silently running in 32bit mode as well, argh.

On 8 December 2011 19:39, Trass3r <un@known.com> wrote:
>> iain@dm1-oneiric:~/src/gdc/src$ hg status
>> ? d/dmd2/cppmangle.c
>> ? d/phobos2/std/internal/processinit.d
>> ? d/phobos2/std/internal/windows/advapi32.d
>>
>>
>> I shall never learn my lesson of checking and adding new files before upload. :)
>
>
> Also had to re-setup gdc.
> btw, is there a way to do that other than removing gcc-4.6 entirely and
> doing all the setup-gcc.sh stuff again?


'setup-gcc.sh --update'  should be enough to rebuild the symlinks for new files in druntime.  Other than that, it depends on what has changed, but it is at least safe to at least remove the entire d build directory.


-- 
Iain Buclaw

*(p < e ? p++ : p) = (c & 0x0f) + '0';