On Thu, 2014-01-02 at 19:37 -0500, Adam Jensen wrote: > On 01/02/2014 06:08 AM, Brian Drummond wrote: > > > > Very old version. > > > > Check out the ghdl-updates repo at > > http://sourceforge.net/projects/ghdl-updates/
> I am now working with: > > ghdl-0.29 : http://ghdl.free.fr/ghdl-0.29.tar.bz2 > ghdl-0.31dev : SorceForge snapshot (2013-12-15) > ghdl-0.31dev : Today's Mercurial clone: Yesterday's Mercurial clone had a file missing in the runtime (grt-rtis.adb) now resolved: your build failed much earlier so you didn't get that far. > > Updated instructions describing building from source with gcc4.8 at > > http://sourceforge.net/p/ghdl-updates/wiki/build%20ghdl%20from%20source% > > 20on%20Linux/ > > There are a few hints in the documentation but it seems weak and > strained; there are unnecessary ambiguities, as if no one could spend an > hour and try to be concise. If you can point out specific failures such as ambiguities, then say so and we'll fix them if possible. It is more likely that instructions for building with gcc are not directly transferable to a different OS and compiler. > So far, my various attempts to build GHDL generally results in errors like: > > gmake[2]: *** No rule to make target `../gcc/gtype-vhdl.h', needed by > `ortho-lang.o'. Stop. This is easy to explain : I do not know the specific solution for your build process. Early in the process of building gcc, various scripts run that auto-generate several megabytes of source code - in the build directory! This source code includes custom generated garbage collection datatypes and routines : some of which (`../gcc/gtype-vhdl.h') is missing. It is also possible for this to get out of date w.r.t. compiler sources if you're working on them; hence the advice to delete the build dir and start again if similar build failures occur. A first place to start is to verify that you have installed and working versions of all the tools needed for this auto-generate process : documented at http://gcc.gnu.org/install/prerequisites.html If one of awk, perl etc are missing or incompatible, that would account for it... You'd like to think the gcc build process would be robust enough to identify and report such deficiencies : perhaps it can and something else is wrong; however I find it frighteningly fragile... > gcc -g -O2 -DIN_GCC -W -Wall -Wno-narrowing -Wwrite-strings ... > -S ../.././gcc -I gtyp-input.list -w tmp-gtype.state > ../.././gcc/vhdl/ortho-lang.c:1266: unexpected character `/' > ../.././gcc/vhdl/ortho-lang.c:1266: unexpected character `/' As David says, this one comes from C++ style comments, apparently rejected by your compiler. There is probably some flag to allow them, and you could add it to the CFLAGS or CPPFLAGS section of build_gcc.sh. However it would probably be better for me to eliminate these comments from ortho-lang.c today. > > A version of this Wiki page describing the build process with the > > dragonlace compiler would be a useful addition, so please keep us > > updated as to how you get on... > > > > Yes, definitely! Generously concise documentation written in such a way > as to actually be helpful is a nice addition to pretty much anything. Your help will be invaluable in preparing it. As a first step, which compiler version are you using to compile it, and which compiler source code are you building against? Thanks, - Brian _______________________________________________ Ghdl-discuss mailing list [email protected] https://mail.gna.org/listinfo/ghdl-discuss
