FreeBSD ports you maintain which are out of date

[portscout]

Dear port maintainer,

The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you can
safely ignore the entry.

You will not be e-mailed again for any of the port/version combinations
below.

Full details can be found at the following URL:
http://portscout.freebsd.org/po...@freebsd.org.html


Port| Current version | New version
+-+
devel/xa65  | 2.3.7   | 2.3.8
+-+


If any of the above results are invalid, please check the following page
for details on how to improve portscout's detection and selection of
distfiles on a per-port basis:

http://portscout.freebsd.org/info/portscout-portconfig.txt

Thanks.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

unable to pkg upgrade: Assertion failed: (strcmp(uid, p->uid) != 0)

[Stefan Bethke]

# pkg upgrade
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
Updating zs64 repository catalogue...
zs64 repository is up to date.
All repositories are up to date.
Checking for upgrades (431 candidates): 100%
Processing candidates (431 candidates): 100%
Checking integrity...Assertion failed: (strcmp(uid, p->uid) != 0), function 
pkg_conflicts_check_local_path, file pkg_jobs_conflicts.c, line 386.
Child process pid=12379 terminated abnormally: Abort trap
# uname -a
FreeBSD krokodil.zs64.net 11.1-BETA2 FreeBSD 11.1-BETA2 #5 r320116: Mon Jun 19 
19:53:49 UTC 2017 
r...@lokschuppen.zs64.net:/usr/obj/freebsd/checkout/src/sys/EISENBOOT  amd64
# pkg -v
1.10.1


Any suggestions? Other jails on the same host update fine.


Stefan

-- 
Stefan BethkeFon +49 151 14070811




___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

print/texinfo build, and httpd dying?

[Larry Rosenman]

Upgraded my -CURRENT system today, and httpd dies on a SIGSEGV, and I can't 
build
print/texinfo.

anyone else having issues building texinfo on -CURRENT? 
panic: bad free, ->next->prev=80509aaa0, header=80509aaa0, 
->prev->next=a5a5a5a5a5a50020 at ../tp/Texinfo/Parser.pm line 3907.
panic: bad free, ->next->prev=5a5a5a5a5a5a5a5a, header=80509a9b0, 
->prev->next=80509a9b0 during global destruction.
gmake[4]: *** [Makefile:1297: info-stnd.info] Error 25
gmake[4]: *** Waiting for unfinished jobs
Assertion failed: (header->next->prev == header), function Perl_safesysrealloc, 
file util.c, line 243.
Abort trap (core dumped)

[12:19] 
I also can’t get my httpd up it sigsegv’s in parsing it’s config

[12:19] 
driving me nuts today

[12:20] 
borg.lerctr.org 
/usr/local/poudriere/data/logs/bulk/live-host-ports/2017-07-02_12h16m20s/logs/errors
 $ uname -aKU
FreeBSD borg.lerctr.org 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r320573: Sun Jul  
2 10:50:05 CDT 2017 r...@borg.lerctr.org:/usr/obj/usr/src/sys/VT-LER  amd64 
1200037 1200037
borg.lerctr.org 
/usr/local/poudriere/data/logs/bulk/live-host-ports/2017-07-02_12h16m20s/logs/errors
 $

