ports/125249: New Port: security/ratproxy
Steven Kreuzer
skreuzer at exit2shell.com
Tue Jul 8 14:45:35 UTC 2008
pav at FreeBSD.org wrote:
> Synopsis: New Port: security/ratproxy
>
> State-Changed-From-To: open->feedback
> State-Changed-By: pav
> State-Changed-When: Tue Jul 8 09:24:50 UTC 2008
> State-Changed-Why:
> Does not compile on my 6.3/amd64 system:
>
> cc ratproxy.c -o ratproxy -Wall -O3 -Wno-pointer-sign -D_GNU_SOURCE http.c mime.c ssl.c -lcrypto -lssl
> cc1: error: unrecognized command line option "-Wno-pointer-sign"
> cc1: error: unrecognized command line option "-Wno-pointer-sign"
> cc1: error: unrecognized command line option "-Wno-pointer-sign"
> cc1: error: unrecognized command line option "-Wno-pointer-sign"
> *** Error code 1
>
> maybe that compiler flag is 4.x specific? Do we need it?
>
>
> Responsible-Changed-From-To: freebsd-ports-bugs->pav
> Responsible-Changed-By: pav
> Responsible-Changed-When: Tue Jul 8 09:24:50 UTC 2008
> Responsible-Changed-Why:
> Does not compile on my 6.3/amd64 system:
>
> cc ratproxy.c -o ratproxy -Wall -O3 -Wno-pointer-sign -D_GNU_SOURCE http.c mime.c ssl.c -lcrypto -lssl
> cc1: error: unrecognized command line option "-Wno-pointer-sign"
> cc1: error: unrecognized command line option "-Wno-pointer-sign"
> cc1: error: unrecognized command line option "-Wno-pointer-sign"
> cc1: error: unrecognized command line option "-Wno-pointer-sign"
> *** Error code 1
>
> maybe that compiler flag is 4.x specific? Do we need it?
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=125249
>
Good catch. Looks like no-pointer-sign is a gcc4 specific flag. Can you
give me a day or two to hack around it and I'll submit an update for the
port?
Also, I don't have access to a FreeBSD 6.2 or 6.3 box, so if someone can
help me test it out, I would be very grateful.
Thanks
More information about the freebsd-ports-bugs
mailing list