FORGET gcc 7.3
I have been hammering it today and got a few 'libbacktrace could not find executable to open' with 64-bit.
It is a gcc bug. It actually appeared in gcc 4.8.1 and got fixed in 4.8.2. It seems to be related to multi-core compilation. The worst thing is it doesn't seem possible to guess whether a compilation will be successful or not and, of course, they are the best bugs, aren't they? <laugh>
I have just had to buy 8.1 a box of chocalates otherwise it wan't going to work either. <smile>
Windows specific questions.
Who is online
Users browsing this forum: No registered users and 2 guests