The new gcc 3.4.2 in -current is more strict than previous versions with
C++ code. Some constructions formerly considered legal now cause compilation
Apply the attached patch.
It was created with the help of this entry in licq's bug tracking system:
Use a recent -current with the new gcc-3.4.2 compiler and try to build net/licq
On Fri, Jul 30, 2004 at 07:20:25PM +0000, FreeBSD-gnats-submit@FreeBSD.org wrote:
> Thank you very much for your problem report.
> It has the internal identification `ports/69823'.
> The individual assigned to look at your
> report is: freebsd-ports-bugs.
> >Category: ports
> >Responsible: freebsd-ports-bugs
> >Synopsis: [patch] unbreak net/licq with gcc-3.4
> >Arrival-Date: Fri Jul 30 19:20:24 GMT 2004
Forgot to attach the patch.
Over to maintainer
dropping the previous patches for socket.cpp is intended?
On Mon, Aug 02, 2004 at 03:08:06PM +0200, Dirk Meyer wrote:
> Synopsis: [patch] unbreak net/licq with gcc-3.4
> State-Changed-From-To: open->analyzed
> State-Changed-By: dinoex
> State-Changed-When: Mon Aug 2 15:06:41 CEST 2004
> dropping the previous patches for socket.cpp is intended?
It wasn't my intention.
I used the version of socket.cpp patched by the actual port as a base.
The file files/patch-socket.cpp contains two separate patches to
src/socket.cpp as you can see here :
It seems only the last one was applied.
Please try the new attached patch instead.