On 3 Jan 2014, at 1:37 pm, Adam Jensen <[email protected]> wrote: > 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. > > or: > > gcc -g -O2 -DIN_GCC -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual > -Wstrict-prototypes -Wmissin > g-prototypes -Wmissing-format-attribute -pedantic -Wno-long-long > -Wno-variadic-macros -Wno-overlength-st > rings -Wold-style-definition -Wc++-compat -DHAVE_CONFIG_H -DGENERATOR_FILE > -o build/gengtype \ > build/gengtype.o build/errors.o build/gengtype-lex.o > build/gengtype-parse.o build/gengtype-state.o b > uild/version.o ../../build-i386-unknown-freebsd9.2/libiberty/libiberty.a > /bin/sh ../.././gcc/../move-if-change tmp-gi.list gtyp-input.list > echo timestamp > s-gtyp-input > build/gengtype \ > -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 `/' > ../.././gcc/vhdl/ortho-lang.c:1267: unidentified type `vec' > ../.././gcc/vhdl/ortho-lang.c:1267: parse error: expected '(', 'GTY', or an > identifier, have '<' > ../.././gcc/vhdl/ortho-lang.c:1297: unexpected character `/' > ../.././gcc/vhdl/ortho-lang.c:1297: unexpected character `/' > ../.././gcc/vhdl/ortho-lang.c:1298: unidentified type `vec' > ../.././gcc/vhdl/ortho-lang.c:1298: parse error: expected '(', 'GTY', or an > identifier, have '<' > ../.././gcc/vhdl/ortho-lang.c:1883: unexpected character `/' > ../.././gcc/vhdl/ortho-lang.c:1883: unexpected character `/' > ../.././gcc/vhdl/ortho-lang.c:1884: unidentified type `vec' > ../.././gcc/vhdl/ortho-lang.c:1884: parse error: expected '(', 'GTY', or an > identifier, have '<' > gmake[2]: *** [s-gtype] Error 1 > > A quick web search indicates that this is a common problem but I haven't > found a solution or an explanation of what leads to this common class of > compilation error. > >> 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.
"So far, my various attempts to build GHDL generally results in errors like:" Concise error reporting might help, too. The above in ortho-lang.c looks like a compiler compatibility issue although I'd have thought they should have been one line earlier. Line 1265 for instance has a c++ type comment with two slashes.
<<inline: Screen Shot 2014-01-03 at 4.13.17 pm.JPG>>
<<inline: Screen Shot 2014-01-03 at 4.17.57 pm.JPG>>
<<inline: Screen Shot 2014-01-03 at 4.19.13 pm.JPG>>
It looks like your compiler is not compatible through configuration or otherwise with those comment types (A C99 feature). Note these line numbers don't match the latest version, Tristan is being prolific. I'd suggest sticking to the ghdl-0.31 archive image which should be built against gcc-4.8.X (where X is currently 2). The missing gtype-vhdl.h might be a "dist.sh sources" failure or perhaps using the wrong dist.sh script. It should be in the top level of the vhdl directory to be installed under gcc-4.X.X/gcc . It might also be the result of trying to build outside the parameters described in Brian's script/method. The identical methodology is used to build under OS X 10.9.
_______________________________________________ Ghdl-discuss mailing list [email protected] https://mail.gna.org/listinfo/ghdl-discuss
