Hi, > Sometimes it is better to move the troubled kid out of the community. > Having a clean-room version of the gcc version compatible with ghdl in a > location where apt-get cannot touch it seems very much a way around the > current problem. Problem for me as a GHDL user is that building gcc in > /usr/local or /opt/local and then build GHDL on top of that needs a > teaspoon step-by-step instruction or a script. So far I am stopping any > update or install on my Debian which would remove GHDL. That also means > I am stuck at whatever GHDL version available in Debian/sid. I would > really like to use OSVVM, but my lack of gcc-fu prevents me from that. >
I'd also second the clean room approach. After a few failures with various compiler versions for the svn150, I finally got a DEB out of a purely sandboxed build procecure based on a slightly patched gcc 4.7.2. But like others mentioned, it's not just a 'make all' thing. To do it right, a few patches would have to be applied. So, maintaining the DEB side is only the 5% of the work, I'd say. (So I've skipped the remaining 95% of putting it into a 'make all' build framework). As far as I can tell, my ghdl DEB is clean enough to coexist with the native Ubuntu gcc (4.4.3) and libraries. Cheers, - Strubi _______________________________________________ Ghdl-discuss mailing list [email protected] https://mail.gna.org/listinfo/ghdl-discuss
