-------- Original Message --------
From: Bernd R <nospamname(a)web.de>
Sent: 30 August 2017 10:00:38 BST
To: Chris Young <chris.young(a)unsatisfactorysoftware.co.uk>
Subject: Re: Wy netsurf can render on amiga version from chris only if all is load. on
windows show page earlier and later load images or other parts
the paths can change with compiler or linker options in makefile. i did not know what
change your build have. My gcc port is too very simular to gcc build of other platforms
and in the page i give you link, is instruction how can build easy.see attached files. on
newer gcc the libs can not compile. there are no programs that need the new libs i know so
far. teh build stop with error, after the important thing(the compilers is compile). many
ports are done with the GCC 4.5 with full optimize, so it know as stable. but intresting
to see if GCC 7.2 give more speed
maybe this build can work with netsurf too. i try to compile 7.2 and let you know. see how
easy should possible to build a new version. work with 4.3.2 and 4.5. lets see if can work
with 7.2 too
On 29.08.17, you wrote:
On Tue, 29 Aug 2017 17:28:55 +0200, Bernd R wrote:
> seem the mailing list not work
> when it show earlier the page but flicker is better, because wait until all is load
is boring. so how is it done in windows version ?
> > A patch to upgrade the toolchain to GCC 4.5 would be greatly
> > appreciated.
> GCC 4.5 and 4.3.2 68k for cygwin host in windows you can download here
> on what system do you compile ?. I have done the 68k ports years
> ago, and now i have install a vmware ubuntu 7 X64. If this is
> usefull, i can try to compile gcc this for ubuntu 7.or can try to
> run cygwin under wine on linux
GCC needs to be integrated into the toolchain:
A "standalone" build of GCC is not helpful as the paths are different.
When I upgraded to 3.4 I managed to mostly copy across the patches
Most of the other ports I've seen for 68k (including a fork of that
one for gcc6) are an entire repository with the changes integrated.
Whilst that can theoretically be cloned and built within the
toolchain, it's a pain to have to change everything to accomodate it
only to have to switch everything around again when the next gcc port
comes along by somebody else with different ideas on how it should be
My preference would be to go as new as possible so it doesn't have to
be done again for a long time.
gcc6 is here: https://github.com/bebbo/gcc
Diese E-Mail wurde von AVG auf Viren geprÃ¼ft.