Hi,
d9492da540430103b9dcd6844eb59b508c061d66 effectively breaks builds with gcc 3.4.
Should we make a statement regarding minimum supported compiler versions?
Nils
___
varnish-dev mailing list
varnish-dev@varnish-cache.org
https://www.varnish-cache.o
>As said on IRC, here's a shot at porting varnishtop on the new logging
>API. I didn't change much, maybe not enough (RB tree freeing?), but it
>seems to work.
I'm wading through my inbox, did Martin look at this patch ?
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org
In message <52ceb8a6.1050...@schokola.de>, Nils Goroll writes:
>d9492da540430103b9dcd6844eb59b508c061d66 effectively breaks builds
>with gcc 3.4.
That was not the intention.
Can you find out which particular option it is ?
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.or
On 01/ 9/14 04:57 PM, Poul-Henning Kamp wrote:
Can you find out which particular option it is ?
I had already started work on a fix, so now that I know your intention I will
finish it.
Nils
___
varnish-dev mailing list
varnish-dev@varnish-cache.or
Not looked at it in detail yet, though first impression looks good. Will be
going in with some tweaks. Thanks for the reminder though :-)
Main
9. jan. 2014 17:23 skrev "Poul-Henning Kamp" følgende:
>
> >As said on IRC, here's a shot at porting varnishtop on the new logging
> >API. I didn't chang
Ah, I was wondering about it too. Martin, feel free to give me pointer
about what you want changed, I see a few spots that could be more
elegant or consistent, but you'll have probably more to say.
On 01/09/2014 05:41 PM, Martin Blix Grydeland wrote:
>
> Not looked at it in detail yet, though firs
d9492da540430103b9dcd6844eb59b508c061d66 effectively breaks builds with gcc 3.4.
... only when developer warnings are enabled.
Patch attached.
This also fixes linker issues if the compiler supports -fstack-protector but not
the linker and a "the address of ‘buf’ will never be NULL" on Solaris
