I have attempted to get the m68k-unknown-amigaos toolchain up so i can
get the CI system building for the target. I managed to get the
main toolchain building once I fixed the already known issues with gmp
and autoconf versioning (applied the same fixes we already had for the
I have unfortunately failed to make the SDK build. libcurl is failing
because of a missing include. This can be seen in the CI systems build
log  If someone knows the answer to this please can they apply it
to the toolchains repo and let me know. Once this is working I will
sort out adding this target to the libs and netsurf.
The recent developer weekend gave John-Mark and myself opportunity to
improve the core buildsystem (used for all the libraries) to use
standard "triplet" type identifiers for the ABI being compiled. This
means we now query the compiler  about the binary it will build to
setup cross compiling.
We use the environment values for HOST, HOST_CC, BUILD and CC in a
similar manner to how the gnu tooling uses them. Simply:
BUILD - The compiler triplet of the system running the compiler, this
can almost always be omitted and will be detected automatically.
CC - The build systems compiler, allows overriding of the default
compiler (cc) searched for on the PATH
HOST - This is the compiler triplet of the system we are building for,
it it differs from BUILD then we are performing a cross compile.
The compiler name is constructed using this unless HOST_CC is
HOST_CC - override the constructed compiler name for cross
compilation, the path and details for all the tools are
derived from this.
The core buildsystem has been updated along with the environment
script  so in general this has a low impact on developers but a
great gain for more complex build setups such as the CI system.
 This uses "cc -dumpmachine"
I have recently had the opportunity to greatly improve the NetSurf CI
build infrastructure both in terms of hardware and software.
On the hardware side I would like to thank Mythic Beasts  for once
again generously donating a 1u rack server. This is a 8 core Xeon with
24G of memory which replaces their previous donation of a 4 core 8G
This server is the projects primary VM host for CI build slaves and
the bug tracker. It continues to be hosted by Collabora  in
Cambridge. Other services the project uses, like the website,
remain hosted by Pepperfish  for which I would also like to extend
The new hardware has reduced the NetSurf CI rebuild time under
150seconds (down from 300) on all ten currently built operating
systems and allowed the addition of more build combinations improving
the utility to the developers.
The additional memory has allowed us to add more build slaves and
hence extend the number of OS built for. Also the number of checks
performed in analysis jobs was extended.
The CI software has been upgraded to the latest version of jenkins
along with all the other plugins.
I used the opportunity to complete the improvements to the development
build process which was started at the developer weekend. This has
resulted in the job history and rss feed data for many CI jobs
(including the main NetSurf job) being reset, apologies if this
adversely affects anyone but as new builds are performed the history
backlog will build up again.
As a note builds are only performed if commits to the git
repository occur, we do not perform periodic (daily) builds in
general. As there have not been many commits recently there have been
very few builds, this is correct and expected behaviour.
A very good day to all of you.
We have read about Netsurf very recently.
Seems very interesting for us as we are looking into porting a rendering
engine with HTML4 support to QNX 4.25 platform.
Here are our first level queries after our basic analysis:
1. First of all, a direct question. Is Netsurf supported in QNX 4.25?
2. We understood that NetSurf has different front ends like SDL,
framebuffer, GTK etc. But haven't seen support for Photon GUI toolkit
supported in QNX. We are quite confused on the framebuffer/SDL support in
We assume this toolkit may be used only by the browser part to get the user
interface part. If so, can it be possible for us to only to port the
rendering engine part to QNX 4.25 and use the Photon APIs in QNX for the
front end part?
3. If query #2 is not a possible option, could you share your thoughts on
porting Netsurf to such an OS like us where any of these front ends are not
Looking forward to hear from you soon.
Thanking you in advance,
I’ve compiled Netsurf 3.2 for arm-none-linux-gnueabi for a mini6410 from FriendlyARM.
when it starts, I get a white screen and get the message BadEncoding.
It also won’t load a simple html page with only text from another server. But it can upload a picture from it.
I think it has some thing to do with the character encoding but I don’t know how to fix it.
Hardware: FriendlyARM mini 6410
Rootfs: busybox 1.17.2
I use the following libraries:
and from the netsurf-all-3.2
for compiling I’ve followed the BUILDING-Framebuffer
is it possible to run netsurf 3.2 fullscreen without the bars etc (kiosk mode)? . I’ve compiled it for frame buffer on a mini6410 from FriendlyARM but can’t figure out how to get it full screen. I want to use it as GUI.
is there a command that I need to use?
glibc-2.20 includes some changes to the include/features.h file
introduced by this commit:
Those changes make libsvgtiny fail because some warnings are thrown and
the build system is using the -Werror option. The errors are this one:
In file included from
error: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use
and this one:
In file included from src/colors.gperf:18:0:
error: "strndup" redefined [-Werror]
Any chance to fix the code upstream?
Vicente Olivert Riera
Graduate Software Engineer, MIPS Platforms
Imagination Technologies Limited
t: +44 (0)113 2429814
I am new to this organization and even to the open source. I have a
good knowledge on C, HTML5, CSS3. I want to contribute to this
organization. Kindly guide me on how to start and where to start.
On Sat, 29 Nov 2014 23:57:22 +0000, Commit Mailer wibbled on for an age:
> correctly calculate writeout bandwidth and properly impose limits
Is this really right?
(22.696681) content/llcache.c llcache_persist 2414: Wrote 884 bytes in 225ms bw:3928 http://aminet.net/pics/at.gif
(22.696759) content/llcache.c llcache_persist 2420: Overran timeslot
(22.696828) content/llcache.c llcache_persist 2426: Cannot write minimum bandwidth
(22.697699) amiga/misc.c ami_misc_req 51: Disc cache write bandwidth is too slow to be useful, disabling cache
(22.497406) content/llcache.c llcache_persist 2414: Wrote 1480 bytes in 114ms bw:12982 http://news.bbcimg.co.uk/view/1_4_38/cream/hi/news/img/services.gif
(22.497485) content/llcache.c llcache_persist 2420: Overran timeslot
(22.497549) content/llcache.c llcache_persist 2426: Cannot write minimum bandwidth
(22.497751) amiga/misc.c ami_misc_req 51: Disc cache write bandwidth is too slow to be useful, disabling cache
(16.366240) content/llcache.c llcache_persist 2414: Wrote 3931 bytes in 263ms bw:14946 http://i2.cdnds.net/13/47/hearst.png
(16.366319) content/llcache.c llcache_persist 2420: Overran timeslot
(16.366384) content/llcache.c llcache_persist 2426: Cannot write minimum bandwidth
(16.366585) amiga/misc.c ami_misc_req 51: Disc cache write bandwidth is too slow to be useful, disabling cache
Even if I spawn it off to another process (so store returns
immediately) I still get the not enough bandwidth message.