Hi guys,
thanks for the quick replies.
>
> I believe either of these ought to be possible, I suspect the Cygwin or MinGW
> option is probably easier (but see Brian Davis' email of this morning, about
> Windows patches.)
>
Haven't checked that yet, but might be the next step..
> Using a cross-compiler on Linux, I would start with the script in the readme
> accompanying the "gcc4.7" patch, and fiddle with the configuration options,
> adding at least --target=something, and presumably
> COMPILER=your_cross_compiler
>
> Sorry I cannot offer more help than this.
No problem, I don't expect any, I keep telling people to read the
source, myself :-)
I've got a successful build from your patches (excellent job, BTW!),
then I gave the target=i586-mingw32msvc option a go. Turns out that
theory didn't work so far. Actually I had to comment this in
gcc/vhdl/Make-lang.in:
vhdl.all.cross:
# @echo "No support for building vhdl cross-compiler"
# exit 1
With some more library fiddling, I did eventually get a ghdl and ghdl1
executable, but it turns out on installation (when trying to compile the
standard libraries for the target), that ghdl wants to use the _native_
assembler, not the cross one. So now I don't know if I'm
just one step from the goal or on the completely wrong track. I believe
there must be a reason that the above rule was introduced, and that it
might be not all that easy..
Anyhow, I'll try some other approaches, the clue must lie somewhere in
the right configuration (I hope). Will keep you posted if I don't give up :)
Greetings,
- Martin
_______________________________________________
Ghdl-discuss mailing list
[email protected]
https://mail.gna.org/listinfo/ghdl-discuss
