compiling d code without phobos ?

[Wiz]

As you said, I replaced the real phobos object.d with an other version 
by renaming mingw/include/d/ to mingw/include/d2/ and just put a 
object.d file containing :
/class Object
{

}
/
so I'm pretty sure gdc will not use the old version, but a gdc -c 
object.d -o object.o does the exactly same thing :
/object.d:0: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.mingw.org/bugs.shtml> for instructions./

Do I must submit a report to that url ? Not even a gdb can helps.


Wiz


John Reimer a écrit :
> I think you need to replace mingw/include/d/3.4.5/object.d with your 
> version.  So backup the one there, replace it with yours, and see what 
> happens.
>
> GDC has a "weird" directory structure for the intrinsic imports.  I'm 
> not sure if that's the fault of the D implementation or the phobos 
> library mechanics hard-wired into D :(. I actually wish the structure 
> were dirt simple for those dmd/gdc users who want to create there own 
> kernels. Right now, it seems to require a certain amount of hackery to 
> get around the setup.
>
> At the very least, we'll eventually need a tutorial for how to 
> roll-your-own phobos-replacement and attach it to d.  Ares is a good 
> example of a start, but I believe it is dmd only, at this point.
>
> -JJR
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.puremagic.com/pipermail/d.gnu/attachments/20061219/8c5e567e/attachment.htm