Re: How to change docdir in port Makefile?
I found that line in Makefile.in. Thank you!
B.R.
HU Dong
On Tue, Aug 7, 2012 at 1:37 PM, Jason Helfman j...@freebsd.org wrote:
On Mon, Aug 6, 2012 at 8:36 PM, HU Dong itechb...@gmail.com wrote:
Hi, all. I'm making a new port. It uses GNU configure to generate a
GNU Makefile. But it set DOCSDIR to
${PREFIX}/share/doc/${PORTNAME}-${PORTVERSION} instead
of ${PREFIX}/share/doc/${PORTNAME}:
***
docdir = $(prefix)/share/doc/$(PACKAGE)-$(VERSION)
***
I've tried post-patch, but it didn't help, cause post-patch phase is
earlier than the time when GNU Makefile is generated. So how to modify the
GNU Makefile to correct this problem?
B.R.
HU Dong
If it is generated from, I assume a Makefile.in, or similar file, try
patching that file. Then your change
should follow. I had to take this approach for deskutils/virt-manager
recently for NLS location
change.
Hope this helps.
-jgh
--
Jason Helfman | FreeBSD Committer
j...@freebsd.org | http://people.freebsd.org/~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
New port: devel/streamhtmlparser
Hello, everyone! I've made a new port: devel/streamhtmlparser. It's a C/C++/Python streaming HTML parser library from Google( http://code.google.com/p/streamhtmlparser/). Currently I've finished it and made it work on my box. I put the files on redports.org: http://svn.redports.org/Lion/devel/streamhtmlparser/ . I hope someone could spend time reviewing the files in case there's something wrong. B.R. HU Dong ___ 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
graphics/rawtherapee
Hi, is it possible to push graphics/rawtherapee to version 4.0.9.50? On the last weekend I talked to a develoer of rawtherapee and he told me about some new noise reduction algorythyms... ...and he told me, the the developers often don't like it, to make a new major, so it is often a lot(!) new stuff in the change of some minor version steps.. so.. 4.0.9.1 is totaly diferent to 4.0.9.15, which is totaly different to 4.0.9.50, etc... Is ist possible? sincerely yours 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
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: cad/feappv broken because: size mismatch build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.7.20120805102317/feappv-3.1.log (_Aug__6_16:25:29_UTC_2012) overview: http://portsmon.FreeBSD.org/portoverview.py?category=cadportname=feappv 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/grass broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=grass 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: http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.8.20120517001625/xapian-bindings10-1.0.23.log (_May_26_19:25:59_UTC_2012) overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=xapian-bindings10 portname: deskutils/simpleagenda broken because: does not build build errors: http://pointyhat.FreeBSD.org/errorlogs/i386-errorlogs/e.8.20120730062936/simpleagenda-0.42.log (_Jul_31_05:33:40_UTC_2012) 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 compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=gcvs 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:
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/feappv broken because: size mismatch build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.7.20120805102317/feappv-3.1.log (_Aug__6_16:25:29_UTC_2012) overview: http://portsmon.FreeBSD.org/portoverview.py?category=cadportname=feappv portname: cad/meshlab broken because: does not build build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.8.20120725160355/meshlab-1.3.0.log (_Jul_26_16:24:10_UTC_2012) http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.10.20120608131052/meshlab-1.2.3_2.log (_Jun__9_15:51:34_UTC_2012) overview: http://portsmon.FreeBSD.org/portoverview.py?category=cadportname=meshlab portname: cad/salome-gui broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=cadportname=salome-gui 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:
FreeBSD unmaintained ports which are currently scheduled for deletion
As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on the existing port. In some cases, ports are marked for removal because they fail to build and install correctly from their sources, or otherwise fail in operation. The ports, and the reason and date that they have been scheduled for removal, are listed below. If no one has stepped forward before that time to propose a way to fix the problems (such as via a PR), the ports will be deleted. portname: archivers/bsdar description:BSD-licensed replacement of the ar utility maintainer: po...@freebsd.org status: IGNORE deprecated because: part of the base system expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=archiversportname=bsdar portname: audio/linux-alsa-lib description:The Advanced Linux Sound Architecture libraries maintainer: po...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-alsa-lib portname: audio/linux-arts description:Audio system for the KDE integrated X11 desktop (Linux version) maintainer: po...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-arts portname: audio/linux-freealut description:A free implementation of OpenAL's ALUT standard (Linux version) maintainer: po...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-freealut portname: audio/linux-libmad description:Libmad library (part of MAD project) maintainer: po...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-libmad portname: audio/linux-libogg description:Ogg bitstream library (Linux version) maintainer: po...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-libogg portname: audio/linux-libvorbis description:Audio compression codec library (Linux version) maintainer: po...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-libvorbis portname: audio/linux-openal description:A 3D positional spatialized sound library (Linux version) maintainer: po...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-openal portname: databases/libudbc description:Openlink UDBC SDK maintainer: po...@freebsd.org deprecated because: Does not fetch and no vendor support anymore expiration date:2012-08-12 build errors: http://pointyhat.FreeBSD.org/errorlogs/i386-errorlogs/e.8.20120806122801/libudbc-4.1.log (_Aug__6_14:02:05_UTC_2012) overview: http://portsmon.FreeBSD.org/portoverview.py?category=databasesportname=libudbc portname: devel/libgetline description:A small, portable, and easy to use command line library maintainer: po...@freebsd.org deprecated because: Upstream disapear and distfile is no more available expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=libgetline portname: graphics/linux-cairo description:Linux cairo binary maintainer: po...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-cairo portname: graphics/linux-gdk-pixbuf description:Linux version of the graphic library for GTK+ maintainer: po...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-gdk-pixbuf portname: java/sun-wtk description:Sun J2ME Wireless Toolkit
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: www/linux-f10-flashplugin10 forbidden because: insecure version - use flashplugin11 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=wwwportname=linux-f10-flashplugin10 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
pkg and portmaster: Downgrading ports? Why? portmaster messes up ...
Hello. I tried to switch to the new tool pkg. I'm still installing my ports via sources and compiling, but I appreciate the more stable dependency tracking of pkg(ng). Therefore, I patched, as reuqired and recommended, ports-mgmt/portmaster. I performed a portmaster --check-depends after I got several warnings and two very confusing (if not scaring) exclsuions and therefore rejections: graphics/libGL and x11/nvidia-driver (which is in my case 304.32 and works pretty well so far!), x11-server/xorg-server. They all install, so the compalin of pkg/portmaster, files in the very same place. So I'm stuck and I do not know, whether my ports collection is now corrupted by this stubborn behaviour or not. Mor scaring, performing a portmaster --check-depends ends up in this: Missing package dependencies were detected. Found 2 issue(s) in total with your package database. The following packages will be installed: Installing pkg-config: 0.25_1 Downgrading pciids: 20120711 - 20120625 Downgrading libdrm: 2.4.31_1 - 2.4.17_1 Installing libGL: 7.6.1 Installing perl: 5.14.2_2 Downgrading dbus: 1.4.14_3 - 1.4.14_2 Downgrading dri: 7.11.2_1,2 - 7.6.1,2 Downgrading pcre: 8.31 - 8.30_2 Downgrading python27: 2.7.3_3 - 2.7.3_2 Installing xorg-server: 1.7.7_5,1 The installation will require 40 MB more space 28 MB to be downloaded Before I made the update towards pkg via pkg2ng, I updated everything with portmaster as it worked in the old-fashion before. I have set properly the knob WITH_NEW_X11 in /etc/make.conf. Now this new toolset tries to donwgrade some of the ports - why? What happens here? ports-mgmt/portmaster installs still the old fashioned style folders of ports in /var/db/pkg. I thought ith the new scheme of pkg, everything is going into a file based SQLite3 DB? With each kernel update, I also need to update x11/nvidia-driver. I do this by /etc/src.conf setting PORTS_MODULES= x11/nvidia-driver PORTS_MODULES+= emulators/virtualbox-ose-kmod The nvidia driver now fails. How can I circumvent this nasty problem? Is there a brute force knob. Will ports-mgmt/portupgrade-devel heal those problems? My OS is a most recent FBSD 10.0-CURRENT. Regards, Oliver signature.asc Description: OpenPGP digital signature
FreeBSD Port: proftpd-1.3.4b vs. mod_clamav
Hello, sorry for my english. I have read on the internet that for proftpd is: Closed-Date:Sat Aug 04 06:55:43 UTC 2012 Last-Modified: Sat Aug 04 06:55:43 UTC 2012 Originator: Sergey Rogoza mod_clamav has been disabled for now. mod_clamav in the future will be supported? Thanks for reply. -- LuMaX ___ 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: pkg and portmaster: Downgrading ports? Why? portmaster messes up ...
On 8/7/2012 4:31 AM, O. Hartmann wrote: Hello. I tried to switch to the new tool pkg. I'm still installing my ports via sources and compiling, but I appreciate the more stable dependency tracking of pkg(ng). Therefore, I patched, as reuqired and recommended, ports-mgmt/portmaster. I performed a portmaster --check-depends after I got several warnings and two very confusing (if not scaring) exclsuions and therefore rejections: graphics/libGL and x11/nvidia-driver (which is in my case 304.32 and works pretty well so far!), x11-server/xorg-server. They all install, so the compalin of pkg/portmaster, files in the very same place. So I'm stuck and I do not know, whether my ports collection is now corrupted by this stubborn behaviour or not. Mor scaring, performing a portmaster --check-depends ends up in this: Missing package dependencies were detected. Found 2 issue(s) in total with your package database. The following packages will be installed: Installing pkg-config: 0.25_1 Downgrading pciids: 20120711 - 20120625 Downgrading libdrm: 2.4.31_1 - 2.4.17_1 Installing libGL: 7.6.1 Installing perl: 5.14.2_2 Downgrading dbus: 1.4.14_3 - 1.4.14_2 Downgrading dri: 7.11.2_1,2 - 7.6.1,2 Downgrading pcre: 8.31 - 8.30_2 Downgrading python27: 2.7.3_3 - 2.7.3_2 Installing xorg-server: 1.7.7_5,1 The installation will require 40 MB more space 28 MB to be downloaded Before I made the update towards pkg via pkg2ng, I updated everything with portmaster as it worked in the old-fashion before. I have set properly the knob WITH_NEW_X11 in /etc/make.conf. Now this new toolset tries to donwgrade some of the ports - why? What happens here? There's some discrepancy between your installed packages, ports, and possibly a remote repository. portmaster --check-depends must not be properly implemented with pkgng. It's trying to use the remote repository to fix the problems it sees instead of the local PORTS tree. The remote is outdated, so it's also trying to downgrade packages. I would not use --check-depends for now. Just manually portmaster port every port that's missing. ports-mgmt/portmaster installs still the old fashioned style folders of ports in /var/db/pkg. I thought ith the new scheme of pkg, everything is going into a file based SQLite3 DB? The portmaster patch is only storing distfile information. The actual pkg db is only using the SQLite3 pkgng db. With each kernel update, I also need to update x11/nvidia-driver. I do this by /etc/src.conf setting PORTS_MODULES= x11/nvidia-driver PORTS_MODULES+= emulators/virtualbox-ose-kmod The nvidia driver now fails. How can I circumvent this nasty problem? Is there a brute force knob. Will ports-mgmt/portupgrade-devel heal those problems? The main problem I see is with --check-depends. This looks to the be equivalent of 'pkgdb -F'. Currently 'pkgdb -F' is not implemented in portupgrade-devel for pkgng support. So it won't help. My OS is a most recent FBSD 10.0-CURRENT. Regards, Oliver -- Regards, Bryan Drewery bdrewery@freenode/EFNet ___ 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: pkg and portmaster: Downgrading ports? Why? portmaster messes up ...
On 8/7/2012 4:31 AM, O. Hartmann wrote: ports-mgmt/portmaster installs still the old fashioned style folders of ports in /var/db/pkg. I thought ith the new scheme of pkg, everything is going into a file based SQLite3 DB? Also ensure WITH_PKGNG=yes is in your /etc/make.conf. My last comment still stands though, portmaster will store distifile information in /var/db/pkg. -- Regards, Bryan Drewery bdrewery@freenode/EFNet ___ 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 ports that you maintain which are currently marked broken
All, I no longer use rsyslog at $work. Are there any interested maintainers and its 3 dependencies. Note, you'll want to be familiar with C to debug core dumps and svn cp/svn mv to keep up with the release strategy. devel/libee devel/libestr devel/librelp sysutils/rsyslog5 sysutils/rsyslog5-dbi sysutils/rsyslog5-gnutls sysutils/rsyslog5-gssapi sysutils/rsyslog5-mysql sysutils/rsyslog5-pgsql sysutils/rsyslog5-relp sysutils/rsyslog5-rfc3195 sysutils/rsyslog5-snmp sysutils/rsyslog6-devel sysutils/rsyslog6-devel-dbi sysutils/rsyslog6-devel-gnutls sysutils/rsyslog6-devel-gssapi sysutils/rsyslog6-devel-mysql sysutils/rsyslog6-devel-pgsql sysutils/rsyslog6-devel-relp sysutils/rsyslog6-devel-rfc3195 sysutils/rsyslog6-devel-snmp On Tue, Aug 7, 2012 at 8:28 AM, lini...@freebsd.org wrote: Dear FreeBSD port maintainer: 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: sysutils/rsyslog5-snmp broken because: Does not link on i386: can't find symbol snmp_timeout in libnetsnmp build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=sysutilsportname=rsyslog5-snmp portname: sysutils/rsyslog6-devel-snmp broken because: Does not link on i386: can't find symbol snmp_timeout in libnetsnmp build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=sysutilsportname=rsyslog6-devel-snmp If these errors are ones that you are already aware of, please accept our apologies and ignore this message. On the other hand, if you no longer wish to maintain this port (or ports), please reply with a message stating that, and accept our thanks for your efforts in the past. Every effort has been made to make sure that these error reports really do correspond to a port that you maintain. However, due to the fact that this is an automated process, it may indeed generate false matches. If one of these errors fits that description, please forward this email to the author of this software, Mark Linimon lini...@freebsd.org, so that he can attempt to fix the problem in the future. Thanks for your efforts to help improve FreeBSD. -- - 1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70 3F8C 75B8 8FFB DB9B 8C1C Philip M. Gollucci (pgollu...@p6m7g8.com) c: 703.336.9354 Member, Apache Software Foundation Committer,FreeBSD Foundation Consultant, P6M7G8 Inc. Director Operations, Ridecharge Inc. Work like you don't need the money, love like you'll never get hurt, and dance like nobody's watching. ___ 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: pkg and portmaster: Downgrading ports? Why? portmaster messes up ...
On 08/07/12 15:39, Bryan Drewery wrote: On 8/7/2012 4:31 AM, O. Hartmann wrote: ports-mgmt/portmaster installs still the old fashioned style folders of ports in /var/db/pkg. I thought ith the new scheme of pkg, everything is going into a file based SQLite3 DB? Also ensure WITH_PKGNG=yes is in your /etc/make.conf. My last comment still stands though, portmaster will store distifile information in /var/db/pkg. WITH_PKGNG=yes is set in /etc/make.conf. signature.asc Description: OpenPGP digital signature
Re: [CFT] editors/emacs to 24.1
On Mon, 6 Aug 2012 11:23:14 +0200 (CEST), Marco Beishuizen mb...@xs4all.nl said: On Sun, 5 Aug 2012, the wise Ashish SHUKLA wrote: % gdb $(which emacs) (gdb) core-file emacs.core (gdb) bt full Hi Marco, Could you provide output of those () ? Output of this is: (gdb) core /var/coredumps/emacs.core Core was generated by `emacs'. [...] (gdb) bt full #0 0x29507cc7 in kill () from /lib/libc.so.7 No symbol table info available. #1 0x08184033 in fatal_error_signal (sig=11) at emacs.c:366 No locals. #2 0x292179fc in pthread_sigmask () from /lib/libthr.so.3 No symbol table info available. #3 0x29217acf in pthread_sigmask () from /lib/libthr.so.3 No symbol table info available. #4 signal handler called No symbol table info available. #5 0x in ?? () No symbol table info available. Hi Marco, The backtrace you posted doesn't reveal much. And since, I'm not able to reproduce it, it's hard for me to troubleshoot. I suggest posting this to emacs-devel[1] list, or filing a bug report with Emacs[2]. If it resolves for you with some diff, feel free to mention to me. References: [1] https://lists.gnu.org/mailman/listinfo/emacs-devel/ [2] http://debbugs.gnu.org/db/pa/lemacs.html HTH -- Ashish SHUKLA | GPG: F682 CDCC 39DC 0FEA E116 20B6 C746 CFA9 E74F A4B0 Sent from my Emacs pgpnW6Li45zn4.pgp Description: PGP signature
Re: [CFT] editors/emacs to 24.1
On Tue, 7 Aug 2012, the wise Ashish SHUKLA wrote: Hi Marco, The backtrace you posted doesn't reveal much. And since, I'm not able to reproduce it, it's hard for me to troubleshoot. I suggest posting this to emacs-devel[1] list, or filing a bug report with Emacs[2]. If it resolves for you with some diff, feel free to mention to me. References: [1] https://lists.gnu.org/mailman/listinfo/emacs-devel/ [2] http://debbugs.gnu.org/db/pa/lemacs.html HTH Hi Ashish, Well it seems it had something to do with the FreeBSD base system. I use stable (problems) and you use release (no problem) so I just upgraded to a newer system. And guess what? Until now problem solved! So fingers crossed, and hoping it stays ok. Thanks for all the help! Regards, Marco -- The Angels want to wear my red shoes. -- E. Costello ___ 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
On Tue, 7 Aug 2012 19:06:27 +0200 (CEST), Marco Beishuizen mb...@xs4all.nl said: On Tue, 7 Aug 2012, the wise Ashish SHUKLA wrote: Hi Marco, The backtrace you posted doesn't reveal much. And since, I'm not able to reproduce it, it's hard for me to troubleshoot. I suggest posting this to emacs-devel[1] list, or filing a bug report with Emacs[2]. If it resolves for you with some diff, feel free to mention to me. References: [1] https://lists.gnu.org/mailman/listinfo/emacs-devel/ [2] http://debbugs.gnu.org/db/pa/lemacs.html HTH Hi Ashish, Well it seems it had something to do with the FreeBSD base system. I use stable (problems) and you use release (no problem) so I just upgraded to a newer system. And guess what? Until now problem solved! So fingers crossed, and hoping it stays ok. newer system? 10-CURRENT, or 9.1-PRERELEASE? Thanks for all the help! You're welcome. -- Ashish SHUKLA | GPG: F682 CDCC 39DC 0FEA E116 20B6 C746 CFA9 E74F A4B0 Sent from my Emacs pgpKP6rYBfOis.pgp Description: PGP signature
Re: [CFT] editors/emacs to 24.1
On Tue, 7 Aug 2012, the wise Ashish SHUKLA wrote: newer system? 10-CURRENT, or 9.1-PRERELEASE? I follow 9-STABLE which now is called 9.1-PRERELEASE. Marco -- QOTD: Flash! Flash! I love you! ...but we only have fourteen hours to save the earth! ___ 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: Questions about/issues with new OPTIONS framework
On 2012-08-06 18:04, Jeremy Chadwick wrote:
(Please keep me CC'd, as I'm not subscribed to the list)
I've been trying to adapt my /etc/make.conf to make use of the new
OPTIONS framework. I've run into some snags that I was hoping someone
could help me with, as I'm unable to find any official documentation
other than these two documents, which don't help me in this case:
http://wiki.freebsd.org/Ports/Options/OptionsNG
http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/makefile-options.html
Below are my questions so far. Note that these questions are all
preceded by a key fact: /var/db/ports/* is completely empty. Keep that
in mind please.
1. databases/mysql55-server and databases/mysql55-client both ask for
the same variables (OPENSSL and FASTMTX). I want FASTMTX to be enabled
by default for both ports.
When I have the following in /etc/make.conf:
mysql_SET=FASTMTX
Doing make config in databases/mysql55-server shows FASTMTX as checked
(which is correct). However, when I do the exact same procedure in
databases/mysql55-client, FASTMTX is not checked.
I am aware that databases/mysql55-client is a slave port, but I'm not
sure how/why that would matter...?
What am I doing wrong, or is this a port bug which needs to be fixed by
the maintainer?
2. ports/KNOBS is very explicit in stating, and even visually
...
2) alredy answerd ...
answer for question 1)
$ cd mysql55-client make -V UNIQUENAME
or
$ make -V UNIQUENAME -C /usr/ports/databases/mysql55-client/
mysql55-client
make.conf entry constructed from UNIQUENAME
mysql55-client_SET+= FASTMTX
Please note the '+=' instead '='.
If you have a port where you set more then on option but not as one expression
all ${UNIQUENAME}_SET+= are applied else only the last entry in make.conf.
Additional if you have done `make config' already, then your make.conf entry
is useless since with options NG the OPTIONSFILE has now a higher priority.
___
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: Shar file too large
On Mon, Jul 9, 2012 at 7:03 PM, Fernando Apesteguía fernando.apesteg...@gmail.com wrote: On Fri, Jul 6, 2012 at 11:14 PM, Chris Rees cr...@freebsd.org wrote: On 6 July 2012 20:31, Fernando Apesteguía fernando.apesteg...@gmail.com wrote: On Fri, Jul 6, 2012 at 9:16 PM, Chris Rees cr...@freebsd.org wrote: On 6 July 2012 20:14, Fernando Apesteguía fernando.apesteg...@gmail.com wrote: Hi, I'm trying to send a shar(1) file for a new port but it exceeds the 100 KB limit (344 KB) mainly because of the size of the pkg-plist file. Is there an alternative way to upload the file? Do you have any web space available? Try this out: https://www.dropbox.com/s/ipcwfgztpvh7z81/visualparadigm.shar.txt If not email it to me and I'll put it up for you. Great, put that link in your PR. Done[1]. Sorry, I was AFK the whole weekend. [1] http://www.freebsd.org/cgi/query-pr.cgi?pr=169741 I updated the PR. The location of the packages changes too often to keep track of it. I contacted upstream and they could only provide me with a link that leads to a redirection, so I redefined FETCH_ARGS. The previous candidate port doesn't even fetch the tarball anymore (they change it again). Cheers. 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: Questions about/issues with new OPTIONS framework
On Tue, Aug 07, 2012 at 08:43:18PM +0200, Olli Hauer wrote:
On 2012-08-06 18:04, Jeremy Chadwick wrote:
(Please keep me CC'd, as I'm not subscribed to the list)
I've been trying to adapt my /etc/make.conf to make use of the new
OPTIONS framework. I've run into some snags that I was hoping someone
could help me with, as I'm unable to find any official documentation
other than these two documents, which don't help me in this case:
http://wiki.freebsd.org/Ports/Options/OptionsNG
http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/makefile-options.html
Below are my questions so far. Note that these questions are all
preceded by a key fact: /var/db/ports/* is completely empty. Keep that
in mind please.
1. databases/mysql55-server and databases/mysql55-client both ask for
the same variables (OPENSSL and FASTMTX). I want FASTMTX to be enabled
by default for both ports.
When I have the following in /etc/make.conf:
mysql_SET= FASTMTX
Doing make config in databases/mysql55-server shows FASTMTX as checked
(which is correct). However, when I do the exact same procedure in
databases/mysql55-client, FASTMTX is not checked.
I am aware that databases/mysql55-client is a slave port, but I'm not
sure how/why that would matter...?
What am I doing wrong, or is this a port bug which needs to be fixed by
the maintainer?
2. ports/KNOBS is very explicit in stating, and even visually
...
2) alredy answerd ...
answer for question 1)
$ cd mysql55-client make -V UNIQUENAME
or
$ make -V UNIQUENAME -C /usr/ports/databases/mysql55-client/
mysql55-client
So it's based off of UNIQUENAME? That's interesting.
The documentation implies that the name of the variable itself
should be the {nameofport}_SET or {nameofport}_UNSET, where {nameofport}
should equal the name of the actual port directory you're in. Yet, take
a look at this:
root@icarus:/usr/ports/devel/apr0 # make -V UNIQUENAME
apr
root@icarus:/usr/ports/devel/apr1 # make -V UNIQUENAME
apr
root@icarus:/usr/ports/devel/apr2 # make -V UNIQUENAME
apr
Another one where the names are consistent (mtr-nox11 is a stub/slave
port):
root@icarus:/usr/ports/net/mtr # make -V UNIQUENAME
mtr
root@icarus:/usr/ports/net/mtr-nox11 # make -V UNIQUENAME
mtr
All of these consistently use the same UNIQUENAME. To me that seems
like the Right Choice(tm), but then there's this:
root@icarus:/usr/ports/databases/mysql55-server # make -V UNIQUENAME
mysql
root@icarus:/usr/ports/databases/mysql55-client # make -V UNIQUENAME
mysql55-client
I would imagine these should return the same thing (e.g. mysql55-client
should have a UNIQUENAME of mysql, or alternately mysql55-server should
have a UNIQUENAME of mysql55-server).
...while for other ports, it does seem to be based off of the port name
itself. Examples ports include apache22-itk-mpm, p5-DBD-mysql,
p5-libwww, and so on.
How are users supposed to know what the name of the variable is they
should be setting in make.conf? There doesn't even appear to be a make
show-xxx command to help people out with this.
Trial and error seems to be the only way to figure it out, and that's
time-consuming. Luckily this is my home system where I only have 81
ports installed, and only a handful require adjustments, but you can see
my point?
make.conf entry constructed from UNIQUENAME
mysql55-client_SET+= FASTMTX
Please note the '+=' instead '='.
If you have a port where you set more then on option but not as one expression
all ${UNIQUENAME}_SET+= are applied else only the last entry in make.conf.
I don't quite understand your last paragraph (maybe a language barrier;
I say that politely, not insultingly). Can you rephrase for me? Also
how does OPTIONS_SET and OPTIONS_UNSET (talking about the global
variables) fit into this?
Next: the documentation does not state to use '+=' on these entries
in make.conf, it says to use '=':
http://wiki.freebsd.org/Ports/Options/OptionsNG
See, for example, the OPTIONS_SET and OPTIONS_UNSET examples, in
addition to the zsh_SET and zsh_UNSET examples on that web page.
There's nothing about any of this framework in make.conf(5) either.
This is frustrating. There isn't even anything in ports/UPDATING about
any of this, so what am I supposed to go off of? :-(
Additional if you have done `make config' already, then your make.conf entry
is useless since with options NG the OPTIONSFILE has now a higher priority.
Absolutely -- and this is why I outlined (for my case anyway) that
/var/db/ports was empty prior to me doing my tests. I'm well-aware of
the options file and how it takes precedence. :-)
--
| Jeremy Chadwick j...@koitsu.org |
| UNIX Systems Administratorhttp://jdc.koitsu.org/ |
| Mountain View, CA, US|
| Making life hard for others since 1977. PGP 4BD6C0CB |
Re: Questions about/issues with new OPTIONS framework
On 2012-08-07 21:30, Jeremy Chadwick wrote:
On Tue, Aug 07, 2012 at 08:43:18PM +0200, Olli Hauer wrote:
On 2012-08-06 18:04, Jeremy Chadwick wrote:
(Please keep me CC'd, as I'm not subscribed to the list)
I've been trying to adapt my /etc/make.conf to make use of the new
OPTIONS framework. I've run into some snags that I was hoping someone
could help me with, as I'm unable to find any official documentation
other than these two documents, which don't help me in this case:
http://wiki.freebsd.org/Ports/Options/OptionsNG
http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/makefile-options.html
Below are my questions so far. Note that these questions are all
preceded by a key fact: /var/db/ports/* is completely empty. Keep that
in mind please.
1. databases/mysql55-server and databases/mysql55-client both ask for
the same variables (OPENSSL and FASTMTX). I want FASTMTX to be enabled
by default for both ports.
When I have the following in /etc/make.conf:
mysql_SET= FASTMTX
Doing make config in databases/mysql55-server shows FASTMTX as checked
(which is correct). However, when I do the exact same procedure in
databases/mysql55-client, FASTMTX is not checked.
I am aware that databases/mysql55-client is a slave port, but I'm not
sure how/why that would matter...?
What am I doing wrong, or is this a port bug which needs to be fixed by
the maintainer?
2. ports/KNOBS is very explicit in stating, and even visually
...
2) alredy answerd ...
answer for question 1)
$ cd mysql55-client make -V UNIQUENAME
or
$ make -V UNIQUENAME -C /usr/ports/databases/mysql55-client/
mysql55-client
So it's based off of UNIQUENAME? That's interesting.
The documentation implies that the name of the variable itself
should be the {nameofport}_SET or {nameofport}_UNSET, where {nameofport}
should equal the name of the actual port directory you're in. Yet, take
a look at this:
root@icarus:/usr/ports/devel/apr0 # make -V UNIQUENAME
apr
root@icarus:/usr/ports/devel/apr1 # make -V UNIQUENAME
apr
root@icarus:/usr/ports/devel/apr2 # make -V UNIQUENAME
apr
Another one where the names are consistent (mtr-nox11 is a stub/slave
port):
root@icarus:/usr/ports/net/mtr # make -V UNIQUENAME
mtr
root@icarus:/usr/ports/net/mtr-nox11 # make -V UNIQUENAME
mtr
All of these consistently use the same UNIQUENAME. To me that seems
like the Right Choice(tm), but then there's this:
root@icarus:/usr/ports/databases/mysql55-server # make -V UNIQUENAME
mysql
root@icarus:/usr/ports/databases/mysql55-client # make -V UNIQUENAME
mysql55-client
I would imagine these should return the same thing (e.g. mysql55-client
should have a UNIQUENAME of mysql, or alternately mysql55-server should
have a UNIQUENAME of mysql55-server).
...while for other ports, it does seem to be based off of the port name
itself. Examples ports include apache22-itk-mpm, p5-DBD-mysql,
p5-libwww, and so on.
For MySQL server / client sharing the same OPTIONSFILE would make sense
since they have exact the same OPTIONS.
Problematic is where a MASTER port has different options then the slave,
(server/client) and are using the same OPTIONSFILE since then they start
overwrite the other port during `make config'.
It would be nice if an option file could be separated into a shared
and a private section (for example the apache port should honor options
from apr, but at the moment this is only a good wish :)
To answer the question how the UNIQUENAME is constructed
From bsd.port.mk:
.if defined(LATEST_LINK)
UNIQUENAME?=${LATEST_LINK}
.else
UNIQUENAME?=${PKGNAMEPREFIX}${PORTNAME}
.endif
Some more to read about UNIQUENAME
http://lists.freebsd.org/pipermail/freebsd-ports/2012-June/075887.html
Matthew Seaman has already a script to identify all problematic ports
http://lists.freebsd.org/pipermail/freebsd-ports/2012-June/076028.html
How are users supposed to know what the name of the variable is they
should be setting in make.conf? There doesn't even appear to be a make
show-xxx command to help people out with this.
Trial and error seems to be the only way to figure it out, and that's
time-consuming. Luckily this is my home system where I only have 81
ports installed, and only a handful require adjustments, but you can see
my point?
The only proof way at the moment is `make -V UNIQUENAME'
make.conf entry constructed from UNIQUENAME
mysql55-client_SET+=FASTMTX
Please note the '+=' instead '='.
If you have a port where you set more then on option but not as one
expression
all ${UNIQUENAME}_SET+= are applied else only the last entry in make.conf.
I don't quite understand your last paragraph (maybe a language barrier;
I say that politely, not insultingly). Can you rephrase for me? Also
how does OPTIONS_SET and OPTIONS_UNSET (talking about the global
variables) fit into this?
I will try (stop thinking and then translate ...)
Say you have a
Problem upgrading graphics/libglut
FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #29 r238959: Tue Jul 31 19:51:57 EDT 2012 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL amd64 Trying to update graphics/libglut on current as per UPDATING, and nothing happens. 20120804: AFFECTS: users of graphics/libglut AUTHOR: x...@freebsd.org The libglut library is replaced by the freeglut library. Due to shlib version bump all glut users should be rebuild. Please follow the instructions below to upgrade. # env DISABLE_CONFLICTS=1 portupgrade -vfo graphics/freeglut graphics/libglut # portupgrade -vfrx freeglut freeglut # portsnap fetch update Looking up portsnap.FreeBSD.org mirrors... 9 mirrors found. Fetching snapshot tag from geodns-1.portsnap.freebsd.org... done. Ports tree hasn't changed since last snapshot. No updates needed. Ports tree is already up to date. # env DISABLE_CONFLICTS=1 portupgrade -vfo graphics/freeglut graphics/libglut --- Session started at: Tue, 07 Aug 2012 18:07:13 -0400 ** None has been installed or upgraded. --- Session ended at: Tue, 07 Aug 2012 18:07:13 -0400 (consumed 00:00:00) # pkg_info |grep glut libglut-7.6.1 OpenGL utility toolkit Any help is appreciated, thanks in advance. ___ 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: Problem upgrading graphics/libglut
On 8/7/2012 5:17 PM, AN wrote: FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #29 r238959: Tue Jul 31 19:51:57 EDT 2012 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL amd64 Trying to update graphics/libglut on current as per UPDATING, and nothing happens. 20120804: AFFECTS: users of graphics/libglut AUTHOR: x...@freebsd.org The libglut library is replaced by the freeglut library. Due to shlib version bump all glut users should be rebuild. Please follow the instructions below to upgrade. # env DISABLE_CONFLICTS=1 portupgrade -vfo graphics/freeglut graphics/libglut # portupgrade -vfrx freeglut freeglut # portsnap fetch update Looking up portsnap.FreeBSD.org mirrors... 9 mirrors found. Fetching snapshot tag from geodns-1.portsnap.freebsd.org... done. Ports tree hasn't changed since last snapshot. No updates needed. Ports tree is already up to date. # env DISABLE_CONFLICTS=1 portupgrade -vfo graphics/freeglut graphics/libglut --- Session started at: Tue, 07 Aug 2012 18:07:13 -0400 ** None has been installed or upgraded. --- Session ended at: Tue, 07 Aug 2012 18:07:13 -0400 (consumed 00:00:00) # pkg_info |grep glut libglut-7.6.1 OpenGL utility toolkit Can you try this: env DISABLE_CONFLICTS=1 portupgrade -vfo libglut\* Bryan ___ 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: Problem upgrading graphics/libglut
On 8/7/2012 5:22 PM, Bryan Drewery wrote: On 8/7/2012 5:17 PM, AN wrote: FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #29 r238959: Tue Jul 31 19:51:57 EDT 2012 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL amd64 Trying to update graphics/libglut on current as per UPDATING, and nothing happens. 20120804: AFFECTS: users of graphics/libglut AUTHOR: x...@freebsd.org The libglut library is replaced by the freeglut library. Due to shlib version bump all glut users should be rebuild. Please follow the instructions below to upgrade. # env DISABLE_CONFLICTS=1 portupgrade -vfo graphics/freeglut graphics/libglut # portupgrade -vfrx freeglut freeglut # portsnap fetch update Looking up portsnap.FreeBSD.org mirrors... 9 mirrors found. Fetching snapshot tag from geodns-1.portsnap.freebsd.org... done. Ports tree hasn't changed since last snapshot. No updates needed. Ports tree is already up to date. # env DISABLE_CONFLICTS=1 portupgrade -vfo graphics/freeglut graphics/libglut --- Session started at: Tue, 07 Aug 2012 18:07:13 -0400 ** None has been installed or upgraded. --- Session ended at: Tue, 07 Aug 2012 18:07:13 -0400 (consumed 00:00:00) # pkg_info |grep glut libglut-7.6.1 OpenGL utility toolkit Can you try this: env DISABLE_CONFLICTS=1 portupgrade -vfo libglut\* Meant of course: env DISABLE_CONFLICTS=1 portupgrade -vfo graphics/freeglut libglut\* Bryan ___ 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
Problem rebuilding mesa-demos
FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #29 r238959: Tue Jul 31 19:51:57 EDT 2012 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL amd64 After updating to graphics/freeglut I had a few failures trying to update related ports, seems like a problem with mesa-demos: cc -I../../include -I/usr/local/include -D_THREAD_SAFE -I/usr/local/include -O2 -pipe -fno-strict-aliasing -Wall -Wmissing-prototypes -std=c99-fno-strict-aliasing -fPIC -DUSE_X86_64_ASM -DHAVE_POSIX_MEMALIGN -DUSE_XCB -DPTHREADS -DUSE_EXTERNAL_DXTN_LIB=1 -DIN_DRI_DRIVER -DHAVE_ALIAS-DGLX_INDIRECT_RENDERING -DGLX_DIRECT_RENDERING -L/usr/local/lib -pthread glxpbdemo.c -L../../lib -lGL -lm -o glxpbdemo /tmp//cccypyrI.o: In function `main': glxpixmap.c:(.text+0x1c5): undefined reference to `glXCreateGLXPixmapMESA' gmake[2]: *** [glxpixmap] Error 1 gmake[2]: *** Waiting for unfinished jobs gmake[2]: Leaving directory `/usr/ports/graphics/mesa-demos/work/Mesa-7.6.1/progs/xdemos' gmake[1]: *** [subdirs] Error 1 gmake[1]: Leaving directory`/usr/ports/graphics/mesa-demos/work/Mesa-7.6.1/progs' gmake: *** [default] Error 1 *** [do-build] Error code 1 Stop in /usr/ports/graphics/mesa-demos. *** [build] Error code 1 Stop in /usr/ports/graphics/mesa-demos. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade20120807-8075-15oyqd8-0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=mesa-demos-7.6.1 UPGRADE_PORT_VER=7.6.1 make ** Fix the problem and try again. --- Skipping 'x11-wm/compiz' (compiz-0.8.4_8) because a requisite package 'mesa-demos-7.6.1' (graphics/mesa-demos) failed (specify -k to force) --- ** Upgrade tasks 10: 3 done, 0 ignored, 1 skipped and 1 failed --- Skipping 'x11-wm/compiz-plugins-main' (compiz-plugins-main-0.8.4_4) because a requisite package 'compiz-0.8.4_8' (x11-wm/compiz) failed (specify -k to force) --- ** Upgrade tasks 10: 3 done, 0 ignored, 2 skipped and 1 failed --- Skipping 'x11-wm/compiz-plugins-extra' (compiz-plugins-extra-0.8.4_5) because a requisite package 'compiz-0.8.4_8' (x11-wm/compiz) failed (specify -k to force) --- ** Upgrade tasks 10: 3 done, 0 ignored, 3 skipped and 1 failed --- Skipping 'x11-wm/emerald' (emerald-0.8.4_7) because a requisite package 'compiz-0.8.4_8' (x11-wm/compiz) failed (specify -k to force) --- ** Upgrade tasks 10: 3 done, 0 ignored, 4 skipped and 1 failed --- Skipping 'x11-wm/compiz-fusion' (compiz-fusion-0.8.4_2) because a requisite package 'emerald-0.8.4_7' (x11-wm/emerald) failed (specify -k to force) --- ** Upgrade tasks 10: 4 done, 0 ignored, 5 skipped and 1 failed --- Listing the results (+:done / -:ignored / *:skipped / !:failed) ! graphics/mesa-demos (mesa-demos-7.6.1)(new compiler error) + graphics/gle (gle-3.1.0_2 - gle-3.1.0_3) + x11/xscreensaver-gnome-hacks (xscreensaver-gnome-hacks-5.12_1 - xscreensaver-gnome-hacks-5.12_1) + x11/gnome-screensaver (gnome-screensaver-2.30.2_3 - gnome-screensaver-2.30.2_3) * x11-wm/compiz (compiz-0.8.4_8) * x11-wm/compiz-plugins-main (compiz-plugins-main-0.8.4_4) * x11-wm/compiz-plugins-extra (compiz-plugins-extra-0.8.4_5) * x11-wm/emerald (emerald-0.8.4_7) * x11-wm/compiz-fusion (compiz-fusion-0.8.4_2) + x11/gnome2 (gnome2-2.32.1_4 - gnome2-2.32.1_4) --- Packages processed: 4 done, 0 ignored, 5 skipped and 1 failed --- Session ended at: Tue, 07 Aug 2012 18:44:37 -0400 (consumed 00:06:14) Can I provide any more info to help fix? ___ 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
