Re: How to remove erroneous deps from pkgng
On Mon, Jul 23, 2012 at 08:04:44PM -0400, Jason E. Hale wrote: On Monday, July 23, 2012 20:50:34 Baptiste Daroussin wrote: Here is a plan for pkg-config, I hope it will statisfy everyone. First we need to get rid of pkg-config, since 0.26 we can't boostrap it anymore because it depends on glib which depends on pkg-config. Hopefully we have a viable alternative. What I will do is : step 1/ introduce a new pkgconf port (https://github.com/nenolod/pkgconf) which is 100% compatible with pkg-config and considers any incompatibility as a bug. along with this, I will introduce a new MACRO: http://people.freebsd.org/~bapt/USE_PKGCONFIG.diff USE_PKGCONFIG= yes or USE_PKGCONFIG= build will bring pkgconf only has a build dependency USE_PKGCONFIG= run will bring pkgconf has a run dependency (some things like ruby wrapper or perl wrapper) USE_PKGCONFIG= both will bring both run and build deps. Why a MACRO, because some ports may need en environnement variable in CONFIGURE_ENV PKG_CONFIG=pkgconf do work correctly. the USE_GNOME= pkgconfig will be automatically add USE_PKGCONFIG= both Yeah sorry for step one will keep pkgconf in both dependencies. This is necessary because too much ports rely on one of their deps bringing pkgconfig, and this concerns about 4k+ ports. All the gnome one (mostly), all the xorg one (xproto bring pkgconfig) most of the gtk ones, most of things depending on libxml2 and curl, from what I have seen. step 2/ advertise the maintainers to stop using USE_GNOME= pkgconfig but rather switch to USE_PKGCONFIG, and do it actively. setp 3/ drop USE_GNOME= pkgconfig from bsd.gnome.mk when switching to USE_PKGCONFIG becare full about the ports that depend on your ports to make sure, it doesn't expect pkgconfig being brought by your port. regards, Bapt I think it might be a good idea to factor out the pkg-config hacks provided by USE_GNOME=gnomehack as well, and expand it to work with CMake (or other build systems if needed). Most ports that install .pc files must be fixed to install them in libdata instead of lib. Jason E. Hale That is a good idea, good be done after the switch to pkgconf. It will need some volunteer :) regards, Bapt pgpQmsdoIGCqm.pgp Description: PGP signature
Re: lang/php53 dumps core
drich wrote: php keeps dumping core on some requests. There are days that it dumps core almost continuously. However there are days it works smoothly. Do you use e-accelerator? No. Here is full extension list: Hmmm... you might try moving memcache.so to the top of the list. Impossible - requires session. After that - dumps core. I have dealt with the php core dumping issue tons of times, generally I can find it running phpinfo();. Try the following: php -r 'phpinfo();' 21 | less I use `php -i /dev/null` to detect such errors. Anyway everything works like a charm but one special request into piwik causes php to dump core. -- Sphinx of black quartz judge my vow. ___ 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: lang/php53 dumps core
Olli Hauer wrote: Try starting with an empty extensions.ini and do the following test, if php coredumps it will mostly also cordump on the command line with the following tests. $ php -ie $ php -nme $ php -me Next do the same test with always only one extension enabled. If you got meanwhile a coredump then you know the single extension which dumps, else can be a combination of extensions or the load order. None of that fail for me. -- Sphinx of black quartz judge my vow. ___ 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: lang/php53 dumps core
Reko Turja wrote:
From: Volodymyr Kostyrko
Rebuilding whole PHP without clang/gcc4.6 (my local settings) dumps
core with this backtrace:
...
Maybe something like this in /etc/make.conf
..if ${.CURDIR:M*php53*}
WITH_DEBUG=YES
..endif
..if ${.CURDIR:M*php5-redis*}
WITH_DEBUG=YES
..endif
And rebuild php+extensions.
then load the corefile to gdb.
The bad thing about this is that if I rebuild everything WITH_DEBUG.
There's no more coredumps, everything works, except for enormous size of
leaks detected and written to log:
/tmp/ports/usr/ports/lang/php53/work/php-5.3.15/main/php_variables.c(53)
: Freeing 0x80247BF08 (946 bytes), script=-
Last leak repeated 1 time
=== Total 2 memory leaks detected ===
[Tue Jul 24 14:44:23 2012] Script: '-'
/tmp/ports/usr/ports/security/php-suhosin/work/suhosin-0.9.33/suhosin.c(971)
: Freeing 0x8024783C8 (68 bytes), script=-
Last leak repeated 1 time
=== Total 2 memory leaks detected ===
[Tue Jul 24 14:39:59 2012] Script: '-'
/tmp/ports/usr/ports/lang/php53/work/php-5.3.15/ext/standard/base64.c(69) :
Freeing 0x80B617348 (153 bytes), script=-
/tmp/ports/usr/ports/lang/php53/work/php-5.3.15/Zend/zend_alloc.c(2734)
: Actual location (location was relayed)
[Tue Jul 24 14:39:59 2012] Script: '-'
/tmp/ports/usr/ports/security/php-suhosin/work/suhosin-0.9.33/suhosin.c(971)
: Freeing 0x80B537ED8 (14 bytes), script=-
Last leak repeated 4 times
=== Total 6 memory leaks detected ===
--
Sphinx of black quartz judge my vow.
___
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: lang/php53 dumps core
Volodymyr Kostyrko wrote: On some of my servers php keeps dumping core on some requests. There are days that it dumps core almost continuously. However there are days it works smoothly. FreeBSD kohrah.xim.bz 9.0-RELEASE-p3 FreeBSD 9.0-RELEASE-p3 #0 r236967: Tue Jun 12 22:25:24 EEST 2012 arc...@kohrah.xim.bz:/usr/obj/usr/src/sys/MINIMAL amd64 The general cause is: Jul 23 16:27:09 kohrah kernel: pid 49951 (php-fpm), uid 80: exited on signal 11 (core dumped) And in very rare case: [23-Jul-2012 16:26:40] WARNING: [pool www] child 49887 said into stderr: zend_mm_heap corrupted [23-Jul-2012 16:26:40] WARNING: [pool www] child 49887 exited with code 1 after 36.791579 seconds from start There's a backtrace on the core: #0 0x0056b9fe in gc_zval_possible_root () [New Thread 802007400 (LWP 149340/php-fpm)] (gdb) bt full #0 0x0056b9fe in gc_zval_possible_root () No symbol table info available. #1 0x0055ce83 in zend_hash_destroy () No symbol table info available. #2 0x0056f79e in zend_objects_free_object_storage () No symbol table info available. #3 0x00572757 in zend_objects_store_free_object_storage () No symbol table info available. #4 0x005465eb in shutdown_executor () No symbol table info available. #5 0x00552400 in zend_deactivate () No symbol table info available. #6 0x00506506 in php_request_shutdown () No symbol table info available. #7 0x005d0548 in main () No symbol table info available. What other data I should collect to file a PR? Or is this just a memory problem? My thanks to all who helped as I found the cause of problem. 1. If suhosin and memcache are loaded script dumps core. 2. If memcache is loaded script occasionally dumps core. Looks like suhosin narrows the problem down. 3. If php is build WITH_DEBUG problem vanishes. A lot of leaks are reported though. So the problem is actually an unplugged memory leak. Should those ones be reported anywhere? -- Sphinx of black quartz judge my vow. ___ 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: (semi-)official git mirror of ports svn repo?
On Tue, 2012-07-24 at 00:05:49 +0300, Andriy Gapon wrote: Do we have a (semi-)official git mirror of the new ports _svn_ repo? Something either FreeBSD hosted/managed or maintained by prominent ports developers on github/gitorious/elsewhere? I looked at gitorious, github and freebsd.your.org and only this github repository seems to be active: https://github.com/freebsd/freebsd-ports/commits/master But note sure if it based off svn. Yes, it's to become the official one, once I get my act together. It's still missing the git-notes, but that will be fixed later and doesn't impact anything, really. So please use git://github.com/freebsd/freebsd-ports.git or the source as a fallback git://git.freebsd.org/freebsd-ports.git Cheers, Uli ___ 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: [CFT] editors/emacs to 24.1
Hi I missed two diffs in the previous Emacs 24.1 update I sent for testing. I've updated the diff file[1] with following new diffs added: files/patch-src_config.in - reported by Jan, which silences the implicit declaration of 'openpty' function compiler warning. files/patch-src_term.c - a diff from NetBSD emacs port which fixes a segfault (provided by Yuji) References: [1] http://people.freebsd.org/~ashish/diffs/emacs-24.1.diff Thanks -- Ashish SHUKLA | GPG: F682 CDCC 39DC 0FEA E116 20B6 C746 CFA9 E74F A4B0 Sent from my Emacs pgpIBQ8z1Sml9.pgp Description: PGP signature
Re: (semi-)official git mirror of ports svn repo?
on 24/07/2012 18:58 Ulrich Spörlein said the following: Yes, it's to become the official one, once I get my act together. It's still missing the git-notes, but that will be fixed later and doesn't impact anything, really. So please use git://github.com/freebsd/freebsd-ports.git or the source as a fallback git://git.freebsd.org/freebsd-ports.git Thank you very much! P.S. Also thank you for teaching me about Mail-Followup-To :-) -- Andriy Gapon ___ 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
mutt 1.5 much slower than mutt 1.4
mail/mutt is much slower on my amd64 and ia64 -current boxes after it was updated from 1.4 to 1.5. Each keystroke takes few seconds to act. Below is my mutt 1.5 config: === The following configuration options are available for mutt-1.5.21: MUTT_ASPELL=off: Enable aspell support MUTT_COMPRESSED_FOLDERS=on: Enable compressed folders MUTT_CYRUS_SASL2=off: Enable SASL2 authentication MUTT_DEBUG=off: Enable debugging capabilities MUTT_FLOCK=off: Enable flock() usage MUTT_GPGME=off: Enable gpgme interface MUTT_GREETING_PATCH=off: Enable greeting MUTT_HTML=on: Enable HTML documentation MUTT_ICONV=on: Enable iconv support MUTT_IDN=off: Enable idn support MUTT_IFDEF_PATCH=off: Enable ifdef feature MUTT_IMAP_HEADER_CACHE=on: Enable imap header cache MUTT_ISPELL=off: Enable ispell support MUTT_LOCALES_FIX=off: Enable locales fix MUTT_MAILBOX_MANPAGES=on: Install mbox.5/mmdf.5 manpages MUTT_MAILDIR_HEADER_CACHE=off: Enable maildir header cache MUTT_MAILDIR_MTIME_PATCH=off: Enable Maildir mtime patch MUTT_MBOX_HOOK_PATCH=off: Enable enhanced mbox-hook MUTT_NCURSES=on: Enable ncurses support MUTT_NCURSES_PORT=off: Use ncurses from port MUTT_NNTP=off: Enable news reader MUTT_PARENT_CHILD_MATCH_PATCH=off: Enable parent/child match MUTT_QUOTE_PATCH=on: Enable extended quoting MUTT_REVERSE_REPLY_PATCH=off: Enable reverse_reply MUTT_SGMLFORMAT=on: Enable sgml support MUTT_SIDEBAR_PATCH=off: Enable sidebar MUTT_SIGNATURE_MENU=off: Enable signature menu MUTT_SLANG=off: Enable slang support MUTT_SMIME_OUTLOOK_COMPAT=on: SMIME outlook compatible MUTT_SMTP=off: Enable SMTP relay support MUTT_TRASH_PATCH=off: Enable trash folder support MUTT_XML=off: Use XML tools for docu === Use 'make config' to modify these settings BUZI# Anybody else is seeing this behaviour? Any advice? -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ 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: CFT: New mplayer / mencoder snapshot
Hi,
New tarball is available for download:
http://bsdistfiles.googlecode.com/files/m20120724.tar.bz2
Changes:
- General cleanup using portlint (a.o. shlib versions)
- Rearrangement of compiler/binutils dependencies
- Inclusion of Juergen's suggestion for ${ARCH}==amd64 on legacy
systems (I was not able to reproduce the problem on my i386 jail)
Happy testing :-)
Riggs
___
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: Upgrading xmlto-0.0.24 to 0.0.25 failing
Am 23.07.2012 22:50, schrieb sindrome: Can't upgrade xmlto -- anyone have ideas? === Building for xmlto-0.0.25 make all-am depbase=`echo xmlif/xmlif.o | sed 's|[^/]*$|.deps/|;s|\.o$||'`; cc -DHAVE_CONFIG_H -I. -O2 -pipe -fno-strict-aliasing -MT xmlif/xmlif.o -MD -MP -MF $depbase.Tpo -c -o xmlif/xmlif.o xmlif/xmlif.c mv -f $depbase.Tpo $depbase.Po cc -O2 -pipe -fno-strict-aliasing -o xmlif/xmlif xmlif/xmlif.o FORMAT_DIR=./format /usr/local/bin/bash ./xmlto -o man/man1 man xmlto should not be trying to format manual pages during build, and it seems to be lacking command line arguments in your case. Note that xmlto 0.0.25 has been updated in February, so your update has been a long time coming and may require some amount of manual work. However, I do not recall having seen your problem, and the build clusters are not complaining either, so it may be a local problem on your computer (given the many other failing upgrades you have reported), so check: * when using networked file systems, if the server and client clocks are in synch (this is crucial!) * that your disks use native file systems (ufs, zfs, or perhaps ext2fs) rather than underfeatured ones (msdosfs, for instance on an external disk, is insufficient) * that your disks have sufficient free space (including free inodes) * if your clock is erratic (virtual machines are notorious for that, and sometimes broken/aging/overheated/dirty hardware is causing that; check you don't have dust bunnies sitting around in heat sinks and that all extensions cards are properly seated) * if your /usr/ports is completely updated * if there are missed manual updates from /usr/ports/UPDATING * if your system proper is a supported version and not in need of updating If that's all working out, you can try: - make sure that your ports tree is fully updated. In doubt, prepare for a c. 80 MB download and rebuild from scratch: rm -rf /usr/ports /var/db/portsnap/* portsnap fetch extract - fixing the pkg relations with pkgdb -F, possibly pkgdb -FLa - upgrading in proper dependency order - try upgrading your upgrade tool first - force-rebuilding portupgrade databases: pkgdb -fu ; portsdb -fu - upgrading with portupgrade -R xmlto - upgrading with portmaster instead: portmaster --check-depends portmaster -d xmlto-0.0.24 HTH MA ___ 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: mutt 1.5 much slower than mutt 1.4
Am 24.07.2012 19:18, schrieb Anton Shterenlikht: mail/mutt is much slower on my amd64 and ia64 -current boxes after it was updated from 1.4 to 1.5. Each keystroke takes few seconds to act. Below is my mutt 1.5 config: ... Anybody else is seeing this behaviour? Not here™ on amd64 9-stable -- which may have little relevance for 10-current. Any advice? Any chance to figure out what mutt is doing, like with truss or similar? Is debugging turned on; was mutt built WITH_DEBUG=yes? Is the lag CPU-bound (near 100% CPU) and if yes, in system or in user space, or is the lag IO-bound (near 100% wait)? Can you verify the header cache databases, or move them away just for the sake of the experiment? Does it help if you make clean before building world? This has cured strance effects on occasions in -STABLE (RELENG_[6-9]) branches for me. ___ 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: mutt 1.5 much slower than mutt 1.4
strance effects on occasions in -STABLE (RELENG_[6-9]) branches for me. s/strance/strange/ ___ 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
[CFT] LibreOffice on 7.x 8.x
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 As you may know, there are numerous build issues with recent LibreOffice on 7.x and 8.x. I am trying to fix it but it's taking too much time for me, unfortunately. If you are a 7/8 user, please test this: http://people.freebsd.org/~jkim/libreoffice-20120724.tar.bz2 Basically, I am trying to build it with base GCC again for these releases, mainly to avoid huge build/runtime dependencies. In fact, it was successfully built on 7.4 8.2 with amd64 but I don't have environment to perform actual runtime tests for all possible combinations. Please note WITH_GCC knob is back. If base GCC doesn't work for you, please try it as well, i.e., make WITH_GCC=yes. Please make sure to include uname -a output when you report success/failure. Thanks! Jung-uk Kim -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlAPGxcACgkQmlay1b9qnVO7ogCeJuMaoS8E4tNXxtgfDLlyov+H uIsAn1Ezj3g9xuNbnFFxHGU6EWgvGbWh =La0T -END PGP SIGNATURE- ___ 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: mutt 1.5 much slower than mutt 1.4
On Tue, Jul 24, 2012 at 06:18:43PM +0100, Anton Shterenlikht wrote: mail/mutt is much slower on my amd64 and ia64 -current boxes after it was updated from 1.4 to 1.5. Each keystroke takes few seconds to act. Below is my mutt 1.5 config: === The following configuration options are available for mutt-1.5.21: MUTT_ASPELL=off: Enable aspell support MUTT_COMPRESSED_FOLDERS=on: Enable compressed folders MUTT_CYRUS_SASL2=off: Enable SASL2 authentication MUTT_DEBUG=off: Enable debugging capabilities MUTT_FLOCK=off: Enable flock() usage MUTT_GPGME=off: Enable gpgme interface MUTT_GREETING_PATCH=off: Enable greeting MUTT_HTML=on: Enable HTML documentation MUTT_ICONV=on: Enable iconv support MUTT_IDN=off: Enable idn support MUTT_IFDEF_PATCH=off: Enable ifdef feature MUTT_IMAP_HEADER_CACHE=on: Enable imap header cache MUTT_ISPELL=off: Enable ispell support MUTT_LOCALES_FIX=off: Enable locales fix MUTT_MAILBOX_MANPAGES=on: Install mbox.5/mmdf.5 manpages MUTT_MAILDIR_HEADER_CACHE=off: Enable maildir header cache MUTT_MAILDIR_MTIME_PATCH=off: Enable Maildir mtime patch MUTT_MBOX_HOOK_PATCH=off: Enable enhanced mbox-hook MUTT_NCURSES=on: Enable ncurses support MUTT_NCURSES_PORT=off: Use ncurses from port MUTT_NNTP=off: Enable news reader MUTT_PARENT_CHILD_MATCH_PATCH=off: Enable parent/child match MUTT_QUOTE_PATCH=on: Enable extended quoting MUTT_REVERSE_REPLY_PATCH=off: Enable reverse_reply MUTT_SGMLFORMAT=on: Enable sgml support MUTT_SIDEBAR_PATCH=off: Enable sidebar MUTT_SIGNATURE_MENU=off: Enable signature menu MUTT_SLANG=off: Enable slang support MUTT_SMIME_OUTLOOK_COMPAT=on: SMIME outlook compatible MUTT_SMTP=off: Enable SMTP relay support MUTT_TRASH_PATCH=off: Enable trash folder support MUTT_XML=off: Use XML tools for docu === Use 'make config' to modify these settings BUZI# Anybody else is seeing this behaviour? No I can't say that I am. I have been using it since it stepped its way into mail/mutt-devel Any advice? Willing to post your muttrc ? -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ 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 -- - (2^(N-1)) JJH48-ARIN pgpmKwLTEC2l9.pgp Description: PGP signature
