Hello,
On 18/11/14 10:08, [email protected] wrote: > Yes it works! I could build GHDL with gcc backend without problem. Great! > I tried it on a design I have. Here is what I did and the result:
$ rm -rf work $ ghdl -a --workdir=work --std=02 ../vhdl/*.vhd warning: directory 'work' set by --workdir= does not exist ghdl: installation problem: libexec/gcc/x86_64-unknown-linux-gnu/4.9.2/ghdl1 not found So I have one question, and one (probably minor) issue. The question: It seems that in version 0.32 ghdl create the work directory when needed, but it no longer does that?
I think nothing has changed here.
The minor issue: And the issue is that ghdl1 is explicitely searched in the directory libexec/gcc/... On my Archlinux system, ghdl1 is (properly) installed in /usr/lib/gcc/... I did a big recursive grep in search for "libexec". The path seems hardcoded in only 2 places: dist/gcc/Make-lang.in:99 dist/gcc/dist.sh:64 I can fix it with a little sed command in my script. Are these places the right ones to fix? Are there other places I should process? Or, do you think it is something that should be fixed in the ghdl build process? I would like to have ghdl1 searched in /usr/lib/gcc/... or in the local install dir according to --prefix. For now, I created the symlink /usr/libexec -> /usr/lib and ghdl works fine. It seems I could also use the parameter --GHDL1=...
This is the same issue that was also reported on gna.org. But now fixed. Thanks, Tristan. _______________________________________________ Ghdl-discuss mailing list [email protected] https://mail.gna.org/listinfo/ghdl-discuss
