Re: FreeBSD Port: ejabberd-2.1.13 - Release updates available; 14.05, 13.12 13.10
On Mon, 19 May 2014 21:22:40 +0200, Matthieu Volat ma...@alkumuna.eu said: On Mon, 19 May 2014 13:40:00 +0530 ash...@freebsd.org (Ashish SHUKLA) wrote: Hi, Thanks to the PR ports/189812[1] filed by Joseph Benden, I'm able to update the net-im/ejabberd to 14.05. Following is the link to the diff, if you like to try it: url:http://people.freebsd.org/~ashish/diffs/ejabberd-14.05.diff sha256: ce4ed8c47734348bc4499af3d11ae2dbc53fc50f4b2041dc557dae793706b188 There is one issue though. As, I don't use PAM option, I could not check PAM support. This port does not install 'epam' binary anymore (although it's compiled). So, if you (or someone) are using PAM support already, and can test if it works without that binary that'll be great. If you encounter any other issues, please feel free to report those to me. I plan to commit this by the end of this week. References: [1] http://www.freebsd.org/cgi/query-pr.cgi?pr=189812 Thanks! -- Ashish SHUKLA | GPG: F682 CDCC 39DC 0FEA E116 20B6 C746 CFA9 E74F A4B0 Sent from my Emacs Thanks for your work, I use the pam module, and the server would not start without epam: 2014-05-19 21:03:50.464 [error] 0.408.0 Can't open file @rootdir@/lib/erlang/lib/ejabberd-14.05/priv/bin/epam: enoent Copying the epam binary from WRKDIR, setted to root:ejabberd rwsr-x--- to /usr/local/lib/erlang/lib/ejabberd-14.05/priv/bin/epam is not enough, it seems... Sorry for the delay in getting back to you. Could you please try this diff[1] which fixes this '@rootdir@' thing ? After installing the port, you need to manually copy the 'epam' binary to its place as you were doing before. Let me know how it goes for you References: [1] http://people.freebsd.org/~ashish/diffs/ejabberd-14.05-0.diff sha256: 9d8ced60960ee3177a234b620c4518092afb834e9880ecfa9ddc04b6b2c873fc Thanks! -- Ashish SHUKLA | GPG: F682 CDCC 39DC 0FEA E116 20B6 C746 CFA9 E74F A4B0 Sent from my Emacs signature.asc Description: PGP signature
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 +-+ www/groupoffice | 3.7.24 | 6.0.2 +-+ www/webservices | 0.5.5 | 0.6.1 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
net/miniupnpd: committer for ports/189061?
Hi, The patch in http://www.freebsd.org/cgi/query-pr.cgi?pr=189061 updates miniupnpd to the most recent version and exposes a few more options to make config. The maintainer (on CC) has approved the patch in the PR. Would somebody be willing to take it and commit it? Thanks, Daniel smime.p7s Description: S/MIME cryptographic signature
Re: FreeBSD Port: ejabberd-2.1.13 - Release updates available; 14.05, 13.12 13.10
On Thu, 22 May 2014 14:05:09 +0530 ash...@freebsd.org (Ashish SHUKLA) wrote: [...] Sorry for the delay in getting back to you. Could you please try this diff[1] which fixes this '@rootdir@' thing ? After installing the port, you need to manually copy the 'epam' binary to its place as you were doing before. Let me know how it goes for you Thanks, it is working. Like you said, I had to copy epam manualy, set it to root:ejabberd 750 with setuid bit. Very well done! References: [1] http://people.freebsd.org/~ashish/diffs/ejabberd-14.05-0.diff sha256: 9d8ced60960ee3177a234b620c4518092afb834e9880ecfa9ddc04b6b2c873fc Thanks! -- Ashish SHUKLA | GPG: F682 CDCC 39DC 0FEA E116 20B6 C746 CFA9 E74F A4B0 Sent from my Emacs -- Matthieu Volat ma...@alkumuna.eu tel: 06 84 54 39 43 www: http://500px.com/Mazhe signature.asc Description: PGP signature
Re: FreeBSD Port: ejabberd-2.1.13 - Release updates available; 14.05, 13.12 13.10
On Thu, 22 May 2014 18:17:35 +0200, Matthieu Volat ma...@alkumuna.eu said: On Thu, 22 May 2014 14:05:09 +0530 ash...@freebsd.org (Ashish SHUKLA) wrote: [...] Sorry for the delay in getting back to you. Could you please try this diff[1] which fixes this '@rootdir@' thing ? After installing the port, you need to manually copy the 'epam' binary to its place as you were doing before. Let me know how it goes for you Thanks, it is working. Like you said, I had to copy epam manualy, set it to root:ejabberd 750 with setuid bit. Very well done! Thanks for checking. Hopefully we'll have a fix (to avoid manual copying) in final port. -- Ashish SHUKLA | GPG: F682 CDCC 39DC 0FEA E116 20B6 C746 CFA9 E74F A4B0 Sent from my Emacs signature.asc Description: PGP signature
splitting subversion port?
I was wondering if you would be open to peeling off the mod_dav_svn from being an option in the subversion port to being its own port that depends on this one, or making a sub-port that installs subversion with it enabled under a different package name. The reason I have is that I am trying to switch over to pkgng and using pre-built packages for everything. I can't do this for subversion as I need the dav module on one server, but not on any other machine I run. Also, I use another apache module, www/mod_authnz_crowd, which depends on a subversion built with mod_dav_svn. As it stands, I cannot make a package for that easily. There is precedent for splitting the apache module out, as PHP5 has recently done just that. By splitting the module out into its own port, all of this would be possible, and it would avoid having to install the module-enabled package on all of my servers which would pull down apache, as well, which I do not need on my compute nodes. Another way of accomplishing the goal would be to make a sub-port similar to things like emacs-nox11 and ImageMagick-nox11 that install their base ports with specific options. There could be a subversion-apache port that builds the subversion port with the apache module and dependencies. Anyhow, I'm willing to try to do the work, but I wanted to know if you're agreeable, and which way you'd prefer to do it. Obviously the sub-port would be easier. I have a feeling the split port may not work out because the SVNUSER gets changed if the dav module is enabled. ___ 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
NDOUtils 2.0 compiles OK in FreeBSD 10 (o use with Nagios 4)
FYI. Hi all! I succeeded in compile NDOUtils 2.0 in FreeBSD 10 in the following way: I needed NDOUtils 2.0 in order to work with Nagios 4 and after to install Centreon. # uname -rsmp FreeBSD 10.0-RELEASE-p1 amd64 amd64 # fetch http://sourceforge.net/projects/nagios/files/ndoutils-2.x/ndoutils-2.0.0/ndoutils-2.0.0.tar.gz # tar -zxf ndoutils-2.0.0.tar.gz # cd ndoutils-2.0.0/ # vi include/config.h #include /usr/local/include/mysql/mysql.h #include /usr/local/include/mysql/errmsg.h # ./configure CFLAGS=-fPIC # make # make install /usr/bin/install -c -m 775 -o nagios -g nagios -d /usr/local/nagios/bin /usr/bin/install -c -m 755 -o nagios -g nagios ndo2db-4x /usr/local/nagios/bin/ndo2db /usr/bin/install -c -m 755 -o nagios -g nagios ndomod-4x.o /usr/local/nagios/bin/ndomod.o /usr/bin/install -c -m 774 -o nagios -g nagios file2sock /usr/local/nagios/bin /usr/bin/install -c -m 774 -o nagios -g nagios log2ndo /usr/local/nagios/bin /usr/bin/install -c -m 774 -o nagios -g nagios sockdebug /usr/local/nagios/bin Hint: NDOUtils Installation against Nagios v4.x completed. If you want to install NDOUtils for Nagios v3.x please type 'make install-3x If you want to install NDOUtils for Nagios v2.x please type 'make install-2x Next step should be the database initialization/upgrade cd into the db/ directory and either: ./installdb (for a new installation) or: ./upgradedb (for an existing one) ——— Before these changes i was not able to compile NDOUtils 2.0: root@ns1:~/ndoutils-2.0.0 # ./configure checking for a BSD-compatible install... /usr/bin/install -c checking for perl... /usr/bin/perl checking build system type... x86_64-unknown-freebsd10.0 checking host system type... x86_64-unknown-freebsd10.0 checking for gcc... no checking for cc... cc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether cc accepts -g... yes checking for cc option to accept ISO C89... none needed checking whether make sets $(MAKE)... yes checking how to run the C preprocessor... cc -E checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for ANSI C header files... yes checking whether time.h and sys/time.h may both be included... yes checking for sys/wait.h that is POSIX.1 compatible... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking arpa/inet.h usability... yes checking arpa/inet.h presence... yes checking for arpa/inet.h... yes checking ctype.h usability... yes checking ctype.h presence... yes checking for ctype.h... yes checking dirent.h usability... yes checking dirent.h presence... yes checking for dirent.h... yes checking dlfcn.h usability... yes checking dlfcn.h presence... yes checking for dlfcn.h... yes checking errno.h usability... yes checking errno.h presence... yes checking for errno.h... yes checking fcntl.h usability... yes checking fcntl.h presence... yes checking for fcntl.h... yes checking float.h usability... yes checking float.h presence... yes checking for float.h... yes checking getopt.h usability... yes checking getopt.h presence... yes checking for getopt.h... yes checking grp.h usability... yes checking grp.h presence... yes checking for grp.h... yes checking for inttypes.h... (cached) yes checking limits.h usability... yes checking limits.h presence... yes checking for limits.h... yes checking ltdl.h usability... no checking ltdl.h presence... no checking for ltdl.h... no checking math.h usability... yes checking math.h presence... yes checking for math.h... yes checking netdb.h usability... yes checking netdb.h presence... yes checking for netdb.h... yes checking netinet/in.h usability... yes checking netinet/in.h presence... yes checking for netinet/in.h... yes checking pthread.h usability... yes checking pthread.h presence... yes checking for pthread.h... yes checking pwd.h usability... yes checking pwd.h presence... yes checking for pwd.h... yes checking regex.h usability... yes checking regex.h presence... yes checking for regex.h... yes checking signal.h usability... yes checking signal.h presence... yes checking for signal.h... yes checking socket.h usability... no checking socket.h presence... no checking for socket.h... no checking stdarg.h usability... yes checking stdarg.h presence... yes checking for stdarg.h... yes checking for stdint.h... (cached) yes checking for string.h... (cached) yes checking for strings.h... (cached) yes checking sys/ipc.h usability... yes checking sys/ipc.h presence... yes checking for
Re: bsd.emacs.mk does not detect non-GUI, non-X11 options
Vick Khera vi...@khera.org writes: All of my freebsd boxes are headless, and I build all ports without X11. To accomplish this, I specify in make.conf the following: WITHOUT_GNOME=yes WITHOUT_X11=yes OPTIONS_UNSET=X11 GUI I have to specify both WITHOUT_X11 and OPTIONS_UNSET since I have found some ports to not honor OPTIONS_UNSET yet. So now I'm moving from individually building ports on each server to using poudriere and pkgng to build packages customized for my environment. This is where I run into problems... One of the packages I need to build is textproc/markdown-mode.el. This port specifies USE_EMACS in the Makefile. When I build this port on a system which has emacs-nox11 installed, all is fine. WhenI try to build this port inside poudriere, it wants to build emacs24 as a dependency. Thus, the package for markdown-mode.el will install emacs instead of using emacs-nox11. I'm not sure why that's a problem, because if you build editors/emacs with the port option for X11 disabled, it should tell configure to use the --without-x argument. The results should be identical to emacs-nox11, except for not having the -nox11 suffix in the package name. I don't have any easy way to experiment with this at the moment, but I can't see any way that configure can pass that argument and have it go after X anyway. If other dependencies conflicted, I'd expect the run to end up with an IGNORE line. Come to think of it, are you sure that X11 is being included? Please humor me by checking to see whether the poudriere run builds, say, libX11, and whether the emacs package that gets built actually links to the X libraries... ...and failing that, the -nox11 port is just a slave port of editors/emacs anyway, so one of the variables in there has to be the magic you're looking for. Is there some way to convince markdown-mode.el to depend on emacs-nox11 instead when building the packages via poudriere? I don't even see how to explicitly state the dependency outside of poudriere. I'm pretty sure that setting EMACS_PORT_NAME will do it in any case. EMACS_PORT_NAME=emacs-nox11 ___ 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
multimedia/ffmpeg: pkg_add: leave_playpen: can't chdir back to ''
I built the latest multimedia/ffmpeg and now it won't install, due to the error(s) shown below. Is there a known fix for this? P.S. Apparently this error: pkg_add: leave_playpen: can't chdir back to '' has been publically discussed since at least January, 2012. In all that time, why hasn't anybody fixed it? = # make install === Installing for ffmpeg-2.1.1_3,1 === ffmpeg-2.1.1_3,1 depends on shared library: libfontconfig.so - found === ffmpeg-2.1.1_3,1 depends on shared library: libfreetype.so - found === ffmpeg-2.1.1_3,1 depends on shared library: libgnutls.so - found === ffmpeg-2.1.1_3,1 depends on shared library: libopencv_imgproc.so - found === ffmpeg-2.1.1_3,1 depends on shared library: libschroedinger-1.0.so - found === ffmpeg-2.1.1_3,1 depends on shared library: libtheora.so - found === ffmpeg-2.1.1_3,1 depends on shared library: libva.so - found === ffmpeg-2.1.1_3,1 depends on shared library: libvorbisenc.so - found === ffmpeg-2.1.1_3,1 depends on shared library: libvpx.so - found === ffmpeg-2.1.1_3,1 depends on shared library: libx264.so - found === ffmpeg-2.1.1_3,1 depends on shared library: libxvidcore.so - found === ffmpeg-2.1.1_3,1 depends on shared library: libiconv.so.3 - found === Checking if multimedia/ffmpeg already installed share/doc/ffmpeg/APIchanges: Could not unlink share/doc/ffmpeg/CREDITS: Could not unlink share/doc/ffmpeg/Changelog: Could not unlink share/doc/ffmpeg/INSTALL: Could not unlink share/doc/ffmpeg/LICENSE: Could not unlink share/doc/ffmpeg/MAINTAINERS: Could not unlink share/doc/ffmpeg/README: Could not unlink share/doc/ffmpeg/RELEASE_NOTES: Could not unlink share/doc/ffmpeg/avutil.txt: Could not unlink share/doc/ffmpeg/build_system.txt: Could not unlink share/doc/ffmpeg/developer.html: Could not unlink share/doc/ffmpeg/errno.txt: Could not unlink share/doc/ffmpeg/faq.html: Could not unlink share/doc/ffmpeg/fate.html: Could not unlink share/doc/ffmpeg/fate.txt: Could not unlink share/doc/ffmpeg/ffmpeg-all.html: Could not unlink share/doc/ffmpeg/ffmpeg-bitstream-filters.html: Could not unlink share/doc/ffmpeg/ffmpeg-codecs.html: Could not unlink share/doc/ffmpeg/ffmpeg-devices.html: Could not unlink share/doc/ffmpeg/ffmpeg-filters.html: Could not unlink share/doc/ffmpeg/ffmpeg-formats.html: Could not unlink share/doc/ffmpeg/ffmpeg-protocols.html: Could not unlink share/doc/ffmpeg/ffmpeg-resampler.html: Could not unlink share/doc/ffmpeg/ffmpeg-scaler.html: Could not unlink share/doc/ffmpeg/ffmpeg-utils.html: Could not unlink share/doc/ffmpeg/ffmpeg.html: Could not unlink share/doc/ffmpeg/ffmpeg.txt: Could not unlink share/doc/ffmpeg/ffprobe-all.html: Could not unlink share/doc/ffmpeg/ffprobe.html: Could not unlink share/doc/ffmpeg/ffserver-all.html: Could not unlink share/doc/ffmpeg/ffserver.html: Could not unlink share/doc/ffmpeg/filter_design.txt: Could not unlink share/doc/ffmpeg/general.html: Could not unlink share/doc/ffmpeg/git-howto.html: Could not unlink share/doc/ffmpeg/git-howto.txt: Could not unlink share/doc/ffmpeg/issue_tracker.txt: Could not unlink share/doc/ffmpeg/libavcodec.html: Could not unlink share/doc/ffmpeg/libavdevice.html: Could not unlink share/doc/ffmpeg/libavfilter.html: Could not unlink share/doc/ffmpeg/libavformat.html: Could not unlink share/doc/ffmpeg/libavutil.html: Could not unlink share/doc/ffmpeg/libswresample.html: Could not unlink share/doc/ffmpeg/libswscale.html: Could not unlink share/doc/ffmpeg/mips.txt: Could not unlink share/doc/ffmpeg/multithreading.txt: Could not unlink share/doc/ffmpeg/nut.html: Could not unlink share/doc/ffmpeg/optimization.txt: Could not unlink share/doc/ffmpeg/platform.html: Could not unlink share/doc/ffmpeg/rate_distortion.txt: Could not unlink share/doc/ffmpeg/snow.txt: Could not unlink share/doc/ffmpeg/soc.txt: Could not unlink share/doc/ffmpeg/swresample.txt: Could not unlink share/doc/ffmpeg/swscale.txt: Could not unlink share/doc/ffmpeg/tablegen.txt: Could not unlink share/doc/ffmpeg/viterbi.txt: Could not unlink tar: Error exit delayed from previous errors. pkg_add: leave_playpen: can't chdir back to '' *** [install-package] Error code 2 Stop in /usr/ports/multimedia/ffmpeg. *** [install] Error code 1 Stop in /usr/ports/multimedia/ffmpeg. ___ 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: multimedia/ffmpeg: pkg_add: leave_playpen: can't chdir back to ''
On Thu, May 22, 2014 at 1:44 PM, Ronald F. Guilmette r...@tristatelogic.comwrote: I built the latest multimedia/ffmpeg and now it won't install, due to the error(s) shown below. Is there a known fix for this? P.S. Apparently this error: pkg_add: leave_playpen: can't chdir back to '' has been publically discussed since at least January, 2012. In all that time, why hasn't anybody fixed it? = # make install === Installing for ffmpeg-2.1.1_3,1 === ffmpeg-2.1.1_3,1 depends on shared library: libfontconfig.so - found === ffmpeg-2.1.1_3,1 depends on shared library: libfreetype.so - found === ffmpeg-2.1.1_3,1 depends on shared library: libgnutls.so - found === ffmpeg-2.1.1_3,1 depends on shared library: libopencv_imgproc.so - found === ffmpeg-2.1.1_3,1 depends on shared library: libschroedinger-1.0.so- found === ffmpeg-2.1.1_3,1 depends on shared library: libtheora.so - found === ffmpeg-2.1.1_3,1 depends on shared library: libva.so - found === ffmpeg-2.1.1_3,1 depends on shared library: libvorbisenc.so - found === ffmpeg-2.1.1_3,1 depends on shared library: libvpx.so - found === ffmpeg-2.1.1_3,1 depends on shared library: libx264.so - found === ffmpeg-2.1.1_3,1 depends on shared library: libxvidcore.so - found === ffmpeg-2.1.1_3,1 depends on shared library: libiconv.so.3 - found === Checking if multimedia/ffmpeg already installed share/doc/ffmpeg/APIchanges: Could not unlink share/doc/ffmpeg/CREDITS: Could not unlink share/doc/ffmpeg/Changelog: Could not unlink share/doc/ffmpeg/INSTALL: Could not unlink share/doc/ffmpeg/LICENSE: Could not unlink share/doc/ffmpeg/MAINTAINERS: Could not unlink share/doc/ffmpeg/README: Could not unlink share/doc/ffmpeg/RELEASE_NOTES: Could not unlink share/doc/ffmpeg/avutil.txt: Could not unlink share/doc/ffmpeg/build_system.txt: Could not unlink share/doc/ffmpeg/developer.html: Could not unlink share/doc/ffmpeg/errno.txt: Could not unlink share/doc/ffmpeg/faq.html: Could not unlink share/doc/ffmpeg/fate.html: Could not unlink share/doc/ffmpeg/fate.txt: Could not unlink share/doc/ffmpeg/ffmpeg-all.html: Could not unlink share/doc/ffmpeg/ffmpeg-bitstream-filters.html: Could not unlink share/doc/ffmpeg/ffmpeg-codecs.html: Could not unlink share/doc/ffmpeg/ffmpeg-devices.html: Could not unlink share/doc/ffmpeg/ffmpeg-filters.html: Could not unlink share/doc/ffmpeg/ffmpeg-formats.html: Could not unlink share/doc/ffmpeg/ffmpeg-protocols.html: Could not unlink share/doc/ffmpeg/ffmpeg-resampler.html: Could not unlink share/doc/ffmpeg/ffmpeg-scaler.html: Could not unlink share/doc/ffmpeg/ffmpeg-utils.html: Could not unlink share/doc/ffmpeg/ffmpeg.html: Could not unlink share/doc/ffmpeg/ffmpeg.txt: Could not unlink share/doc/ffmpeg/ffprobe-all.html: Could not unlink share/doc/ffmpeg/ffprobe.html: Could not unlink share/doc/ffmpeg/ffserver-all.html: Could not unlink share/doc/ffmpeg/ffserver.html: Could not unlink share/doc/ffmpeg/filter_design.txt: Could not unlink share/doc/ffmpeg/general.html: Could not unlink share/doc/ffmpeg/git-howto.html: Could not unlink share/doc/ffmpeg/git-howto.txt: Could not unlink share/doc/ffmpeg/issue_tracker.txt: Could not unlink share/doc/ffmpeg/libavcodec.html: Could not unlink share/doc/ffmpeg/libavdevice.html: Could not unlink share/doc/ffmpeg/libavfilter.html: Could not unlink share/doc/ffmpeg/libavformat.html: Could not unlink share/doc/ffmpeg/libavutil.html: Could not unlink share/doc/ffmpeg/libswresample.html: Could not unlink share/doc/ffmpeg/libswscale.html: Could not unlink share/doc/ffmpeg/mips.txt: Could not unlink share/doc/ffmpeg/multithreading.txt: Could not unlink share/doc/ffmpeg/nut.html: Could not unlink share/doc/ffmpeg/optimization.txt: Could not unlink share/doc/ffmpeg/platform.html: Could not unlink share/doc/ffmpeg/rate_distortion.txt: Could not unlink share/doc/ffmpeg/snow.txt: Could not unlink share/doc/ffmpeg/soc.txt: Could not unlink share/doc/ffmpeg/swresample.txt: Could not unlink share/doc/ffmpeg/swscale.txt: Could not unlink share/doc/ffmpeg/tablegen.txt: Could not unlink share/doc/ffmpeg/viterbi.txt: Could not unlink tar: Error exit delayed from previous errors. pkg_add: leave_playpen: can't chdir back to '' *** [install-package] Error code 2 Stop in /usr/ports/multimedia/ffmpeg. *** [install] Error code 1 Stop in /usr/ports/multimedia/ffmpeg. The list of Could not unlink messages smell like some sort of permissions problem. Since I have not either seen this issue nor have many others, there most be something different about your build that triggers the error. Please provide the output of uname -a, make -C /usr/ports/multimedia/ffmpeg showconfig and cat /etc/make.conf. I assume that you are using the old pkg system due to the reference to pkg_add.. Are you building/installing as root? Anything else that might be unusual?
Re: bsd.emacs.mk does not detect non-GUI, non-X11 options
On Thu, May 22, 2014 at 4:08 PM, Lowell Gilbert freebsd-ports-lo...@be-well.ilk.org wrote: I'm not sure why that's a problem, because if you build editors/emacs with the port option for X11 disabled, it should tell configure to use the --without-x argument. The results should be identical to emacs-nox11, except for not having the -nox11 suffix in the package I think I threw in too many distracting details. What I'm saying here is that when I specify USE_EMACS in the Makefile for a port, it should detect if X11 is disabled and select the correct emacs-nox11 port as the dependency automatically. One precedent for this is the USE_GHOSTSCRIPT knob. If that is specified in a port, it automatically chooses the -nox11 slave port for ghostscript if WITHOUT_X11 is set. Since emacs has a -nox11 slave port, I believe it should work in the same way for consistency. ___ 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: multimedia/ffmpeg: pkg_add: leave_playpen: can't chdir back to ''
In message can6yy1vziebtf8ueotil9xrvrq_rzbkhlysn3qgduoruqje...@mail.gmail.com Kevin Oberman rkober...@gmail.com wrote: On Thu, May 22, 2014 at 1:44 PM, Ronald F. Guilmette r...@tristatelogic.comwrote: ... share/doc/ffmpeg/swscale.txt: Could not unlink share/doc/ffmpeg/tablegen.txt: Could not unlink share/doc/ffmpeg/viterbi.txt: Could not unlink tar: Error exit delayed from previous errors. pkg_add: leave_playpen: can't chdir back to '' *** [install-package] Error code 2 Stop in /usr/ports/multimedia/ffmpeg. *** [install] Error code 1 Stop in /usr/ports/multimedia/ffmpeg. The list of Could not unlink messages smell like some sort of permissions problem. Nevermind. Apparently, there was a _file_... please note... a _file_ (not a directory) on my system with the name /usr/local/share/doc/ffmpeg and this was apparently causing all the problems. I removed it and now the install completes without error. I myseld never intentionally created that file, and I feel that it must have been a left-over of some kind of some prior install of ffmpeg... perhaps from long ago. The file itself was apparently a text file, 7 bytes long, containing only the following text: 0.7.15 I say again that I personally have no recollection of *ever* having intentionally created any such file. I humbly suggest that install scripts should avoid making assumptions about the presence of absence of some particular type of thing within the file system unless the scripts in question have themselves made all necessary arrangements beforehand to create said filesystem objects (and using rm -f where necessary, in order to reliably clear the way for any such creations). ___ 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
