Re: Debugging ports

2017-10-18 Thread Piotr Kubaj via freebsd-ports
Well, 11-STABLE now has LLVM 5.0 too, so it should work as well as in head. I actually tried it on the recent 11-STABLE. On 17-10-18 10:03:49, Guido Falsi wrote: On 10/18/2017 09:59, Piotr Kubaj wrote: According to https://wiki.freebsd.org/lldb, it should work just fine on amd64, apart from

Re: Debugging ports

2017-10-18 Thread Piotr Kubaj via freebsd-ports
According to https://wiki.freebsd.org/lldb, it should work just fine on amd64, apart from kernel debugger. I suppose there should be some improvements for other archs too, since that page was updated 1.5 years ago :) On 17-10-18 09:54:05, Guido Falsi wrote: On 10/18/2017 09:52, Piotr Kubaj

Re: Debugging ports

2017-10-18 Thread Piotr Kubaj via freebsd-ports
Shouldn't lldb be the replacement for gdb in base? On 17-10-18 09:47:25, Guido Falsi wrote: On 10/18/2017 06:33, Jan Beich wrote: Kubilay Kocak writes: On 10/18/17 8:29 AM, Jan Beich wrote: Guido Falsi writes: On 10/17/2017 23:11, Guido Falsi wrote: Thing is, recompiling with WITH_DE

Re: Debugging ports

2017-10-17 Thread Piotr Kubaj via freebsd-ports
I think I got it. It turns out that it's our gdb in base that can't read the debug info. lldb and gdb from ports do it just fine. I also thought about recompiling library dependecies, but something didn't fit in, because not only the libraries calls were not there, but the calls from the port

Debugging ports

2017-10-17 Thread Piotr Kubaj via freebsd-ports
Hi all, I am preparing a new port. However, I hit an assertion fail when starting the binary. The developer is willing to help me, provided that I send him backtrace and values from the structure that hits assertion failure. Thing is, recompiling with WITH_DEBUG doesn't help (I only get memory

Re: FreeBSD Port: MailScanner-5.0.3

2017-07-29 Thread Piotr Kubaj via freebsd-ports
After your commit, I now get an error during staging: (00:00:54) === (00:00:54) === (00:00:54) ===> Staging for MailScanner-5.0.3_1 (00:00:54) ** Missing /usr/ports/mail/mailsca

Re: www/lighttpd 1.4.45 broken mod_fastcgi for PHP

2017-03-02 Thread Piotr Kubaj via freebsd-ports
Could you send me a truss(1) output of the relevant process? On 17-03-01 11:36:02, Miroslav Lachman wrote: > Piotr Kubaj wrote on 2017/03/01 11:13: > > If FPM works fine, it looks to me more like PHP error than Lighttpd's. > > Could you use truss(1) on Lighttpd'

Re: www/lighttpd 1.4.45 broken mod_fastcgi for PHP

2017-03-01 Thread Piotr Kubaj via freebsd-ports
If FPM works fine, it looks to me more like PHP error than Lighttpd's. Could you use truss(1) on Lighttpd's process to obtain more information? On 17-03-01 10:56:29, Miroslav Lachman wrote: > Piotr Kubaj wrote on 2017/03/01 08:59: > > Hi, > > > > I use Lighttp

Re: www/lighttpd 1.4.45 broken mod_fastcgi for PHP

2017-03-01 Thread Piotr Kubaj via freebsd-ports
Hi, I use Lighttpd 1.4.45_1 on 11.0-RELEASE with mod_fastcgi and php-cgi. There are no problems with this setup. Are you sure php-cgi processes are running are the socket file is present? On 17-03-01 00:36:46, Miroslav Lachman wrote: > Hi, > I upgraded from 1.4.44 to 1.4.45_1 and after service

Re: Change of email

2016-01-07 Thread Piotr Kubaj
My old email will work for a while, I'll do it when sending PR with other issues with the given port. On 01/07/16 13:45, Renato Botelho wrote: >> On Jan 7, 2016, at 10:44, Piotr Kubaj wrote: >> >> I'm changing my email to pku...@anongoth.pl. This email is written to

Re: FreeBSD Port: lighttpd-1.4.37

2015-12-07 Thread Piotr Kubaj
Could you test this diff? Index: Makefile === --- Makefile(revision 403188) +++ Makefile(working copy) @@ -2,7 +2,7 @@ # $FreeBSD$ PORTNAME?= lighttpd -PORTVERSION= 1.4.37 +PORTVERSION= 1.4.38 CATEGORIES?= www MA

Re: Is there an equivalent of NO_EXTRACT?

2015-09-08 Thread Piotr Kubaj
On 09/09/2015 07:07, Ben Woods wrote: > On 9 September 2015 at 07:00, Piotr Kubaj wrote: >> On 09/09/2015 06:44, Don Lewis wrote: >>> If you list the distfiles that you want to have automatically extracted >>> in EXTRACT_ONLY, then it will leave the unlisted ones u

Re: Is there an equivalent of NO_EXTRACT?

2015-09-08 Thread Piotr Kubaj
On 09/09/2015 06:44, Don Lewis wrote: > If you list the distfiles that you want to have automatically extracted > in EXTRACT_ONLY, then it will leave the unlisted ones untouched. But I want the other one to properly extract and compile. Does that mean I'd have to write my own extract: step? sign

Re: Is there an equivalent of NO_EXTRACT?

2015-09-08 Thread Piotr Kubaj
On 09/09/2015 00:58, Montgomery-Smith, Stephen wrote: > I think EXTRACT_ONLY will do the equivalent of what you need. > > > From: owner-freebsd-po...@freebsd.org [owner-freebsd-po...@freebsd.org] on > behalf of Piotr Kubaj [pku...@ris

Is there an equivalent of NO_EXTRACT?

2015-09-08 Thread Piotr Kubaj
I'm a maintainer of a few ports. For the next update I'm preparing, I want to make it possible to download some addons via options. The thing is, they are downloaded as-is. They are not meant to be extracted (although they are zips), since it's the program itself that manages it. Is there such a po