FreeBSD ports which are currently marked broken
As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users of ports that are marked as broken in their Makefiles. In many cases these ports are failing to compile on some subset of the FreeBSD build environments. The most common problem is that recent versions of -CURRENT include gcc4.2, which is much stricter than older versions. The next most common problem is that compiles succeed on the i386 architecture (e.g. the common Intel PC), but fail on one or more of the other architectures due to assumptions about things such as size of various types, byte-alignment issues, and so forth. In occasional cases we see that the same port may have different errors in different build environments. The script that runs on the build cluster uses heuristics to try to 'guess' the error type to help you isolate problems, but it is only a rough guide. One more note: on occasion, there are transient build errors seen on the build farm. Unfortunately, there is not yet any way for this algorithm to tell the difference (humans are much, much better at this kind of thing.) The errors are listed below. In the case where the same problem exists on more than one build environment, the URL points to the latest errorlog for that type. (By 'build environment' here we mean 'combination of 7.x/8.x/9.x/-current with target architecture'.) (Note: the dates are included to help you to gauge whether or not the error still applies to the latest version. The program that generates this report is not yet able to determine this automatically.) portname: accessibility/yasr broken because: fails to build with new utmpx build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=accessibilityportname=yasr portname: audio/gdam broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=gdam portname: audio/hydrogen broken because: does not install build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=hydrogen portname: audio/teamspeak_client broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=teamspeak_client portname: benchmarks/polygraph31 broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=benchmarksportname=polygraph31 portname: cad/meshlab broken because: does not build build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.10.20120628171716/meshlab-1.2.3_2.log (_Jul_16_09:33:26_UTC_2012) overview: http://portsmon.FreeBSD.org/portoverview.py?category=cadportname=meshlab portname: chinese/big5con broken because: fails to build with new utmpx build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=big5con portname: chinese/cxterm broken because: fails to build with new utmpx build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=cxterm portname: chinese/hztty broken because: fails to build with new utmpx build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=hztty portname: comms/hso-kmod broken because: does not build with USB2, please try comms/uhso-kmod instead build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=commsportname=hso-kmod portname: comms/ib-kmod broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=commsportname=ib-kmod portname: comms/uticom broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=commsportname=uticom portname: databases/adstudio broken because: incomplete plist build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=adstudio portname: databases/glom broken because: bad-plist build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=glom portname: databases/gomysql broken because: Does not compile with go1 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=gomysql portname: databases/msql broken because: Broken on FreeBSD 9+ build errors: none. overview:
FreeBSD unmaintained ports which are currently marked broken
As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users of ports that are marked as broken in their Makefiles. In many cases these ports are failing to compile on some subset of the FreeBSD build environments. The most common problem is that recent versions of -CURRENT include gcc4.2, which is much stricter than older versions. The next most common problem is that compiles succeed on the i386 architecture (e.g. the common Intel PC), but fail on one or more of the other architectures due to assumptions about things such as size of various types, byte-alignment issues, and so forth. In occasional cases we see that the same port may have different errors in different build environments. The script that runs on the build cluster uses heuristics to try to 'guess' the error type to help you isolate problems, but it is only a rough guide. One more note: on occasion, there are transient build errors seen on the build farm. Unfortunately, there is not yet any way for this algorithm to tell the difference (humans are much, much better at this kind of thing.) The errors are listed below. In the case where the same problem exists on more than one build environment, the URL points to the latest errorlog for that type. (By 'build environment' here we mean 'combination of 7.x/8.x/9.x/-current with target architecture'.) (Note: the dates are included to help you to gauge whether or not the error still applies to the latest version. The program that generates this report is not yet able to determine this automatically.) portname: audio/teamspeak_client broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=teamspeak_client portname: chinese/big5con broken because: fails to build with new utmpx build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=big5con portname: chinese/hztty broken because: fails to build with new utmpx build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=hztty portname: databases/adstudio broken because: incomplete plist build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=adstudio portname: databases/msql broken because: Broken on FreeBSD 9+ build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=msql portname: databases/xapian-bindings10 broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=xapian-bindings10 portname: deskutils/simpleagenda broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=deskutilsportname=simpleagenda portname: devel/dsss broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=dsss portname: devel/gauche-gaunit broken because: does not package build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=gauche-gaunit portname: devel/gcvs broken because: Does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=gcvs portname: devel/libYGP broken because: Does not build with recent boost build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=libYGP portname: devel/linux-js broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-js portname: devel/linuxthreads broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linuxthreads portname: devel/lua-posix broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=lua-posix portname: devel/lua50-posix broken because: does not build build errors: http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.9.20120820204747/lua50-posix-5.0.log (_Apr__6_15:35:56_UTC_2012) overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=lua50-posix portname: devel/p5-Dialog broken because: Does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=p5-Dialog portname:
FreeBSD ports which are currently marked forbidden
As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users about ports that are marked as forbidden in their Makefiles. Often, these ports are so marked due to security concerns, such as known exploits. An overview of each port, including errors seen on the build farm, is included below. portname: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-tiff portname: lang/eperl forbidden because: Vulnerable since 2001-06-21, http://portaudit.freebsd.org/73efb1b7-07ec-11e2-a391-000c29033c32.html build errors: http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.7.20101015091133/eperl-2.2.14_3.log.bz2 (_Jul_31_06:17:35_UTC_2010) overview: http://portsmon.FreeBSD.org/portoverview.py?category=langportname=eperl portname: security/sudosh3 forbidden because: Secunia Advisory SA38292, ISS X-Force sudosh-replay-bo (55903), replay() function buffer overflow. build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=securityportname=sudosh3 portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkitsportname=linux-pango ___ 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+BRAINSTORM] One USE_ to rule them all
On Thu, Feb 07, 2013 at 09:54:59AM +0100, Alberto Villa wrote: On Thursday 07 February 2013 06:32:54 Armin Pirkovitsch wrote: # find /usr/ports -name Makefile | xargs grep -R FEATURES | wc -l 82 # find /usr/ports -name Makefile | xargs grep -R USES | wc -l 20 Sounds to me like there are less false positives for USES. Add -w and USES wins: $ find /usr/ports -name Makefile | xargs grep -Rw FEATURES | wc -l 37 $ find /usr/ports -name Makefile | xargs grep -Rw USES | wc -l 0 Let's go for USES then! regards, Bapt pgpvVHsW85L1n.pgp Description: PGP signature
Re: CFT: building multimedia/vlc with clang on 9.1+
Op za 19 jan 2013 22:09:03 schreef Juergen Lock: Hi! As having to depend on gcc 4.6+ on i386 is kindof a waste on 9.1+ where we have clang too, and clang might generate better code than the old gcc 4.2.1 in base on amd64 anyway I thought what if we have the vlc port default to using clang on 9.1+ when it's available? So I propse the patch below for testing by anyone on 9.1 or later, also on i386 where I can't test myself, please report any issues or regressions you find. I ran into an issue yesterday with an MKV. The error was: mkv error: cannot find KaxSegment or missing mandatory KaxInfo. Searching this brought me to: http://forum.videolan.org/viewtopic.php?f=13t=98175 Where the answer is: Your g++ is to old, they also provide a workaround patch to mkv.hpp that supposedly exposes a security issue: #define MKV_IS_ID( el, C ) ( EbmlId( (*el) ) == C::ClassInfos.GlobalId ) After some quick testing (all FreeBSD 9.1 RELEASE amd64): clang 3.1 without patching: MKV error clang 3.1 with that patch : OK USE_GCC=4.6 without patch : OK Oliver ___ 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 Port: wbar-2.3.4 upgrade
After upgrading wbar and changing the background icon according to the entry in /usr/ports/UPDATING I'm now getting wbar in the middle of the screen standing vertically even though I use the command wbar -above-desk -bpress -pos bottom -nanim 7 Any suggestions on how I can get it to place itself in the bottom of the screen? Thanks /Leslie ___ 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: LibreOffice 3.6.5 on amd
2013/2/6 Jung-uk Kim j...@freebsd.org: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2013-02-06 11:15:44 -0500, Olivier Smedts wrote: 2013/2/6 Denny Lin dennyli...@hs.ntnu.edu.tw: gmake[2]: *** [/tmp/lobuild/workdir/unxfbsd.pro/CustomTarget/testtools/uno_test.done] Segmentation fault: 11 (core dump cr×™×™) I am also seeing this on -CURRENT amd64. For some reason uno causes a segmentation fault. I do not have Java enabled. Metoo : uno segfault during testtools stage. 10-CURRENT amd64, system and most ports compiled with clang. You can bypass the test with this patch: http://svn.redports.org/office/editors/libreoffice/files/patch-testtools__Module_testtools.mk Drop the file in libreoffice/files directory and rebuild. Actually, I am going to commit it soonish because I've seen enough complaints already. :-( Thanks, libreoffice now builds and runs ! -- Olivier Smedts _ ASCII ribbon campaign ( ) e-mail: oliv...@gid0.org- against HTML email vCards X www: http://www.gid0.org- against proprietary attachments / \ Il y a seulement 10 sortes de gens dans le monde : ceux qui comprennent le binaire, et ceux qui ne le comprennent pas. ___ 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/tcl85 builds fine on ia64, please remove BROKEN=
On 2013-Feb-07, 10:24, Anton Shterenlikht wrote: lang/tcl85 builds fine on ia64, and always had. I don't recall any problem with in all the time I've used ia64, about 4-5 years. Please remove the BROKEN= Thanks a lot, it's done! -- Pietro Cerutti The FreeBSD Project g...@freebsd.org PGP Public Key: http://gahr.ch/pgp pgpf0jvNitWTh.pgp Description: PGP signature
Re: [CFT+BRAINSTORM] One USE_ to rule them all
Date: Thu, 7 Feb 2013 10:52:01 +0100 From: Baptiste Daroussin b...@freebsd.org To: Alberto Villa avi...@freebsd.org Subject: Re: [CFT+BRAINSTORM] One USE_ to rule them all On Thu, Feb 07, 2013 at 09:54:59AM +0100, Alberto Villa wrote: On Thursday 07 February 2013 06:32:54 Armin Pirkovitsch wrote: # find /usr/ports -name Makefile | xargs grep -R FEATURES | wc -l 82 # find /usr/ports -name Makefile | xargs grep -R USES | wc -l 20 =20 Sounds to me like there are less false positives for USES. =20 Add -w and USES wins: $ find /usr/ports -name Makefile | xargs grep -Rw FEATURES | wc -l 37 $ find /usr/ports -name Makefile | xargs grep -Rw USES | wc -l 0 Is -R really needed in this case? I think there is no recursion as you already found all files. Anyway, I get the same answers with no -R. Anton P.S. I'm not trying to be clever, just always fascinated by multi-pipe unix examples, so I try to study those in detail. ___ 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+BRAINSTORM] One USE_ to rule them all
On 2013-02-07 11:36, Anton Shterenlikht wrote: Date: Thu, 7 Feb 2013 10:52:01 +0100 From: Baptiste Daroussin b...@freebsd.org To: Alberto Villa avi...@freebsd.org Subject: Re: [CFT+BRAINSTORM] One USE_ to rule them all On Thu, Feb 07, 2013 at 09:54:59AM +0100, Alberto Villa wrote: On Thursday 07 February 2013 06:32:54 Armin Pirkovitsch wrote: # find /usr/ports -name Makefile | xargs grep -R FEATURES | wc -l 82 # find /usr/ports -name Makefile | xargs grep -R USES | wc -l 20 =20 Sounds to me like there are less false positives for USES. =20 Add -w and USES wins: $ find /usr/ports -name Makefile | xargs grep -Rw FEATURES | wc -l 37 $ find /usr/ports -name Makefile | xargs grep -Rw USES | wc -l 0 Is -R really needed in this case? I think there is no recursion as you already found all files. Anyway, I get the same answers with no -R. You are of course right - i just copied the grep and forgot to remove -R - when you give grep a specific file (which happens in this case) -R has no effect. Armin ___ 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
is it a good idea to overwrite GCC_DEFAULT_VERSION= in Mk/bsd.gcc.mk?
Hi Gerald Right now the default GCC is GCC_DEFAULT_VERSION=4.6 For some time lang/gcc46 doesn't build for me on ia64. However, lang/gcc47 and lang/gcc48 do. There are quite a few ports which I cannot update because they depend on lang/gcc46 via USE_FORTRAN=yes. So I wonder if there are any side effects or unexpected effects if I just change GCC_DEFAULT_VERSION= to e.g. 4.7? I know there are also ways to require a specific GCC version for a specific port via /etc/make.conf, however, this seems tedious. And anyway, 4.7 will be the default soon, right? Please comment ___ 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
2013/2/2 Jason Helfman j...@freebsd.org: [ ] STD_SOCKET Use standard socket for agent ... 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-socket By 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. I'd like to change description for STD_SOCKET option to summerize above if someone suggests better wordings. -- Jun Kuriyama kuriy...@freebsd.org // FreeBSD Project kuriy...@s2factory.co.jp // S2 Factory, Inc. ___ 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
openssh-portable segmentation faults
Would it be possible if someone with a FreeBSD 9.1Stable system built after 2-Feb could build and run openssh-portable. Segmentation faults are occurring with both ssh, and sshd built today on both i386 and amd64 machines. A portsnap was performed and built all ports on 4-Feb. The openssh issue was picked up during pre-deployment testing. We then performed another portsnap, which updated openssl, hence the openssl 1.0.1.d below; it also failed using 1.0.1c. Starting from the default options, each option was turned off, and rebuilt until there was only one option OVERWRITE_BASE=on. Other info: # ldd `which ssh` /usr/bin/ssh: libcrypto.so.8 = /usr/lib/libcrypto.so.8 (0x280bb000) libutil.so.9 = /lib/libutil.so.9 (0x2823d000) libz.so.6 = /lib/libz.so.6 (0x2825) libcrypt.so.5 = /lib/libcrypt.so.5 (0x28264000) libthr.so.3 = /lib/libthr.so.3 (0x28289000) libc.so.7 = /lib/libc.so.7 (0x282a9000) # ll /usr/bin/ssh -rwxr-xr-x 1 root wheel 347136 Feb 7 22:37 /usr/bin/ssh Example: # /usr/bin/ssh -vvv localhost OpenSSH_5.8p2-hpn13v11 FreeBSD-openssh-portable-5.8.p2_3,1, OpenSSL 1.0.1d 5 Feb 2013 Segmentation fault (core dumped) # /usr/sbin/sshd Segmentation fault Regards, Dewayne. ___ 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: openssh-portable segmentation faults
On 2013-02-07 12:59, Dewayne wrote:... Example: # /usr/bin/ssh -vvv localhost OpenSSH_5.8p2-hpn13v11 FreeBSD-openssh-portable-5.8.p2_3,1, OpenSSL 1.0.1d 5 Feb 2013 Segmentation fault (core dumped) # /usr/sbin/sshd Segmentation fault Can you get backtraces for those segfaults, please? Preferably with symbols, e.g. rebuild the port with WITH_DEBUG=x in the environment. ___ 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: openssh-portable segmentation faults
On 2/7/2013 5:59 AM, Dewayne wrote: Would it be possible if someone with a FreeBSD 9.1Stable system built after 2-Feb could build and run openssh-portable. For what it's worth, I am planning to upgrade this very soon to a newer release. I haven't seen these general crashes yet. A debug trace would be great. Segmentation faults are occurring with both ssh, and sshd built today on both i386 and amd64 machines. A portsnap was performed and built all ports on 4-Feb. The openssh issue was picked up during pre-deployment testing. We then performed another portsnap, which updated openssl, hence the openssl 1.0.1.d below; it also failed using 1.0.1c. Starting from the default options, each option was turned off, and rebuilt until there was only one option OVERWRITE_BASE=on. Other info: # ldd `which ssh` /usr/bin/ssh: libcrypto.so.8 = /usr/lib/libcrypto.so.8 (0x280bb000) libutil.so.9 = /lib/libutil.so.9 (0x2823d000) libz.so.6 = /lib/libz.so.6 (0x2825) libcrypt.so.5 = /lib/libcrypt.so.5 (0x28264000) libthr.so.3 = /lib/libthr.so.3 (0x28289000) libc.so.7 = /lib/libc.so.7 (0x282a9000) # ll /usr/bin/ssh -rwxr-xr-x 1 root wheel 347136 Feb 7 22:37 /usr/bin/ssh Example: # /usr/bin/ssh -vvv localhost OpenSSH_5.8p2-hpn13v11 FreeBSD-openssh-portable-5.8.p2_3,1, OpenSSL 1.0.1d 5 Feb 2013 Segmentation fault (core dumped) # /usr/sbin/sshd Segmentation fault Regards, Dewayne. -- Regards, Bryan Drewery bdrewery@freenode/EFNet signature.asc Description: OpenPGP digital signature
Re: portupgrade+pkgng stale dependency - ports/175841 - github issue 44
On 2/5/2013 8:03 PM, Bryan Drewery wrote: Looking into this more I see that there definitely is some bug here either with portupgrade, pkg(8), or the integration of the two. I will update ports@ and https://github.com/pkgtools/pkgtools/issues/44 when I have more details or a fix. portupgrade -O should work around this issue. I am working on an update that should avoid these issues. Should be done today or tomorrow. -- Regards, Bryan Drewery bdrewery@freenode/EFNet signature.asc Description: OpenPGP digital signature
LibreOffice and OpenJDK
Am I correct in believing LibreOffice(-3.6.5) will build with OpenJDK-6, but not OpenJDK-7? Respectfully, Robert Huff ___ 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: ports-mgmt/portupgrade ISSUE portinstall recursive dependency error
Thank you for support. On a fresh 9.1-REL compiled with GCC 4.2.1 it works fine. But on mixed (GCC 4.2.1, but 4.6.3 whereever possible) 9.0-REL the problem persists still. Looks like portinstall itself, or ruby/ruby-bdb might or whatever direct siblings deviate under GCC 4.6.3 compilation, likewise java/icedtea-web does with Opera. Tried total removal of portupgrade, ruby and databases/ruby-bdb, /usr/ports/indexes and pkgdb.db ... total clean-up - without success. Could you advise any special files that might need removal used by portinstall, except /var/db/pkg/pkgdb.db? Which may affect double counting of dependancies, like in the case mentioned above?: [Gathering depends for security/vuxml .(devel/binutils)...(devel/binutils)--- Session ended at: Looks like it builds /var/db/pkg/pkgdb.db in some inproper way... Have you tried to compile the whole bunch with gcc 4.6.3? Was it successful? Looks like it stucks inside the bdb-creation/processing step: # rm -f /var/db/pkg/pkgdb.db # pkgdb -uf --- Updating the pkgdb [Rebuilding the pkgdb format:bdb_btree in /var/db/pkg ... - 1094 packages found (-0 +1094) 100200300400500600700800900... .1000.. done] # portupgrade -Nvprn security/vuxml --- Session started at: Thu, 07 Feb 2013 21:33:21 +0400 [Updating the portsdb format:bdb_btree in /usr/ports ... - 24165 port entries found .1000.2000.3000.4000.5000.6000.7000.8000.9000.1.11000.12000.13000.14000.15000.16000.17000.18000.19000.2.21000.22000.23000.24000. . done] Install 'security/vuxml'? [no] [Gathering depends for security/vuxml .(textproc/xmlcatmgr)..(devel/binutils)...(devel/binutils)--- Session ended at: Thu, 07 Feb 2013 21:34:31 +0400 (consumed 00:01:10) /usr/local/sbin/portupgrade:898:in `get_all_depends': recursive dependency (RecursiveDependencyError) from /usr/local/sbin/portupgrade:921:in `get_all_depends' from /usr/local/lib/ruby/1.8/set.rb:195:in `each' from /usr/local/lib/ruby/1.8/set.rb:195:in `each_key' from /usr/local/lib/ruby/1.8/set.rb:195:in `each' from /usr/local/sbin/portupgrade:920:in `get_all_depends' from /usr/local/sbin/portupgrade:921:in `get_all_depends' from /usr/local/lib/ruby/1.8/set.rb:195:in `each' from /usr/local/lib/ruby/1.8/set.rb:195:in `each_key' from /usr/local/lib/ruby/1.8/set.rb:195:in `each' from /usr/local/sbin/portupgrade:920:in `get_all_depends' from /usr/local/sbin/portupgrade:921:in `get_all_depends' from /usr/local/lib/ruby/1.8/set.rb:195:in `each' from /usr/local/lib/ruby/1.8/set.rb:195:in `each_key' from /usr/local/lib/ruby/1.8/set.rb:195:in `each' from /usr/local/sbin/portupgrade:920:in `get_all_depends' from /usr/local/sbin/portupgrade:937:in `get_notinstalled_depends' from /usr/local/sbin/portupgrade:813:in `main' from /usr/local/sbin/portupgrade:791:in `each' from /usr/local/sbin/portupgrade:791:in `main' from /usr/local/lib/ruby/1.8/optparse.rb:1310:in `call' from /usr/local/lib/ruby/1.8/optparse.rb:1310:in `parse_in_order' from /usr/local/lib/ruby/1.8/optparse.rb:1306:in `catch' from /usr/local/lib/ruby/1.8/optparse.rb:1306:in `parse_in_order' from /usr/local/lib/ruby/1.8/optparse.rb:1254:in `catch' from /usr/local/lib/ruby/1.8/optparse.rb:1254:in `parse_in_order' from /usr/local/lib/ruby/1.8/optparse.rb:1248:in `order!' from /usr/local/lib/ruby/1.8/optparse.rb:1241:in `order' from /usr/local/sbin/portupgrade:576:in `main' from /usr/local/lib/ruby/1.8/optparse.rb:791:in `initialize' from /usr/local/sbin/portupgrade:237:in `new' from /usr/local/sbin/portupgrade:237:in `main' from /usr/local/sbin/portupgrade:2371 2013/2/6 Bryan Drewery bdrew...@freebsd.org: On 1/5/2013 9:38 AM, awarecons wrote: # $FreeBSD: ports/ports-mgmt/portupgrade/Makefile,v 1.285 2012/12/11
Re: LibreOffice and OpenJDK
On Thu, Feb 07, 2013 at 11:21:59AM -0500, Robert Huff wrote: Am I correct in believing LibreOffice(-3.6.5) will build with OpenJDK-6, but not OpenJDK-7? Yes upstream do not support openjdk7 yet iirc regards, Bapt pgpBuaLr2l9B8.pgp Description: PGP signature
Updating KDE
I just updated to KDE Version 4.9.5 as described in the UPDATING file. KDE starts; however, all of my desktop icon and shortcuts are gone. What could have happened to them? Also, the ALT TAB key combination no longer functions. -- 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
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 +-+ editors/ted | 2.22| 2.23 +-+ 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
Re: openssh-portable segmentation faults
On 2013-02-07 22:14, Dewayne Geraghty wrote:
...
Bryan, Dimitry,
Thank-you for your interest.
Unfortunately we have no debugging tools on any of the machines. I'll build one
today and reproduce.
I have reproduced the segfault here:
Starting program: /usr/ports/security/openssh-portable/work/openssh-5.8p2/ssh
-vvv localhost
OpenSSH_5.8p2 FreeBSD-openssh-portable-5.8.p2_3,1, OpenSSL 1.0.1c 10 May 2012
Program received signal SIGSEGV, Segmentation fault.
istrsnvis (dst=0xbfbfb8f4 debug1: Reading configuration data %.200s, dlen=0xbfbfb880,
csrc=optimized out, flag=33, extra=optimized out) at
/usr/src/contrib/libc-vis/vis.c:380
380 for (start = dst; (c = *src++) != '\0'; /* empty */) {
(gdb) bt
#0 istrsnvis (dst=0xbfbfb8f4 debug1: Reading configuration data %.200s,
dlen=0xbfbfb880, csrc=optimized out, flag=33, extra=optimized out) at
/usr/src/contrib/libc-vis/vis.c:380
#1 0x28360cfd in istrnvis (dst=0xbfbfb8f4 debug1: Reading configuration data
%.200s, dlen=0xbfbfb880, src=optimized out, flag=-1077954316) at
/usr/src/contrib/libc-vis/vis.c:534
#2 0x28360d71 in strnvis (dst=0xbfbfb878 , dlen=3217014004, src=0xbfbfb878
, flag=-1077954440) at /usr/src/contrib/libc-vis/vis.c:548
#3 0x08082e5d in do_log (level=SYSLOG_LEVEL_DEBUG1, fmt=0x80a914e Reading configuration
data %.200s, args=0xbfbfc134 $\321\277\277@) at log.c:384
#4 0x08083048 in debug (fmt=0x80a914e Reading configuration data %.200s)
at log.c:209
#5 0x08054c8e in read_config_file (filename=0xbfbfd124 /home/dim/.ssh/config,
host=0xbfbfd770 localhost, options=0x80b99dc options, checkperm=1) at readconf.c:1051
#6 0x0804e542 in main (ac=0, av=0xbfbfd5c0) at ssh.c:670
This is exactly the same problem as reported in this thread about
the security/pam_ssh_agent_auth port (rather long, beware):
http://lists.freebsd.org/pipermail/freebsd-stable/2013-January/071703.html
Executive summary: we recently imported a strnvis() implementation from
NetBSD, which has differently ordered arguments from the strnvis()
implementation in OpenBSD. When OpenSSH calls it with arguments ordered
in the way OpenBSD expects, the function segfaults.
I guess a similar approach as take in the above thread should be taken,
e.g. rename the function in the port to openbsd_strnvis(), and have the
port call that. Or use macro trickery to swap the arguments... :)
___
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: openssh-portable segmentation faults
On Fri, Feb 08, 2013 at 12:16:40AM +0100, Dimitry Andric wrote: This is exactly the same problem as reported in this thread about the security/pam_ssh_agent_auth port (rather long, beware): http://lists.freebsd.org/pipermail/freebsd-stable/2013-January/071703.html Executive summary: we recently imported a strnvis() implementation from NetBSD, which has differently ordered arguments from the strnvis() implementation in OpenBSD. When OpenSSH calls it with arguments ordered in the way OpenBSD expects, the function segfaults. I guess a similar approach as take in the above thread should be taken, e.g. rename the function in the port to openbsd_strnvis(), and have the port call that. Or use macro trickery to swap the arguments... :) I suggest taking a reverse approach, and rename our libc function to e.g. NetBSD_strnvis(). This way, at least linking binaries would result in the build-time failure. For shared libraries, we also get some semi-helpful message from rtld which would allow to identify the problem without obtaining the backtrace. Anyway, the porter will see the issue cleanly. This should be done before merging the libc changes to stable. pgpu2SEEYuAEo.pgp Description: PGP signature
Re: openssh-portable segmentation faults
On 2/7/2013 5:16 PM, Dimitry Andric wrote:
On 2013-02-07 22:14, Dewayne Geraghty wrote:
...
Bryan, Dimitry,
Thank-you for your interest.
Unfortunately we have no debugging tools on any of the machines. I'll
build one today and reproduce.
I have reproduced the segfault here:
Starting program:
/usr/ports/security/openssh-portable/work/openssh-5.8p2/ssh -vvv localhost
OpenSSH_5.8p2 FreeBSD-openssh-portable-5.8.p2_3,1, OpenSSL 1.0.1c 10
May 2012
Program received signal SIGSEGV, Segmentation fault.
istrsnvis (dst=0xbfbfb8f4 debug1: Reading configuration data %.200s,
dlen=0xbfbfb880, csrc=optimized out, flag=33, extra=optimized out)
at /usr/src/contrib/libc-vis/vis.c:380
380 for (start = dst; (c = *src++) != '\0'; /* empty */) {
(gdb) bt
#0 istrsnvis (dst=0xbfbfb8f4 debug1: Reading configuration data
%.200s, dlen=0xbfbfb880, csrc=optimized out, flag=33,
extra=optimized out) at /usr/src/contrib/libc-vis/vis.c:380
#1 0x28360cfd in istrnvis (dst=0xbfbfb8f4 debug1: Reading
configuration data %.200s, dlen=0xbfbfb880, src=optimized out,
flag=-1077954316) at /usr/src/contrib/libc-vis/vis.c:534
#2 0x28360d71 in strnvis (dst=0xbfbfb878 , dlen=3217014004,
src=0xbfbfb878 , flag=-1077954440) at /usr/src/contrib/libc-vis/vis.c:548
#3 0x08082e5d in do_log (level=SYSLOG_LEVEL_DEBUG1, fmt=0x80a914e
Reading configuration data %.200s, args=0xbfbfc134 $\321\277\277@)
at log.c:384
#4 0x08083048 in debug (fmt=0x80a914e Reading configuration data
%.200s) at log.c:209
#5 0x08054c8e in read_config_file (filename=0xbfbfd124
/home/dim/.ssh/config, host=0xbfbfd770 localhost, options=0x80b99dc
options, checkperm=1) at readconf.c:1051
#6 0x0804e542 in main (ac=0, av=0xbfbfd5c0) at ssh.c:670
This is exactly the same problem as reported in this thread about
the security/pam_ssh_agent_auth port (rather long, beware):
http://lists.freebsd.org/pipermail/freebsd-stable/2013-January/071703.html
Executive summary: we recently imported a strnvis() implementation from
NetBSD, which has differently ordered arguments from the strnvis()
implementation in OpenBSD. When OpenSSH calls it with arguments ordered
in the way OpenBSD expects, the function segfaults.
I guess a similar approach as take in the above thread should be taken,
e.g. rename the function in the port to openbsd_strnvis(), and have the
port call that. Or use macro trickery to swap the arguments... :)
Aha, thanks. I see this is logged at netbsd here
http://gnats.netbsd.org/44977 as well.
I will write up a patch.
--
Regards,
Bryan Drewery
bdrewery@freenode/EFNet
signature.asc
Description: OpenPGP digital signature
Re: openssh-portable segmentation faults
On 2/7/2013 5:50 PM, Dimitry Andric wrote: On 2013-02-08 00:16, Dimitry Andric wrote: On 2013-02-07 22:14, Dewayne Geraghty wrote: ... Bryan, Dimitry, Thank-you for your interest. Unfortunately we have no debugging tools on any of the machines. I'll build one today and reproduce. ... Executive summary: we recently imported a strnvis() implementation from NetBSD, which has differently ordered arguments from the strnvis() implementation in OpenBSD. When OpenSSH calls it with arguments ordered in the way OpenBSD expects, the function segfaults. And here is a patch, which works for me. It simply disables use of libc's strnvis(), forcing the port to use its own bundled version. Perfect thanks. This was the approach I was going to take as well, since it has a bundled compatibility version already. Fix Committed. -- Regards, Bryan Drewery bdrewery@freenode/EFNet signature.asc Description: OpenPGP digital signature
FreeBSD Port: pdftk-1.44_1
Just wondering if this port will be updated to 1.45 anytime soon? I need a feature added in 1.45 and I am to computer illiterate to update the port myself. Thanks Mazsola ___ 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: pdftk-1.44_1
This has already been updated to 1.45. -jgh -- Jason Helfman | FreeBSD Committer j...@freebsd.org | http://people.freebsd.org/~jgh | The Power to Serve On Thu, Feb 7, 2013 at 7:32 PM, Mazsola mazs...@gmail.com wrote: Just wondering if this port will be updated to 1.45 anytime soon? I need a feature added in 1.45 and I am to computer illiterate to update the port myself. Thanks Mazsola __**_ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/**mailman/listinfo/freebsd-portshttp://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscribe@**freebsd.orgfreebsd-ports-unsubscr...@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: Updating KDE
Jerry je...@seibercom.net wrote: I just updated to KDE Version 4.9.5 as described in the UPDATING file. KDE starts; however, all of my desktop icon and shortcuts are gone. What could have happened to them? Also, the ALT TAB key combination no longer functions. My stuff: Icon are there - fine so far. Background image is there. Fino so far, but.. Virtual desktops eare not accessable by ctrl + F1 / F2 / F3 / F4 My K-panel has an unreadable font - with a strange 3d look. It ist black/gray on black By The Way, you should install kdemultimedia4 und kde4-runtime (and maybe kde4-network) by hand after update like UPDATING says Heino ___ 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
