portmaster: printing messages that do not come from pkg-message files
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Hello, portmaster's feature to print collected pkg-message files after successful installation is very useful. However, there are many ports that echo messages from inside Makefile, usually in post-install phase (but not exclusively there). A simple question: would it be possible (or better, would it be desirable) to collect that text as well and to include it in the final output in the same way it is done with pkg-messages? Best regards, - -- Nikola Lečić = Никола Лечић fingerprint : FEF3 66AF C90E EDC3 D878 7CDC 956D F4AB A377 1C9B -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.11 (FreeBSD) iJwEAQEDAAYFAks/exQACgkQ/MM/0rYIoZjvvwP/XfClZj6xNhEri/uDK4ijPiLH xlF2umQji9VoGEpJy3pm+ZyzX8GP03VNJsSVNPOI+vyuz6eXXVae45+yfL0CLY/L 6RPKCi3QGLC8PFP5Bv1X/MpA+usUMKSOpprGYxSfxrVOT5yFl2lSxT7hyHEAbIZb QxkLkcLF0jOwZboMQnk= =d/Pz -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: portmaster: printing messages that do not come from pkg-message files
2010/1/2 Nikola Lečić nikola.le...@anthesphoria.net: Hello, portmaster's feature to print collected pkg-message files after successful installation is very useful. However, there are many ports that echo messages from inside Makefile, usually in post-install phase (but not exclusively there). A simple question: would it be possible (or better, would it be desirable) to collect that text as well and to include it in the final output in the same way it is done with pkg-messages? Hi, It's better to correct these ports to make them use pkg-message, so it will be printed by portmaster *and* pkg_add (dont forget packages !) Best, Julien ___ 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
lang/cmucl port broken in FreeBSD. [PATCH attached]
The problem is that the prebuilt binary it downloads is linked to
older libraries (libutils and some others).
uname -a: FreeBSD freebsd.gateway.2wire.net 8.0-RELEASE FreeBSD
8.0-RELEASE #0: Sat Nov 21 15:48:17 UTC 2009
r...@almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386
The following fixes the port so it works correctly on FreeBSD 8.0. I
just used an updated binary for 8.0rc1. At least this makes the port
work in 8.0 since originally it was unusable.
diff -u /usr/ports/lang/cmucl/Makefile cmucl/Makefile
--- /usr/ports/lang/cmucl/Makefile 2009-04-29 10:38:12.0 -0500
+++ cmucl/Makefile 2010-01-02 11:47:24.0 -0600
@@ -7,7 +7,7 @@
#
PORTNAME= cmucl
-PORTVERSION= 19f
+PORTVERSION= 20a
PORTREVISION= 1
CATEGORIES=lang lisp
MASTER_SITES= http://common-lisp.net/pub/project/cmucl/release/${PORTVERSION}/
\
@@ -15,7 +15,7 @@
ftp://ftp.averillpark.net/cmucl/release/${PORTVERSION}/ \
ftp://ftp.linux.org.uk/pub/lisp/cmucl/release/${PORTVERSION}/ \
ftp://ftp.tepus.com/pub/project/cmucl/release/${PORTVERSION}/
-DISTNAME= ${PORTNAME}-${PORTVERSION}-x86-freebsd_6.3-release
+DISTNAME= ${PORTNAME}-${PORTVERSION}-x86-freebsd_8.0-rc1
MAINTAINER=craca...@cons.org
COMMENT= The CMU implementation of Common Lisp
diff -u /usr/ports/lang/cmucl/distinfo cmucl/distinfo
--- /usr/ports/lang/cmucl/distinfo 2009-04-29 10:38:12.0 -0500
+++ cmucl/distinfo 2010-01-02 11:45:32.0 -0600
@@ -1,3 +1,3 @@
-MD5 (cmucl-19f-x86-freebsd_6.3-release.tar.bz2) =
f099355a4c2e85b03c8d8f3949f96619
-SHA256 (cmucl-19f-x86-freebsd_6.3-release.tar.bz2) =
d627940a9b30e831acf684ed0b17419d4299f112add208782d9f6f503216103e
-SIZE (cmucl-19f-x86-freebsd_6.3-release.tar.bz2) = 15213148
+MD5 (cmucl-20a-x86-freebsd_8.0-rc1.tar.bz2) = c6d8d63c61b25f42c562097c7a46e333
+SHA256 (cmucl-20a-x86-freebsd_8.0-rc1.tar.bz2) =
876c20f390417b8f98d009ab604ff4b9787e9a201b222c3345b15431ef82e492
+SIZE (cmucl-20a-x86-freebsd_8.0-rc1.tar.bz2) = 16175907
___
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
Initial bsd.gnat.mk
Hello.
This is an initial version of 'bsd.gnat.mk'.
A user may set USE_GNAT to 'gnat-gcc' or 'gnat-gpl', currently.
gnat-gcc selects lang/gnat-gcc44 and gnat-gpl selects lang/gnat
as the Ada compiler used to compile ports.
I have made gnat-gcc the default as it supports more architectures
(I've been unable to get gnat-gpl to build on AMD64 as it seems to
specifically lack support for it).
As shown, GNAT_GCC_CFLAGS may also be set. These are optional
compiler flags (like CFLAGS).
--8---
#
# bsd.gnat.mk - GNAT Ada compiler selection.
#
#
# User settable knobs:
#
# Name Default value Description
# GNAT_GCC_CFLAGS(empty)Optional Ada compiler flags
#
GNAT_Include=bsd.gnat.mk
GNAT_Include_MAINTAINER= freebsd-po...@coreland.ath.cx
# Default case - a current lang/gnat-gcc port.
.if ${USE_GNAT} == yes || ${USE_GNAT} == gnat-gcc
BUILD_DEPENDS+= gnat-gcc44:${PORTSDIR}/lang/gnat-gcc44
RUN_DEPENDS+= gnat-gcc44:${PORTSDIR}/lang/gnat-gcc44
GNAT_GCC:= gcc44
GNAT_BIND:= gnatbind
GNAT_LINK:= gnatlink
# GNAT GPL port.
.elif ${USE_GNAT} == gnat-gpl
BUILD_DEPENDS+= gnat-gpl:${PORTSDIR}/lang/gnat
RUN_DEPENDS+= gnat-gpl:${PORTSDIR}/lang/gnat
GNAT_GCC:= gnatgcc
GNAT_BIND:= gnatbind
GNAT_LINK:= gnatlink
.else
IGNORE= specifies unknown value ${USE_GNAT} for USE_GNAT
.endif
test-gnat:
@echo USE_GCC=${USE_GCC}
@echo GNAT_GCC=${GNAT_GCC}
@echo BUILD_DEPENDS=${BUILD_DEPENDS}
@echo RUN_DEPENDS=${RUN_DEPENDS}
--8---
An example of a port using this makefile:
--8---
# New ports collection makefile for: sdl-ada
# Date created: 02 December 2009
# Whom: freebsd-po...@coreland.ath.cx
#
# $FreeBSD$
#
PORTNAME= sdl-ada
PORTVERSION=1.2.14
CATEGORIES= devel
MASTER_SITES= http://coreland.ath.cx/code/sdl-ada/src/
MAINTAINER= freebsd-po...@coreland.ath.cx
COMMENT=This is a set of Ada bindings to the SDL library.
USE_GNAT=yes
post-patch:
@${ECHO_CMD} ${GNAT_GCC}
${WRKSRC}/conf-adacomp
@${ECHO_CMD} ${GNAT_GCC_CFLAGS}
${WRKSRC}/conf-adacflags
@${ECHO_CMD} ${GNAT_BIND}
${WRKSRC}/conf-adabind
@${ECHO_CMD} ${GNAT_LINK}
${WRKSRC}/conf-adalink
@${ECHO_CMD} ${CC}
${WRKSRC}/conf-cc
@${ECHO_CMD} ${CFLAGS}
${WRKSRC}/conf-cflags
@${ECHO_CMD} ${LD}
${WRKSRC}/conf-ld
@${ECHO_CMD} ${PREFIX}/bin
${WRKSRC}/conf-bindir
@${ECHO_CMD} ${PREFIX}/include/coreland/sdl-ada
${WRKSRC}/conf-incdir
@${ECHO_CMD} ${PREFIX}/lib/coreland/sdl-ada-static
${WRKSRC}/conf-slibdir
@${ECHO_CMD} ${PREFIX}/lib/coreland/sdl-ada
${WRKSRC}/conf-dlibdir
@${ECHO_CMD} ${PREFIX}/share/coreland/sdl-ada-repos
${WRKSRC}/conf-repos
.if defined(DESTDIR)
@${ECHO_CMD} ${DESTDIR} ${WRKSRC}/conf-fakeroot
.endif
.include bsd.port.mk
--8---
Comments welcome.
M
___
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: portmaster: printing messages that do not come from pkg-message files
On Sat 02 Jan 2010 at 09:14:11 PST Julien Laffaye wrote: 2010/1/2 Nikola Le??i?? nikola.le...@anthesphoria.net: Hello, portmaster's feature to print collected pkg-message files after successful installation is very useful. However, there are many ports that echo messages from inside Makefile, usually in post-install phase (but not exclusively there). A simple question: would it be possible (or better, would it be desirable) to collect that text as well and to include it in the final output in the same way it is done with pkg-messages? Hi, It's better to correct these ports to make them use pkg-message, so it will be printed by portmaster *and* pkg_add (dont forget packages !) Sometimes whether a message is echoed depends on a knob. The porter's handbook includes examples of this. Is there a way to get the same effect with pkg-messages? ___ 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: portmaster: printing messages that do not come from pkg-message files
On Sat, Jan 02, 2010 at 01:11:38PM -0800, Charlie Kester wrote: On Sat 02 Jan 2010 at 09:14:11 PST Julien Laffaye wrote: 2010/1/2 Nikola Le??i?? nikola.le...@anthesphoria.net: Hello, portmaster's feature to print collected pkg-message files after successful installation is very useful. However, there are many ports that echo messages from inside Makefile, usually in post-install phase (but not exclusively there). A simple question: would it be possible (or better, would it be desirable) to collect that text as well and to include it in the final output in the same way it is done with pkg-messages? Hi, It's better to correct these ports to make them use pkg-message, so it will be printed by portmaster *and* pkg_add (dont forget packages !) Sometimes whether a message is echoed depends on a knob. The porter's handbook includes examples of this. Is there a way to get the same effect with pkg-messages? See devel/git for an example of displaying pkg-message depending upon a knob. I'm sure with a bit of creativity you could display only a portion of pkg-message depending upon a knob. -- WXS ___ 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: portmaster: printing messages that do not come from pkg-message files
Nikola Lečić wrote: Hello, portmaster's feature to print collected pkg-message files after successful installation is very useful. However, there are many ports that echo messages from inside Makefile, usually in post-install phase (but not exclusively there). A simple question: would it be possible (or better, would it be desirable) to collect that text as well and to include it in the final output in the same way it is done with pkg-messages? In a word, no. :) Random messages emitted by the port at random points in the process are evil (well, usually they are evil), and should not be encouraged. Messages related to build choices should be handled by OPTIONS, information that the user needs after the port is installed should be handled in the pkg-message. Portmaster has support for both of those. If you have something specific in mind, or specific examples of a port that emits something meaningful I'll be glad to take another look, but as a general principle my opinion is that using the established mechanisms is the better route to take. Doug PS, I'm glad you find the pkg-message feature useful. :) -- Improve the effectiveness of your Internet presence with a domain name makeover!http://SupersetSolutions.com/ Computers are useless. They can only give you answers. -- Pablo Picasso ___ 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: firefox35 crashes frequently and when run from the command line always look for libpthread.so.0
On Thu, Dec 31, 2009 at 9:46 AM, eculp ec...@encontacto.net wrote: Thanks Scot. I see the same: # ls -l /compat/linux/lib/libpthread* -rwxr-xr-x 1 root wheel 133456 Dec 29 08:23 /compat/linux/lib/libpthread-2.9.so lrwxrwxrwx 1 root wheel 17 Dec 29 08:34 /compat/linux/lib/libpthread.so.0 - libpthread-2.9.so # pkg_info -W /compat/linux/lib/libpthread.so.0 /compat/linux/lib/libpthread.so.0 was installed by package linux_base-f10-10_2 but when starting from a term window I now see: # firefox3 (firefox-bin:48016): GLib-WARNING **: g_set_prgname() called multiple times :1: error: unexpected number `9', expected keyword - e.g. `style' LoadPlugin: failed to initialize shared library /root/.mozilla/plugins/nppdf.so [/usr/local/lib/compat/libc.so.6: version GLIBC_2.1.3 required by /root/.mozilla/plugins/nppdf.so not defined] LoadPlugin: failed to initialize shared library /usr/local/lib/npapi/linux-f10-flashplugin/libflashplayer.so [Shared object libpthread.so.0 not found, required by libflashplayer.so] :1: error: unexpected number `9', expected keyword - e.g. `style' The change is because I have been using portmaster and testing pkg_debunk to find missing and stale files and rebuilding and trying to eliminate errors. I still have the libpthread.so.0 that won't go away and the flash plugin works fine. Just out of curiosity have you tried running firefox35 from a term window? I have firefox 3.6 beta installed, and when I had run it from a term window I didn't see any error messages. Scot ___ 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: portmaster: printing messages that do not come from pkg-message files
On Sat 02 Jan 2010 at 13:32:05 PST Wesley Shields wrote: On Sat, Jan 02, 2010 at 01:11:38PM -0800, Charlie Kester wrote: Sometimes whether a message is echoed depends on a knob. The porter's handbook includes examples of this. Is there a way to get the same effect with pkg-messages? See devel/git for an example of displaying pkg-message depending upon a knob. I'm sure with a bit of creativity you could display only a portion of pkg-message depending upon a knob. Thanks. I just checked the handbook again and couldn't find the examples I thought I had seen there. I'll take a look at devel/git. ___ 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: portmaster: printing messages that do not come from pkg-message files
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 On Sat, 02 Jan 2010 13:41:25 -0800 in 4b3fbd85.9090...@freebsd.org Doug Barton do...@freebsd.org wrote: Nikola Lečić wrote: Hello, portmaster's feature to print collected pkg-message files after successful installation is very useful. However, there are many ports that echo messages from inside Makefile, usually in post-install phase (but not exclusively there). A simple question: would it be possible (or better, would it be desirable) to collect that text as well and to include it in the final output in the same way it is done with pkg-messages? In a word, no. :) Random messages emitted by the port at random points in the process are evil (well, usually they are evil), and should not be encouraged. I see. I asked because the practice to emit such messages seems to be widespread and I cannot find any place where the Porters Handbook discourages it -- correct me if I am wrong. Messages related to build choices should be handled by OPTIONS, information that the user needs after the port is installed should be handled in the pkg-message. Portmaster has support for both of those. Yes, but port messages often tells what could have been done differently _before_; see below. If you have something specific in mind, or specific examples of a port that emits something meaningful I'll be glad to take another look, but as a general principle my opinion is that using the established mechanisms is the better route to take. editors/openoffice.org-*: the ports emit a lot of important info through files/Makefile.knobs; it would be nice to have these messages printed after the build; they are not about what should be done after the install, but about what *could* be done differently. multimedia/mplayer: the same thing, two important messages that should not be lost somewhere in a huge build log. net/quagga: big pre-everything and crucial post-install info. security/stunnel: again, crucial post-install info. databases/mysql60-server: everything that is important is echoed in advance. devel/tmake: an example of short post-install message -- is it worth adding pkg-message instead? Also, lang/php_doc www/apache22 www/moinmoin mail/squirrelmail Finally, not that important, but some my own ports have Makefile messages: textproc/scim-kmfl-imengine in pre-patch and other scim-kmfl-* ports in post-install; I never met any resistance by any committer in regard to that fact. I understand that these things could be handled by OPTIONS and pkg_message, but this is not the case. So, if this behaviour is considered definitely bad, maybe maintainers should be called to gradually adapt their ports accordingly (as Julien Laffaye suggested in his reply and as it was done in the past, e.g. for adding more DESKTOP_ENTRIES)? PS, I'm glad you find the pkg-message feature useful. :) Indeed, among many others. :-) Best wishes, - -- Nikola Lečić = Никола Лечић fingerprint : FEF3 66AF C90E EDC3 D878 7CDC 956D F4AB A377 1C9B -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.11 (FreeBSD) iJwEAQEDAAYFAks/33IACgkQ/MM/0rYIoZgs5wQAqtZw+Eo202UROBisv3cAQZTR ee7GbA+JTQ9UphbMhWQ+M65S2fysr+1Lo2VrE0RZ9QGWGQQXxljsbqFQXLOGzd2J mnwJypW8xHbB+10mA2xJ7HgFDtIV1yc3dsgU1wAK96OF4zWsaz/BLMUG/TSJM9Gb vfiVootdRYyhqzET10c= =oqBc -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: cvs commit: ports/devel/p5-Gearman-XS Makefile
The Restless Daemon identified a depend_object error while trying to build: p5-Gearman-XS-0.5 maintained by po...@freebsd.org Makefile ident: $FreeBSD: ports/devel/p5-Gearman-XS/Makefile,v 1.3 2010/01/03 07:26:54 linimon Exp $ Excerpt from http://QAT.TecNik93.com/logs/8-STABLE-NPD/p5-Gearman-XS-0.5.log : CCLD reverse_worker CC wc_worker.o CCLD wc_worker Making all in scripts Making all in support Making all in benchmark CC blobslap_client.o CC benchmark.o CCLD blobslap_client CC blobslap_worker.o CCLD blobslap_worker Making all in tests CC test.o CC test_gearmand.o CC test_worker.o CC client_test.o CCLD client_test CC worker_test.o CCLD worker_test CXXcpp_test.o CXXLD cpp_test CC memcached_test.o CCLD memcached_test === Installing for gearmand-0.11 === Generating temporary packing list === Checking if devel/gearmand already installed === gearmand-0.11 is already installed You may wish to ``make deinstall'' and install this port again by ``make reinstall'' to upgrade it properly. If you really wish to overwrite the old port of devel/gearmand without deleting it first, set the variable FORCE_PKG_REGISTER in your environment or the make install command line. *** Error code 1 Stop in /a/ports/devel/gearmand. *** Error code 1 Stop in /a/ports/devel/p5-Gearman-XS. build of /usr/ports/devel/p5-Gearman-XS ended at Sun Jan 3 07:28:46 UTC 2010 PortsMon page for the port: http://portsmon.freebsd.org/portoverview.py?category=develportname=p5-Gearman-XS The build which triggered this BotMail was done under tinderbox-3.3; dsversion: 3.2.1 on RELENG_8 on amd64, kern.smp.cpus: 8 with tinderd_flags=-nullfs -plistcheck -onceonly and ccache support, with the official up-to-date Ports Tree, with the following vars set: NOPORTDOCS=yes, NOPORTEXAMPLES=yes, NOPORTDATA=yes, FORCE_PACKAGE=yes. A description of the testing process can be found here: http://T32.TecNik93.com/FreeBSD/QA-Tindy/ Thanks for your work on making FreeBSD better, -- QAT - your friendly neighborhood Daemon, preparing a heck of an error trapping system: - HMC and EOI? - Halt, Melt and Catch fire or Execute Operator Immediately. ___ 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