[12:21] 
borg.lerctr.org / $ gdb -c httpd.core /usr/local/sbin/httpd
GNU gdb (GDB) 7.12.1 [GDB v7.12.1 for FreeBSD]
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type “show copying”
and “show warranty” for details.
This GDB was configured as “x86_64-portbld-freebsd12.0”.
Type “show configuration” for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type “help”.
Type “apropos word” to search for commands related to “word”...
Reading symbols from /usr/local/sbin/httpd...(no debugging symbols 
found)...done.
[New LWP 101514]
Core was generated by `/usr/local/sbin/httpd -DNOHTTPACCEPT -t’.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x000801d09b90 in strcmp () from /lib/libc.so.7
(gdb) bt
#0  0x000801d09b90 in strcmp () from /lib/libc.so.7
#1  0x00457d9a in process_resource_config_fnmatch ()
#2  0x00457d2f in process_resource_config_fnmatch ()
#3  0x00457d2f in process_resource_config_fnmatch ()
#4  0x00457d2f in process_resource_config_fnmatch ()
#5  0x00457d2f in process_resource_config_fnmatch ()
#6  0x00457d2f in process_resource_config_fnmatch ()
#7  0x00457a69 in ap_process_fnmatch_configs ()
#8  0x00448eb0 in include_config ()
#9  0x00459ac8 in invoke_cmd ()
#10 0x00456cda in ap_build_config_sub ()
#11 0x004571ab in ap_build_config ()
#12 0x004578d9 in ap_process_resource_config ()
#13 0x00458d81 in ap_read_config ()
#14 0x00430c8d in main ()
(gdb)

-- 
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 E-Mail: l...@lerctr.org
US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

[poudriere] lang/go14 failing on 12.0-CURRENT i386?

[Ben Lavery-Griffiths]

Hi all,

Testing the latest www/gohugo port so I can submit a patch.  I’ve tested the 
port with the following:

> poudriere bulk -f pkglist -p local -tC -j 12Ci386


Where pkglist contains a single line with “www/gohugo”.  For all other jails 
(10.3 and 11.0 i386 and amd64, and 12.0-CURRENT amd64) everything passes, but 
with 12.0-CURRENT i386 it fails:

> [00:00:00] >> Creating the reference jail... done
> [00:00:01] >> Mounting system devices for 12Ci386-local
> [00:00:01] >> Mounting ports/packages/distfiles
> [00:00:01] >> Stashing existing package repository
> [00:00:01] >> Mounting packages from: 
> /poudriere/data/packages/12Ci386-local
> /etc/resolv.conf -> /poudriere/data/.m/12Ci386-local/ref/etc/resolv.conf
> [00:00:01] >> Starting jail 12Ci386-local
> [00:00:01] >> Logs: 
> /poudriere/data/logs/bulk/12Ci386-local/2017-07-02_19h40m46s
> [00:00:01] >> Loading MOVED
> [00:00:02] >> Calculating ports order and dependencies
> [00:00:02] >> (-C) Cleaning specified ports to build
> [00:00:03] >> Sanity checking the repository
> [00:00:03] >> Checking packages for incremental rebuild needed
> [00:00:03] >> Deleting stale symlinks
> [00:00:03] >> Deleting empty directories
> [00:00:03] >> Cleaning the build queue
> [00:00:03] >> Recording filesystem state for prepkg... done
> [00:00:05] >> Building 3 packages using 3 builders
> [00:00:05] >> Starting/Cloning builders
> [00:00:05] >> Hit CTRL+t at any time to see build progress and stats
> [00:00:05] >> [01][00:00:00] Starting build of lang/go14
> [00:00:06] >> [01][00:00:01] Finished build of lang/go14: Failed: 
> pkg-depends
> [00:00:06] >> [01][00:00:01] Skipping build of lang/go: Dependent port 
> lang/go14 failed
> [00:00:06] >> [01][00:00:01] Skipping build of www/gohugo: Dependent port 
> lang/go14 failed
> [00:00:06] >> Stopping 3 builders
> [00:00:06] >> No package built, no need to update the repository
> [00:00:06] >> Committing packages to repository
> [00:00:06] >> Removing old packages
> [00:00:06] >> Failed ports: lang/go14:pkg-depends
> [00:00:06] >> Skipped ports: lang/go www/gohugo
> [12Ci386-local] [2017-07-02_19h40m46s] [committing:] Queued: 3  Built: 0  
> Failed: 1  Skipped: 2  Ignored: 0  Tobuild: 0   Time: 00:00:05
> [00:00:06] >> Logs: 
> /poudriere/data/logs/bulk/12Ci386-local/2017-07-02_19h40m46s
> [00:00:06] >> Cleaning up
> [00:00:06] >> Unmounting file systems


Logs can be found here:
https://gist.github.com/forquare/cd7bcc22cbd44d4b55663dd9cb5db81d 


I’ve spun up an i386 install of the latest 12.0-CURRENT snapshot and doing a 
make/make install works fine there, but doesn’t seem to work in this poudriere 
jail…

Any ideas?

Many thanks,
Ben
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: sysutils/tmux - strange behaviour with new version 2.4 / 2.5

[Adam Weinberger]

> On 26 Jun, 2017, at 7:54, Miroslav Lachman <000.f...@quip.cz> wrote:
> 
> Vanilla Hsu wrote on 2017/05/16 01:37:
>> I got the same problem too, but after update to 2.5-rc2, all issues gone.
>> 
>> maybe you can try to update to 2.5-rc2 (2.5 not yet released) by yourself.
> 
> Opening this again. I downgraded to 2.3 in the meantime but I had a hope that 
> 2.5 will be fine - it is not. Event final 2.5 exhibits the same symptoms as 
> 2.4 on my machines and doesn't show innocent lines of text file.
> 
> Does 2.5 work for you or anybody else without issues? What is you tmux.conf? 
> (I tried it with empty but still have this problem)

I encountered the same problem, and it disappeared after I exported:

TERM=xterm-256color
LANG=en_US.UTF-8

In particular, make sure that LANG specifies UTF-8.

# Adam


-- 
Adam Weinberger
ad...@adamw.org
https://www.adamw.org


> 
> Miroslav Lachman
> 
> 
>> 2017-05-16 1:18 GMT+08:00 Miroslav Lachman <000.f...@quip.cz
>> >:
>> 
>>I noticed some strange behaviours with Tmux 2.4.
>>If I run "cat /path/to/somefile.txt" sometimes part of file is
>>missing in the output (no special characters in this text file, it
>>is log of "pkg upgrade")
>> 
>>And I thing some key presses are interpreted differently. (in Vim)
>> 
>>I know that nobody can solve this without more details... so I am
>>just asking if I am alone or somebody else have this problem too?
> 
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

It looks like USE_GCC=any is broken and leads to system-clang use

[Mark Millard]

[It looks like USE_GCC=any is broken and leads to system-clang use.]

On 2017-Jun-29, at 5:58 PM, Gerald Pfeifer  wrote:

> Am 29. Juni 2017 18:55:59 GMT+08:00 schrieb Mark Millard 
> :
>> I'm not currently set up to run more than head on
>> any of amd64, powerpc64, powerpc, aarch64, or armv6/7
>> (which are all I target). And I'm in the middle of
>> attempting a fairly large jump to head -r320458 on
>> those.
> 
> Oh, then I had misunderstood your previous mail. No worries, I'll gently 
> proceed then.
> 
> I expect to update gcc5 in the next 24 hours.
> 
>> [In my normal/head environment I'm switching to lang/gcc7-devel
>> for gcc (from lang/gcc6 ) but I'm odd that way.]
> 
> The compiler should be fine, it's a number of ports that are not (even 
> blocking the move from GCC 5 to 6 as default).

As part of testing that an environment seemed stable,
an environment based on head -r320570 and ports -r444872
with gcc being lang/gcc7-devel that is installed on
amd64, I tried:

script ~/ports_typescripts/phoronix-try-00-typescript portmaster -DK 
benchmarks/phoronix-test-suite

in part because it has:

USE_GCC=any

and I'm using:

DEFAULT_VERSIONS+=perl5=5.24 gcc=7

in /etc/make.conf and the gcc that I have installed
is lang/gcc7-devel. This should also have been a test
of the adjusted-header removal that has been applied
to lang/gcc7-devel (but not a old environment's build
used under a modern system environment).

But the result was a surprise: the log file
shows all the build as using cc and in my context
cc is:

# cc --version
FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on LLVM 
4.0.0)
Target: x86_64-unknown-freebsd12.0
Thread model: posix
InstalledDir: /usr/bin

Configure repeatedly shows:

checking for gcc... cc
. . .
checking whether we are using the GNU C compiler... yes


In fact "phoronix-test-suite diagnostics" reports:

COMPILER = Clang 4.0.0 (SVN 297347) + LLVM 4.0.0

So clang is being treated as an example of gcc as far
as I can tell.


===
Mark Millard
markmi at dsl-only.net

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: It looks like USE_GCC=any is broken and leads to system-clang use

[Mark Millard]

[Looks like output from "make test-gcc" is appropriate,
so I'm adding such.]

On 2017-Jul-2, at 7:53 PM, Mark Millard  wrote:

> [It looks like USE_GCC=any is broken and leads to system-clang use.]
> 
> On 2017-Jun-29, at 5:58 PM, Gerald Pfeifer  wrote:
> 
>> Am 29. Juni 2017 18:55:59 GMT+08:00 schrieb Mark Millard 
>> :
>>> I'm not currently set up to run more than head on
>>> any of amd64, powerpc64, powerpc, aarch64, or armv6/7
>>> (which are all I target). And I'm in the middle of
>>> attempting a fairly large jump to head -r320458 on
>>> those.
>> 
>> Oh, then I had misunderstood your previous mail. No worries, I'll gently 
>> proceed then.
>> 
>> I expect to update gcc5 in the next 24 hours.
>> 
>>> [In my normal/head environment I'm switching to lang/gcc7-devel
>>> for gcc (from lang/gcc6 ) but I'm odd that way.]
>> 
>> The compiler should be fine, it's a number of ports that are not (even 
>> blocking the move from GCC 5 to 6 as default).
> 
> As part of testing that an environment seemed stable,
> an environment based on head -r320570 and ports -r444872
> with gcc being lang/gcc7-devel that is installed on
> amd64, I tried:
> 
> script ~/ports_typescripts/phoronix-try-00-typescript portmaster -DK 
> benchmarks/phoronix-test-suite
> 
> in part because it has:
> 
> USE_GCC=any
> 
> and I'm using:
> 
> DEFAULT_VERSIONS+=perl5=5.24 gcc=7
> 
> in /etc/make.conf and the gcc that I have installed
> is lang/gcc7-devel. This should also have been a test
> of the adjusted-header removal that has been applied
> to lang/gcc7-devel (but not a old environment's build
> used under a modern system environment).
> 
> But the result was a surprise: the log file
> shows all the build as using cc and in my context
> cc is:
> 
> # cc --version
> FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on LLVM 
> 4.0.0)
> Target: x86_64-unknown-freebsd12.0
> Thread model: posix
> InstalledDir: /usr/bin
> 
> Configure repeatedly shows:
> 
> checking for gcc... cc
> . . .
> checking whether we are using the GNU C compiler... yes
> 
> 
> In fact "phoronix-test-suite diagnostics" reports:
> 
> COMPILER = Clang 4.0.0 (SVN 297347) + LLVM 4.0.0
> 
> So clang is being treated as an example of gcc as far
> as I can tell.

# cd /usr/ports/benchmarks/phoronix-test-suite/
FreeBSDx64OPC# make test-gcc
USE_GCC=any
Port can use later versions.
GCC version: 4.2 - OSVERSION up to 999
GCC version: 4.8 - OSVERSION up to 0
GCC version: 4.9 - OSVERSION up to 0
GCC version: 5 - OSVERSION up to 0
GCC version: 6 - OSVERSION up to 0
Using GCC version 7
CC=cc - CXX=c++ - CPP=cpp - CFLAGS="-O2 -pipe -g -fstack-protector 
-fno-strict-aliasing"
LDFLAGS=" -fstack-protector"
BUILD_DEPENDS=/usr/local/include/php/main/php.h:lang/php56 
/usr/local/bin/python2.7:lang/python27 
update-desktop-database:devel/desktop-file-utils 
update-mime-database:misc/shared-mime-info 
/usr/local/lib/php/20131226/ctype.so:textproc/php56-ctype 
/usr/local/lib/php/20131226/curl.so:ftp/php56-curl 
/usr/local/lib/php/20131226/dom.so:textproc/php56-dom 
/usr/local/lib/php/20131226/filter.so:security/php56-filter 
/usr/local/lib/php/20131226/gd.so:graphics/php56-gd 
/usr/local/lib/php/20131226/hash.so:security/php56-hash 
/usr/local/lib/php/20131226/json.so:devel/php56-json 
/usr/local/lib/php/20131226/openssl.so:security/php56-openssl 
/usr/local/lib/php/20131226/pcntl.so:devel/php56-pcntl 
/usr/local/lib/php/20131226/posix.so:sysutils/php56-posix 
/usr/local/lib/php/20131226/session.so:www/php56-session 
/usr/local/lib/php/20131226/simplexml.so:textproc/php56-simplexml 
/usr/local/lib/php/20131226/sockets.so:net/php56-sockets 
/usr/local/lib/php/20131226/sqlite3.so:databases/php56-sqlite3 /usr/l
 ocal/lib/php/20131226/zip.so:archivers/php56-zip 
/usr/local/lib/php/20131226/zlib.so:archivers/php56-zlib
RUN_DEPENDS=fpdf>0:print/fpdf cmake:devel/cmake 
/usr/local/include/php/main/php.h:lang/php56 
/usr/local/bin/python2.7:lang/python27 
update-desktop-database:devel/desktop-file-utils 
update-mime-database:misc/shared-mime-info 
/usr/local/lib/php/20131226/ctype.so:textproc/php56-ctype 
/usr/local/lib/php/20131226/curl.so:ftp/php56-curl 
/usr/local/lib/php/20131226/dom.so:textproc/php56-dom 
/usr/local/lib/php/20131226/filter.so:security/php56-filter 
/usr/local/lib/php/20131226/gd.so:graphics/php56-gd 
/usr/local/lib/php/20131226/hash.so:security/php56-hash 
/usr/local/lib/php/20131226/json.so:devel/php56-json 
/usr/local/lib/php/20131226/openssl.so:security/php56-openssl 
/usr/local/lib/php/20131226/pcntl.so:devel/php56-pcntl 
/usr/local/lib/php/20131226/posix.so:sysutils/php56-posix 
/usr/local/lib/php/20131226/session.so:www/php56-session 
/usr/local/lib/php/20131226/simplexml.so:textproc/php56-simplexml 
/usr/local/lib/php/20131226/sockets.so:net/php56-sockets 
/usr/local/lib/php/20131226/sqlite3
 .so:databases/php56-sqlite3 
/usr/local/lib/php/20131226/zip.so:archivers/php56-zip 
/usr/local/lib/php/20131226/zlib.so:archivers/php56-zlib

===
Mark Mil

Re: It looks like USE_GCC=any is broken and leads to system-clang use

[Mark Millard]

[More on the behavior: it is more complicated than
previously shown.]

On 2017-Jul-2, at 8:12 PM, Mark Millard  wrote:

> [Looks like output from "make test-gcc" is appropriate,
> so I'm adding such.]
> 
> On 2017-Jul-2, at 7:53 PM, Mark Millard  wrote:
> 
>> [It looks like USE_GCC=any is broken and leads to system-clang use.]
>> 
>> On 2017-Jun-29, at 5:58 PM, Gerald Pfeifer  wrote:
>> 
>>> Am 29. Juni 2017 18:55:59 GMT+08:00 schrieb Mark Millard 
>>> :
 I'm not currently set up to run more than head on
 any of amd64, powerpc64, powerpc, aarch64, or armv6/7
 (which are all I target). And I'm in the middle of
 attempting a fairly large jump to head -r320458 on
 those.
>>> 
>>> Oh, then I had misunderstood your previous mail. No worries, I'll gently 
>>> proceed then.
>>> 
>>> I expect to update gcc5 in the next 24 hours.
>>> 
 [In my normal/head environment I'm switching to lang/gcc7-devel
 for gcc (from lang/gcc6 ) but I'm odd that way.]
>>> 
>>> The compiler should be fine, it's a number of ports that are not (even 
>>> blocking the move from GCC 5 to 6 as default).
>> 
>> As part of testing that an environment seemed stable,
>> an environment based on head -r320570 and ports -r444872
>> with gcc being lang/gcc7-devel that is installed on
>> amd64, I tried:
>> 
>> script ~/ports_typescripts/phoronix-try-00-typescript portmaster -DK 
>> benchmarks/phoronix-test-suite
>> 
>> in part because it has:
>> 
>> USE_GCC=any
>> 
>> and I'm using:
>> 
>> DEFAULT_VERSIONS+=perl5=5.24 gcc=7
>> 
>> in /etc/make.conf and the gcc that I have installed
>> is lang/gcc7-devel. This should also have been a test
>> of the adjusted-header removal that has been applied
>> to lang/gcc7-devel (but not a old environment's build
>> used under a modern system environment).
>> 
>> But the result was a surprise: the log file
>> shows all the build as using cc and in my context
>> cc is:
>> 
>> # cc --version
>> FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on LLVM 
>> 4.0.0)
>> Target: x86_64-unknown-freebsd12.0
>> Thread model: posix
>> InstalledDir: /usr/bin
>> 
>> Configure repeatedly shows:
>> 
>> checking for gcc... cc
>> . . .
>> checking whether we are using the GNU C compiler... yes
>> 
>> 
>> In fact "phoronix-test-suite diagnostics" reports:
>> 
>> COMPILER = Clang 4.0.0 (SVN 297347) + LLVM 4.0.0
>> 
>> So clang is being treated as an example of gcc as far
>> as I can tell.
> 
> # cd /usr/ports/benchmarks/phoronix-test-suite/
> FreeBSDx64OPC# make test-gcc
> USE_GCC=any
> Port can use later versions.
> GCC version: 4.2 - OSVERSION up to 999
> GCC version: 4.8 - OSVERSION up to 0
> GCC version: 4.9 - OSVERSION up to 0
> GCC version: 5 - OSVERSION up to 0
> GCC version: 6 - OSVERSION up to 0
> Using GCC version 7
> CC=cc - CXX=c++ - CPP=cpp - CFLAGS="-O2 -pipe -g -fstack-protector 
> -fno-strict-aliasing"
> LDFLAGS=" -fstack-protector"
> BUILD_DEPENDS=/usr/local/include/php/main/php.h:lang/php56 
> /usr/local/bin/python2.7:lang/python27 
> update-desktop-database:devel/desktop-file-utils 
> update-mime-database:misc/shared-mime-info 
> /usr/local/lib/php/20131226/ctype.so:textproc/php56-ctype 
> /usr/local/lib/php/20131226/curl.so:ftp/php56-curl 
> /usr/local/lib/php/20131226/dom.so:textproc/php56-dom 
> /usr/local/lib/php/20131226/filter.so:security/php56-filter 
> /usr/local/lib/php/20131226/gd.so:graphics/php56-gd 
> /usr/local/lib/php/20131226/hash.so:security/php56-hash 
> /usr/local/lib/php/20131226/json.so:devel/php56-json 
> /usr/local/lib/php/20131226/openssl.so:security/php56-openssl 
> /usr/local/lib/php/20131226/pcntl.so:devel/php56-pcntl 
> /usr/local/lib/php/20131226/posix.so:sysutils/php56-posix 
> /usr/local/lib/php/20131226/session.so:www/php56-session 
> /usr/local/lib/php/20131226/simplexml.so:textproc/php56-simplexml 
> /usr/local/lib/php/20131226/sockets.so:net/php56-sockets 
> /usr/local/lib/php/20131226/sqlite3.so:databases/php56-sqlite3 /usr
 /l
> ocal/lib/php/20131226/zip.so:archivers/php56-zip 
> /usr/local/lib/php/20131226/zlib.so:archivers/php56-zlib
> RUN_DEPENDS=fpdf>0:print/fpdf cmake:devel/cmake 
> /usr/local/include/php/main/php.h:lang/php56 
> /usr/local/bin/python2.7:lang/python27 
> update-desktop-database:devel/desktop-file-utils 
> update-mime-database:misc/shared-mime-info 
> /usr/local/lib/php/20131226/ctype.so:textproc/php56-ctype 
> /usr/local/lib/php/20131226/curl.so:ftp/php56-curl 
> /usr/local/lib/php/20131226/dom.so:textproc/php56-dom 
> /usr/local/lib/php/20131226/filter.so:security/php56-filter 
> /usr/local/lib/php/20131226/gd.so:graphics/php56-gd 
> /usr/local/lib/php/20131226/hash.so:security/php56-hash 
> /usr/local/lib/php/20131226/json.so:devel/php56-json 
> /usr/local/lib/php/20131226/openssl.so:security/php56-openssl 
> /usr/local/lib/php/20131226/pcntl.so:devel/php56-pcntl 
> /usr/local/lib/php/20131226/posix.so:sysutils/php56-posix 
> /usr/local/lib/php/20131226/session.so:www/php56-session 
> /usr/local/lib/