On Thu, 2012-10-18 at 10:26 +0200, Lluís Batlle i Rossell wrote: > On Wed, Oct 17, 2012 at 07:55:20PM +0100, Brian Drummond wrote: > > GHDL 0.30, Dunoon Edition! > > > > > > To be built as per attached instructions, using attached patch. > > > > It's my first (and quite possibly last :-) biggish GCC project, and I > > really didn't expect it to take 3 weeks.
> > I've just tried to put your patch into our gcc 4.7.2 build system, and I get: > make[3]: *** No rule to make target `../gcc/gtype-vhdl.h', needed by > `ortho-lang.o'. Stop. > > Any quick idea? Without knowing "your gcc build system" I can't be sure. Whose build system? What I do know is: Following the script (building gcc according to prev email) the "configure" operation runs all sorts of scripts on all the gcc (and sub-language) source files and auto-generates a bunch of additional source files for YOUR specific system (e.g word width, endian-ness, selected languages). These files are for the GCC garbage collector (and probably other purposes too, but here we are concerned with the gc) and they are - insanely, to me - in the BUILD directory! Probably to avoid confusion with the original sources... But why not in $SOURCEDIR/generated or $BUILDDIR/gen_source ??? I think the gcc build process is insane and frequently broken, and that's probably why you use your own build system... Anyway, your missing file is one of these. If you look in your $BUILDDIR/gcc you will see gtype-java.h and many others, but not gtype-vhdl.h. This is telling me that your build system has skipped past the "Configure" step (presumably it was done once, the first time you built gcc4.7.2) So now I think we know what is missing - likely more files, this is the first - and why - the remaining question is how to solve it. Does your build process have any option to let you re-run Configure? I could send you my copy, but (a) I don't know how many other files you need and (b) it is probably incompatible with yours anyway. My suggestion would be to build from my instructions on the same machine but outside your build tree - but to stop after the "configure" stage. Then look to see if the gcc folder contains the .h files. (I do not honestly know if "configure" generates them, or if it just creates a Makefile that will later. So, run the "Make" stage if necessary ) Then use this build directory as a source for gtype-vhdl.h and any other missing files... Thanks for the feedback, and I hope this helps, - Brian _______________________________________________ Ghdl-discuss mailing list [email protected] https://mail.gna.org/listinfo/ghdl-discuss
