Re: [PKGNG] use more than one threads?
On Wed, Jan 30, 2013 at 09:14:35AM +, Matthew Seaman wrote: On 30/01/2013 09:00, Alex Keda wrote: man xz say about -T threads, --threads=threads but, when work pkg create -a it use only one: PID USERNAME THR PRI NICE SIZERES STATE C TIME WCPU COMMAND 48672 root1 1030 216M 117M CPU22 20:39 99.37% pkg create -a how I can use more than one CPU? pkgng doesn't call the xz executable for compressing packages; instead it uses library code via libarchive. So making it compress created packages is a bit more involved than just tweaking a command-line somewhere. However, yes, this would be a desirable behaviour. If you could open an issue at Github, that would be great. Cheers, Matthew PS. There's a brand-new freebsd-pkg@ mailing list which I'd encourage people to use for this sort of question. libarchive doesn't support yet threading as soon as libarchive supports it pkgng will automatically gain it. regards, Bapt pgpi5NTizzTbz.pgp Description: PGP signature
Re: FreeBSD Port: pecl-APC-3.1.13
Hello, Fabien. You wrote 31 января 2013 г., 13:48:42: FD I use this extension on several servers (4 with php5.4 and 2 with php5.3 FD with the same configuration) and since you've update apc to 3.1.14 it stop FD working with some apps in php 5.3. Same problem here: apache22 (2.2.23_4), php53 (5.3.21), and some sites stop working with pecl-APC-3.1.14 (server drops connection right after request, no messages in any log). -- // Black Lion AKA Lev Serebryakov l...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD Port: pecl-APC-3.1.13
W dniu 2013-02-01 09:32, Lev Serebryakov pisze: FD I use this extension on several servers (4 with php5.4 and 2 with php5.3 FD with the same configuration) and since you've update apc to 3.1.14 it stop FD working with some apps in php 5.3. Same problem here: apache22 (2.2.23_4), php53 (5.3.21), and some sites stop working with pecl-APC-3.1.14 (server drops connection right after request, no messages in any log). I got it with Kohana script. With 3.1.13 it worked fine, with 3.1.14 connection close and empty logs. -- best regards, Lukasz Wasikowski ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: pkgng update - No address record
On 01/02/2013 09:46, Ivan Voras wrote: Hello, I know that the default pkgng repos are not up yet (probably...) but even so, when I try to run pkg update on two machines, I get this error: # pkg update Updating repository catalogue pkg: http://pkg.freebsd.org/freebsd:9:x86:64/latest/repo.txz: No address record However, there are other machines where it succeeds: # pkg update Updating repository catalogue Repository catalogue is up-to-date, no need to fetch fresh copy The only difference I see is that the ones that fail have pkg 1.0.7 and the one that works is 1.0.2. Is this expected? Could you show us the pkg.conf from the various machines please? There have been some recent changes to support alternate forms of mirroring (SRV, HTTP) -- but the default, unless you overrode it, should be to resolve pkg.freebsd.org into actual HTTP servers and ports via decoding the SRV records. That hasn't changed for a long time. Cheers, Matthew PS. The new freebsd-pkg@... list would probably be a better venue for this question. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: pkgng update - No address record
On 01/02/2013 11:05, Matthew Seaman wrote:
On 01/02/2013 09:46, Ivan Voras wrote:
Hello,
I know that the default pkgng repos are not up yet (probably...) but
even so, when I try to run pkg update on two machines, I get this error:
# pkg update
Updating repository catalogue
pkg: http://pkg.freebsd.org/freebsd:9:x86:64/latest/repo.txz: No address
record
However, there are other machines where it succeeds:
# pkg update
Updating repository catalogue
Repository catalogue is up-to-date, no need to fetch fresh copy
The only difference I see is that the ones that fail have pkg 1.0.7 and
the one that works is 1.0.2. Is this expected?
Could you show us the pkg.conf from the various machines please?
On all the machines, the pkg.conf is a copy of pkg.conf.sample and the
only uncommented line is:
PACKAGESITE : http://pkg.freebsd.org/${ABI}/latest
I've verified that the URL is the same on two of the machines. However,
the two machines are on different DNS servers. I've tried to debug using
dig -t SRV pkg.freebsd.org but on both machines it shows no response.
I've also tried this:
http://dnsrlookup.onlinetoolkit.org/?host=pkg.freebsd.orgrecordtype=SRV
with same results, so it's probably not the way to debug it :)
signature.asc
Description: OpenPGP digital signature
GNU style getopt problem
I am trying to get a linux app to compile in the native FreeBSD environment. I have solved most of the problems, except one: getopt. I have installed misc/getopt because compile-check asks for Build dependency: Please install GNU getopt However, the problem persists because the depends-check script checks for and as answer gets: $ getopt --help 2 1 | grep long /dev/null Ambiguous output redirect. But if I do an arrow up to get to the previous command I see this, where it's 1 not 1 $ getopt --help 2 1 | grep long /dev/null Should I be trying a different port? -- View this message in context: http://freebsd.1045724.n5.nabble.com/GNU-style-getopt-problem-tp5782884.html Sent from the freebsd-ports mailing list archive at Nabble.com. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: pkgng update - No address record
On 01/02/2013 10:16, Ivan Voras wrote: I've verified that the URL is the same on two of the machines. However, the two machines are on different DNS servers. I've tried to debug using dig -t SRV pkg.freebsd.org but on both machines it shows no response. I've also tried this: http://dnsrlookup.onlinetoolkit.org/?host=pkg.freebsd.orgrecordtype=SRV with same results, so it's probably not the way to debug it :) Looks like the SRV record has mysteriously disappeared: % dig pkg.freebsd.org IN SRV ; DiG 9.8.4-P1 pkg.freebsd.org IN SRV ;; global options: +cmd ;; Got answer: ;; -HEADER- opcode: QUERY, status: NOERROR, id: 59444 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;pkg.freebsd.org. IN SRV ;; AUTHORITY SECTION: freebsd.org.600 IN SOA ns0.freebsd.org. hostmaster.freebsd.org. 2013013104 3600 900 604800 600 ;; Query time: 45 msec ;; SERVER: ::1#53(::1) ;; WHEN: Fri Feb 1 11:09:57 2013 ;; MSG SIZE rcvd: 84 Hmmm Matthew ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: pkgng update - No address record
On Fri, Feb 01, 2013 at 11:10:45AM +, Matthew Seaman wrote: On 01/02/2013 10:16, Ivan Voras wrote: I've verified that the URL is the same on two of the machines. However, the two machines are on different DNS servers. I've tried to debug using dig -t SRV pkg.freebsd.org but on both machines it shows no response. I've also tried this: http://dnsrlookup.onlinetoolkit.org/?host=pkg.freebsd.orgrecordtype=SRV with same results, so it's probably not the way to debug it :) Looks like the SRV record has mysteriously disappeared: % dig pkg.freebsd.org IN SRV ; DiG 9.8.4-P1 pkg.freebsd.org IN SRV ;; global options: +cmd ;; Got answer: ;; -HEADER- opcode: QUERY, status: NOERROR, id: 59444 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;pkg.freebsd.org. IN SRV ;; AUTHORITY SECTION: freebsd.org.600 IN SOA ns0.freebsd.org. hostmaster.freebsd.org. 2013013104 3600 900 604800 600 ;; Query time: 45 msec ;; SERVER: ::1#53(::1) ;; WHEN: Fri Feb 1 11:09:57 2013 ;; MSG SIZE rcvd: 84 Hmmm Matthew works here: ; DiG 9.8.1-P1 -t srv _http._tcp.pkg.freebsd.org ;; global options: +cmd ;; Got answer: ;; -HEADER- opcode: QUERY, status: NOERROR, id: 54951 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;_http._tcp.pkg.freebsd.org.IN SRV ;; ANSWER SECTION: _http._tcp.pkg.freebsd.org. 3594 IN SRV 10 10 80 pkgbeta.freebsd.org. ;; Query time: 2 msec ;; SERVER: 213.186.33.99#53(213.186.33.99) ;; WHEN: Fri Feb 1 12:19:02 2013 ;; MSG SIZE rcvd: 83 regards, Bapt pgp1l3gzh90J7.pgp Description: PGP signature
shells/mksh does not compile with gcc47
With clang 3.2 it works fine though.
No strange flags, only CPUTYPE?=native (penryn,
detected correctly both by clang and gcc47)
Related bit:
conftest.c || for _f in ${tcfn}*; do case $_f in
Build.sh|check.pl|check.t|dot.mkshrc|*.c|*.h|mksh.1) ;; *) rm -f $_f ;;
esac; done
] conftest.c:29:1: error: variably modified 'ari_sign_32_bit_and_wrap' at
file scope
== whether compile-time assertions pass... no
*** [do-build] Error code 1
Stop in /usr/ports/shells/mksh.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/shells-mksh-does-not-compile-with-gcc47-tp5782887.html
Sent from the freebsd-ports mailing list archive at Nabble.com.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: pkgng update - No address record
On 01/02/2013 11:19, Baptiste Daroussin wrote: On Fri, Feb 01, 2013 at 11:10:45AM +, Matthew Seaman wrote: On 01/02/2013 10:16, Ivan Voras wrote: I've verified that the URL is the same on two of the machines. However, the two machines are on different DNS servers. I've tried to debug using dig -t SRV pkg.freebsd.org but on both machines it shows no response. I've also tried this: http://dnsrlookup.onlinetoolkit.org/?host=pkg.freebsd.orgrecordtype=SRV with same results, so it's probably not the way to debug it :) Looks like the SRV record has mysteriously disappeared: % dig pkg.freebsd.org IN SRV ; DiG 9.8.4-P1 pkg.freebsd.org IN SRV ;; global options: +cmd ;; Got answer: ;; -HEADER- opcode: QUERY, status: NOERROR, id: 59444 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;pkg.freebsd.org. IN SRV ;; AUTHORITY SECTION: freebsd.org.600 IN SOA ns0.freebsd.org. hostmaster.freebsd.org. 2013013104 3600 900 604800 600 ;; Query time: 45 msec ;; SERVER: ::1#53(::1) ;; WHEN: Fri Feb 1 11:09:57 2013 ;; MSG SIZE rcvd: 84 Hmmm Matthew works here: ; DiG 9.8.1-P1 -t srv _http._tcp.pkg.freebsd.org ;; global options: +cmd ;; Got answer: ;; -HEADER- opcode: QUERY, status: NOERROR, id: 54951 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;_http._tcp.pkg.freebsd.org. IN SRV ;; ANSWER SECTION: _http._tcp.pkg.freebsd.org. 3594 IN SRV 10 10 80 pkgbeta.freebsd.org. ;; Query time: 2 msec ;; SERVER: 213.186.33.99#53(213.186.33.99) ;; WHEN: Fri Feb 1 12:19:02 2013 ;; MSG SIZE rcvd: 83 regards, Bapt D'Oh -- I'm suffering from the stupids today. Matthew ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: GNU style getopt problem
## Beeblebrox (zap...@berentweb.com): However, the problem persists because the depends-check script checks for and as answer gets: $ getopt --help 2 1 | grep long /dev/null Ambiguous output redirect. I believe that should be 2 1 (or 21) but 2 1 does not redirect stderr (fd 2). Regards, Christoph -- Spare Space ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Status of devel/icu, or icu4c
What is the status of devel/icu? I see on http://site.icu-project.org that ICU4J 50.1.1 released on 2012-Dec-17 ICU4C 50.1.2 released on 2013-Jan-16 I keep following http://www.freshports.org/commits.php daily, generally somewhat after midnight UTC, and nothing on devel/icu since I saw the update for NetBSD pkgsrc, whose updates I also follow daily somewhat after midnight UTC. I checked devel/icu/distinfo, and the icu4c distfile is still on 50.1.1. I'm concerned because the usr/ports/UPDATING file says all ports that depend on devel/icu need to be rebuilt/updated. Or is that due to a bump in the .so.49 - .so.50 file that would not be affected by a minor version update such as 50.1.1 to 50.1.2? devel/icu has been updated to 50.1.2. Yes the updating entry concerned the switch from .so.49 - .so.50 regards, Bapt Thanks for letting me know, but I had already checked http://www.freshports.org/commits.php before downloading my email, though I could have looked at the web version of the most recent posts to po...@freebsd.org . I suppose failing to update all ports/packages that depend on a recently updated port/package could result in shared-library versions out of sync. Now I can have fun with a massive portmaster run. Tom ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
ia64 -current: updating devel/boost-lib to 1.52 from 1.48 failed
This is on ia64 r244834, with ports tree at r311350. I managed to updated devel/boost-jam fine: # pkg version -vX boost boost-jam-1.52.0 = up-to-date with port boost-libs-1.48.0_2 needs updating (port has 1.52.0) # The boost-libs build fails with messages like: ./boost/context/fcontext.hpp:59:3: error: #error platform not supported A fuller log: http://seis.bris.ac.uk/~mexas/ia64-boost-libs-1.52.log I can post the full build log if needed. Please advise Thanks Anton ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: GNU style getopt problem
Hi, thanks for replying I tried both $ getopt --help 2 1 | grep long /dev/null $ getopt --help 21 | grep long /dev/null And got the Ambiguous output redirect message., and up arrow in both instances showed the code as 2 1 Unless you meant ? $ getopt --help 21 -- 21 -- View this message in context: http://freebsd.1045724.n5.nabble.com/GNU-style-getopt-problem-tp5782884p5782949.html Sent from the freebsd-ports mailing list archive at Nabble.com. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: GNU style getopt problem
Interesting - when I switch to bash and try it: getopt --help 2 1 | grep long bash: syntax error near unexpected token `' while this one gives no message - I guess I'll try a test with this. $ getopt --help 21 | grep long -- View this message in context: http://freebsd.1045724.n5.nabble.com/GNU-style-getopt-problem-tp5782884p5782951.html Sent from the freebsd-ports mailing list archive at Nabble.com. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
FreeBSD ports you maintain which are out of date
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/guile-lib | 0.2.1 | 0.2.2 +-+ textproc/py-jaxml | 3.02| 7.01 +-+ 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 If wish to stop receiving portscout reminders, please contact portsc...@portscout.freebsd.org Thanks. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
security/gnupg
Many users have reported in the past that one of the problems with the ports system is that OPTIONS are not properly documented. Usually, if I spend some time, I can locate it but it is a PIA. However, with the security/gnupg port, I cannot find out specifically what this option does: [ ] STD_SOCKET Use standard socket for agent This is off by default. Is there any advantage to activating it and why isn't it using a standard socket to begin with? Maybe if a port had a file name options-descr or some such thing and it listed each available option in the port and specifically what it did or how it effected the operation of the application, it would prove beneficial to the end use. Just my 2¢ on the matter. -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD Port: pecl-APC-3.1.13
On 01.02.13 09:59, Łukasz Wąsikowski wrote: W dniu 2013-02-01 09:32, Lev Serebryakov pisze: FD I use this extension on several servers (4 with php5.4 and 2 with php5.3 FD with the same configuration) and since you've update apc to 3.1.14 it stop FD working with some apps in php 5.3. Same problem here: apache22 (2.2.23_4), php53 (5.3.21), and some sites stop working with pecl-APC-3.1.14 (server drops connection right after request, no messages in any log). I got it with Kohana script. With 3.1.13 it worked fine, with 3.1.14 connection close and empty logs. It looks like pecl-APC-3.1.14 was pulled, due to a lot of reported problems. https://bugs.php.net/bug.php?id=64116 http://pecl.php.net/package/APC Florian signature.asc Description: OpenPGP digital signature
Re: security/gnupg
On 1 Feb 2013 15:34, Jerry je...@seibercom.net wrote: Many users have reported in the past that one of the problems with the ports system is that OPTIONS are not properly documented. Usually, if I spend some time, I can locate it but it is a PIA. However, with the security/gnupg port, I cannot find out specifically what this option does: [ ] STD_SOCKET Use standard socket for agent This is off by default. Is there any advantage to activating it and why isn't it using a standard socket to begin with? Maybe if a port had a file name options-descr or some such thing and it listed each available option in the port and specifically what it did or how it effected the operation of the application, it would prove beneficial to the end use. Just my 2¢ on the matter. You're right, and ports will move towards more verbose option descriptions in the future. However, the version dialog in older (but still supported) versions of FreeBSD chokes on long descriptions. Once we are free of supporting older versions, longer/more descriptive descriptions will be possible. Perhaps Kuriyama-san may comment on STD_SOCKET, but my general rule of thumb is to customise as little as possible, so if the option isn't obviously what you want, just leave it as default :) Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: security/gnupg
On Fri, 1 Feb 2013 16:42:46 + Chris Rees articulated: You're right, and ports will move towards more verbose option descriptions in the future. However, the version dialog in older (but still supported) versions of FreeBSD chokes on long descriptions. Once we are free of supporting older versions, longer/more descriptive descriptions will be possible. Perhaps Kuriyama-san may comment on STD_SOCKET, but my general rule of thumb is to customise as little as possible, so if the option isn't obviously what you want, just leave it as default :) I concur. I rarely modify the port unless I have a specific reason for doing so. -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: security/gnupg
On Fri, Feb 1, 2013 at 8:42 AM, Chris Rees utis...@gmail.com wrote: On 1 Feb 2013 15:34, Jerry je...@seibercom.net wrote: Many users have reported in the past that one of the problems with the ports system is that OPTIONS are not properly documented. Usually, if I spend some time, I can locate it but it is a PIA. However, with the security/gnupg port, I cannot find out specifically what this option does: [ ] STD_SOCKET Use standard socket for agent This is off by default. Is there any advantage to activating it and why isn't it using a standard socket to begin with? Maybe if a port had a file name options-descr or some such thing and it listed each available option in the port and specifically what it did or how it effected the operation of the application, it would prove beneficial to the end use. Just my 2¢ on the matter. You're right, and ports will move towards more verbose option descriptions in the future. However, the version dialog in older (but still supported) versions of FreeBSD chokes on long descriptions. Once we are free of supporting older versions, longer/more descriptive descriptions will be possible. Perhaps Kuriyama-san may comment on STD_SOCKET, but my general rule of thumb is to customise as little as possible, so if the option isn't obviously what you want, just leave it as default :) Chris Agreed with all of stated above, and please use the documentation as well to see if it is noted there. Enabling the flag in the port adds --enable-standard-socket to the CONFIGURE arguments for the ports build process. http://www.gnupg.org/documentation/manuals/gnupg/Agent-Options.html --use-standard-socket--no-use-standard-socketBy enabling this option gpg-agent will listen on the socket named S.gpg-agent, located in the home directory, and not create a random socket below a temporary directory. Tools connecting to gpg-agent should first try to connect to the socket given in environment variable GPG_AGENT_INFO and then fall back to this socket. This option may not be used if the home directory is mounted on a remote file system which does not support special files like fifos or sockets. Note, that --use-standard-socket is the default on Windows systems. The default may be changed at build time. It is possible to test at runtime whether the agent has been configured for use with the standard socket by issuing the command gpg-agent --use-standard-socket-p which returns success if the standard socket option has been enabled. HTH -jgh ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD Port: pecl-APC-3.1.13
Hi, I've reverted pecl-APC to 3.1.13. Thanks. Regards, sunpoet On Sat, Feb 2, 2013 at 12:04 AM, Florian Smeets f...@smeets.im wrote: On 01.02.13 09:59, Łukasz Wąsikowski wrote: W dniu 2013-02-01 09:32, Lev Serebryakov pisze: FD I use this extension on several servers (4 with php5.4 and 2 with php5.3 FD with the same configuration) and since you've update apc to 3.1.14 it stop FD working with some apps in php 5.3. Same problem here: apache22 (2.2.23_4), php53 (5.3.21), and some sites stop working with pecl-APC-3.1.14 (server drops connection right after request, no messages in any log). I got it with Kohana script. With 3.1.13 it worked fine, with 3.1.14 connection close and empty logs. It looks like pecl-APC-3.1.14 was pulled, due to a lot of reported problems. https://bugs.php.net/bug.php?id=64116 http://pecl.php.net/package/APC Florian ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
zsh crash
Hi all, I am seeing a very common crash now in zsh. The backtrace is here (and this it shows a corrupt stack / missing symbols). I'm still working on figuring out a reproducible version of the crash, but so far it seems to relate to sending SIGINT. gdb bt #0 0x00464f18 in wait_for_processes () #1 0x004653c6 in zhandler () #2 0x0044567c in zfree () #3 0x0041e60b in execrestore () #4 0x004647fd in queue_traps () #5 0x00464b37 in dotrap () #6 0x00465414 in zhandler () #7 0x00439ae7 in waitforpid () #8 0x00426fa4 in getoutput () #9 0x0046938a in quotesubst () #10 0x0046de99 in prefork () #11 0x0041f492 in execsubst () #12 0x0041f869 in execsubst () #13 0x00425235 in execlist () #14 0x004258fb in execode () #15 0x00425a64 in runshfunc () #16 0x00425e64 in doshfunc () #17 0x00472dee in callhookfunc () #18 0x0047a543 in preprompt () #19 0x00437600 in loop () #20 0x00438606 in zsh_main () #21 0x0040e31e in _start () ---Type return to continue, or q return gdb frame Stack level 0, frame at 0x7fffccb0: rip = 0x464f18 in wait_for_processes; saved rip 0x4653c6 called by frame at 0x7fffccf0 Arglist at 0x7fffcbb8, args: Locals at 0x7fffcbb8, Previous frame's sp is 0x7fffccb0 Saved registers: rbx at 0x7fffcc78, rbp at 0x7fffcc80, r12 at 0x7fffcc88, r13 at 0x7fffcc90, r14 at 0x7fffcc98, r15 at 0x7fffcca0, rip at 0x7fffcca8 gdb lib FromTo Syms Read Shared Object Library 0x0008008a8b90 0x0008008ac8a8 Yes /usr/local/lib/libgdbm.so.4 0x000800ab0c70 0x000800ac86a8 Yes /usr/local/lib/libiconv.so.3 0x000800dbe590 0x000800deddc8 Yes /lib/libncursesw.so.8 0x0008010087c0 0x00080101e1b8 Yes /lib/libm.so.5 0x0008012571d0 0x000801329358 Yes /lib/libc.so.7 0x00080158f1d0 0x0008015b2288 Yes /usr/local/lib/zsh/5.0.2/zsh/zle.so 0x0008017c9cc0 0x0008017e00f8 Yes /usr/local/lib/zsh/5.0.2/zsh/complete.so 0x0008019e7a80 0x0008019f0488 Yes /usr/local/lib/zsh/5.0.2/zsh/complist.so 0x000801bf4f70 0x000801bf8a38 Yes /usr/local/lib/zsh/5.0.2/zsh/parameter.so 0x000801dfce30 0x000801e00588 Yes /usr/local/lib/zsh/5.0.2/zsh/zutil.so 0x000802002e10 0x0008020034a8 Yes /usr/local/lib/zsh/5.0.2/zsh/terminfo.so 0x00080068ff70 0x00080069fe68 Yes /libexec/ld-elf.so.1 -- Eitan Adler ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
