Re: mail/roundcube (bsd.php.mk broken?)
> Now i have to manually reinstall all the php packages and > binaries that depend on them and hope that my php > software will still function with the new php. There’s no need to manually reinstall. This thread provides a clue in its very last post: https://forums.freebsd.org/threads/50622/ Just use pkg and portmaster and you’re pretty much set. 5.6 to 7.0 has had some teething pains, but 5.4 to 5.6 is not rocket surgery. -- Raivo ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
building multimedia/ffmpeg results in tons of 'undefined references'
FreeBSD 10.1-STABLE from mid-June on a Core2Duo. Building multimedia/ffmpeg invariably fails for me like this: MAN doc/ffprobe.1 MAN doc/ffmpeg-all.1 MAN doc/ffprobe-all.1 MAN doc/ffmpeg-utils.1 libavcodec/libavcodec.so: undefined reference to `ff_dcadsp_init_x86' libavcodec/libavcodec.so: undefined reference to `ff_ttadsp_init_x86' libavcodec/libavcodec.so: undefined reference to `ff_dwt_init_x86' libavcodec/libavcodec.so: undefined reference to `ff_bswapdsp_init_x86' libavcodec/libavcodec.so: undefined reference to `ff_h264dsp_init_x86' libavcodec/libavcodec.so: undefined reference to `ff_h263dsp_init_x86’ Etc. Needless to say, the functions are nicely present within the files. Curiously enough, it is always multimedia/ffmpeg and never any of the suffixed ffmpeg ports, such as multimedia/ffmpeg26, which did not used to build when it was still called multimedia/ffmpeg, but now, having gained the suffix, builds without an issue. There is no difference whether I have a make.conf or not. No suffix - build fail. Suffix - no problemo. Where should I look? I am completely at a loss. I have read through all the man pages I could think of (ldconfig and ld, to be precise), wandered in places the former recommended, and found nothing. The same port builds fine on another FreeBSD machine that I administer. -- Raivo ___ 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: print/cups-base - Avahi backend
The cups-base port has been marked as BROKEN if built against Avahi since version 1.4. (The Makefile even helpfully points the user to http://www.avahi.org/ticket/303 which states that the problem exists with CUPS version 1.4 and that a fix is in the making.) Since version 1.6, however, there exists native Avahi support in CUPS and there is really no point in marking the port broken and including all kinds of compatibility headers that are no longer of any use whatsoever. Building CUPS 1.7 directly against Avahi works well and without any need for the avahi-compat-libdns_sd headers. I tested the setup on my system and came up with the following patch that incidentally also checks whether one or the other mDNS backend was selected and activates the pkg-plist magic accordingly. (Note how the dependency on avahi-libdns has been replaced with a dependency on avahi-app, as the configure script checks for the presence of libavahi-client.so, installed by net/avahi-app.) Raivo patch-cups_172_avahi Description: Binary data ___ 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"
