On Sat, 2014-01-04 at 13:24 +1300, David Koontz wrote:

> I'm not sure ghdl-0.3.1dev can be built agains gcc-4.7.3  
> There were boatloads of changes to support building against gcc-4.8.X.
> This would be one for Brian or Tristan.  The previous release (ghdl-0.29) 
> targeted gcc-4.3.4.

I see Adam managed to build with 4.8.2 but just in case anyone else goes
down this path...

IF YOU MUST USE GCC4.7 or IF YOU HAVE NO C++ COMPILER THEN:

If Adam winds back to revision 136, the last revision before the gcc4.8
changes, he ought to have a version buildable against gcc4.7.3.
I would recommend this over SVN r150 from gna.org as it includes the
OSVVM fixes. I kept the bugfixes in order while transferring to
ghdl-updates for that reason.

In the ghdl directory created by "hg clone", the command line
hg update 136
should accomplish this backtrack...

Then forget "make clean" and "make distclean" - only deleting the
builddir will be reliable after such a big change.

NB: he may want to either revert 134 or apply 144 if he is trying 32-bit
builds.

But really I don't know how the instructions could be clearer that newer
releases require gcc4.8 (4.8.1 has been successfully used, as well as
4.8.2) and gnu.org have made it abundantly clear that 4.8 requires C++.

> Going through the revision longs on ghdl-updates it looks like gcc-4.7.2 
> might work up through r136.   Brian might tell us that's no a particularly 
> desirable target. 

Oh I should read the whole thing before replying... 
r136 is OK (for 64 bit builds) else apply diffs between 143 and 144 on
top.

But gcc4.8 is preferred...

- Brian


_______________________________________________
Ghdl-discuss mailing list
[email protected]
https://mail.gna.org/listinfo/ghdl-discuss

Reply via email to