Re: FreeBSD Port: omnetpp-3.3_3
On Tuesday 11 August 2009 19:13:44 Gabriele Cecchetti wrote:
Probably there is an error in the Makefile of omnetpp:
When I do portupgrade at the install phase the following output is shown:
--- Installing the new version via the port
=== Installing for omnetpp-3.3_3
=== omnetpp-3.3_3 depends on executable: convert - found
=== omnetpp-3.3_3 depends on executable: dot - found
=== omnetpp-3.3_3 depends on executable: doxygen - found
=== omnetpp-3.3_3 depends on executable: giftrans - found
=== omnetpp-3.3_3 depends on file: /usr/local/bin/perl5.10.0 - found
=== omnetpp-3.3_3 depends on executable: pkg-config - found
=== omnetpp-3.3_3 depends on shared library: BLT24 - found
=== omnetpp-3.3_3 depends on shared library: tcl84 - found
=== omnetpp-3.3_3 depends on shared library: tk84 - found
=== omnetpp-3.3_3 depends on shared library: glib-12.3 - found
=== omnetpp-3.3_3 depends on shared library: xml.5 - found
=== omnetpp-3.3_3 depends on shared library: xml2.5 - found
=== omnetpp-3.3_3 depends on shared library: xslt.2 - found
cp: pkg-plist: No such file or directory
...
Having a working directory is legal and this is set putting the
following variable in /etc/make.conf
WRKDIRPREFIX= /somedir
FWIW, reproduced and ${.CURDIR} should be used (`pwd` at pre-install is
${.OBJDIR}).
--
Mel
Index: science/omnetpp/Makefile
===
RCS file: /home/ncvs/ports/science/omnetpp/Makefile,v
retrieving revision 1.12
diff -u -r1.12 Makefile
--- science/omnetpp/Makefile31 Jul 2009 13:55:36 - 1.12
+++ science/omnetpp/Makefile12 Aug 2009 06:21:49 -
@@ -82,7 +82,7 @@
@${ECHO} WISH=wish${TK_VER} ${CONFIGUREUSER}
pre-install:
- @${CP} pkg-plist ${PLIST}
+ @${CP} ${.CURDIR}/pkg-plist ${PLIST}
@(cd ${WRKSRC}; \
${FIND} -s include -type f | ${SED}
s,^include,${INCLDIR_REL}, ${PLIST}; \
${FIND} -s -d include -type d | ${SED} s,^include,@dirrm
${INCLDIR_REL}, ${PLIST}; \
___
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_add with NFS
В Tue, 11 Aug 2009 14:01:00 -0700 Robert travelin...@cox.net пишет: R Greetings R R A simple question from a simple mind. Or, at least a forgetful one. R R I am slowly moving the computers in my SOHO to FreeBSD 8 from R 7-stable. In order to be more efficient, I am using a faster server R as a source and ports server. R R The source portion is working as designed with the slower boxes able R to update simply with a make kernel, reboot, make installworld. R R I am exporting and then NFS mounting /usr/src, /usr/obj, R and /usr/ports. R R I had rebuilt all of my ports on the faster computer with R pagkage-recursive. I change the environment on the client box of R PACKAGESITE to /usr/ports/packages/ALL but when I try pkg_add I get R the error can't stat package file 'xorg'. Yes, the file R xorg-7blah.tbz does show at that location. R R I probably am forgetting something simple but my searches have not R triggered anything. R Hi, did you try `cd /path/to/packages/All pkg_add packagename` on NFS client(-s) ? R Thanks R R Robert -- wbr, tiger ___ 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
/usr/ports/dns/bind9-sdb-postgresql
Hi Mailing List, I cant find any manual for bind9 + postgresql. Questions: 1. does /usr/ports/dns/bind9-sdb-postgresql is capable of dynamic loadable zone (DLZ) 2. I updated my ports just now, It seems the makefile for /usr/ports/dns/bind9-dlz is not complete. or can you help out a bit. 3. Is there any share/examples for named and its schema for these ports? Best regards, Albert ___ 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
Aalib installation
Hi!
There is /usr/ports/graphics/aalib installation process log:
# make
=== Vulnerability check disabled, database not found
=== Extracting for aalib-1.4.r5_4
= MD5 Checksum OK for aalib-1.4rc5.tar.gz.
= SHA256 Checksum OK for aalib-1.4rc5.tar.gz.
=== Patching for aalib-1.4.r5_4
=== Applying FreeBSD patches for aalib-1.4.r5_4
=== aalib-1.4.r5_4 depends on file: /usr/local/libdata/pkgconfig/x11.pc -
found
=== aalib-1.4.r5_4 depends on file: /usr/local/bin/libtool - found
=== Configuring for aalib-1.4.r5_4
creating cache ./config.cache
checking for a BSD compatible install... /usr/bin/install -c -o root -g
wheel
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... yes
checking for working aclocal... found
checking for working autoconf... found
checking for working automake... found
checking for working autoheader... found
checking for working makeinfo... found
checking host system type... i386-portbld-freebsd7.2
checking target system type... i386-portbld-freebsd7.2
checking for gcc... cc
checking whether the C compiler (cc -O2 -fno-strict-aliasing -pipe )
works... yes
checking whether the C compiler (cc -O2 -fno-strict-aliasing -pipe ) is a
cross-compiler... no
checking whether we are using GNU C... yes
checking whether cc accepts -g... yes
checking build system type... i386-portbld-freebsd7.2
checking for ranlib... ranlib
checking for ld used by GCC... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
updating cache ./config.cache
ltconfig: `/usr/local/share/libtool/config/ltmain.sh' does not exist
Try `ltconfig --help' for more information.
configure: error: libtool configure failed
=== Script configure failed unexpectedly.
Please report the problem to po...@freebsd.org [maintainer] and attach the
/usr/ports/graphics/aalib/work/aalib-1.4.0/config.log including the output
of the failure of your make command. Also, it might be a good idea to
provide
an overview of all packages installed on your system (e.g. an `ls
/var/db/pkg`).
*** Error code 1
Stop in /usr/ports/graphics/aalib.
After I look at /usr/share/libtool and do not found config dir there, but
ltmain.sh file placed there.
Thanx.
Serebryakoff Alexey
___
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: SourceForge changing file distribution scheme!
* Glen Barber (glen.j.bar...@gmail.com) wrote: So, what do we do? May I commit the patch (+portmgr)? I believe this to be the best solution (even if a temporary one if we'll be able to resolve things with SF) as it will be clear which port uses the new scheme and there will be no variety of workarounds. Perhaps I've lost it in this thread, but is it only a certain amount of ports affected? It appears the two SF ports I maintain hiccup a bit, but are able to eventually find the distfile. This should only affect updating SF ports to new versions. I've checked your ports, they seem to fetch just fine. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amd...@amdmi3.ru ..: jabber: amd...@jabber.ruhttp://www.amdmi3.ru ___ 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: Aalib installation
Am Wed, 12 Aug 2009 19:45:53 +0700
schrieb karfagen agent_...@mail.ru:
Read UPDATING:
20090802:
AFFECTS: users of devel/libtool15 and devel/libltdl15
AUTHOR: m...@freebsd.org
The devel/libtool15 and devel/libltdl15 ports have been moved to
libtool22 and libltdl22, respectively, then updated to 2.2.6a. You
will need to run portmaster or portupgrade to properly perform the
upgrade:
Portmaster:
---
portmaster -o devel/libtool22 devel/libtool15
portmaster -o devel/libltdl22 devel/libltdl15
Portupgrade:
portupgrade -o devel/libtool22 libtool-1.5\*
portupgrade -o devel/libltdl22 libltdl-1.5\*
After that, you will need to rebuild all ports that depend on
libltdl. Since all dependent ports' PORTREVISIONs have been bumped,
you can run portupgrade or portmaster with '-a' to complete the
upgrade.
HTW
J.
Hi!
There is /usr/ports/graphics/aalib installation process log:
# make
=== Vulnerability check disabled, database not found
=== Extracting for aalib-1.4.r5_4
= MD5 Checksum OK for aalib-1.4rc5.tar.gz.
= SHA256 Checksum OK for aalib-1.4rc5.tar.gz.
=== Patching for aalib-1.4.r5_4
=== Applying FreeBSD patches for aalib-1.4.r5_4
=== aalib-1.4.r5_4 depends on
file: /usr/local/libdata/pkgconfig/x11.pc - found
=== aalib-1.4.r5_4 depends on file: /usr/local/bin/libtool - found
=== Configuring for aalib-1.4.r5_4
creating cache ./config.cache
checking for a BSD compatible install... /usr/bin/install -c -o root
-g wheel
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... yes
checking for working aclocal... found
checking for working autoconf... found
checking for working automake... found
checking for working autoheader... found
checking for working makeinfo... found
checking host system type... i386-portbld-freebsd7.2
checking target system type... i386-portbld-freebsd7.2
checking for gcc... cc
checking whether the C compiler (cc -O2 -fno-strict-aliasing -pipe )
works... yes
checking whether the C compiler (cc -O2 -fno-strict-aliasing -pipe )
is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether cc accepts -g... yes
checking build system type... i386-portbld-freebsd7.2
checking for ranlib... ranlib
checking for ld used by GCC... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
updating cache ./config.cache
ltconfig: `/usr/local/share/libtool/config/ltmain.sh' does not exist
Try `ltconfig --help' for more information.
configure: error: libtool configure failed
=== Script configure failed unexpectedly.
Please report the problem to po...@freebsd.org [maintainer] and
attach the /usr/ports/graphics/aalib/work/aalib-1.4.0/config.log
including the output of the failure of your make command. Also, it
might be a good idea to provide
an overview of all packages installed on your system (e.g. an `ls
/var/db/pkg`).
*** Error code 1
Stop in /usr/ports/graphics/aalib.
After I look at /usr/share/libtool and do not found config dir there,
but ltmain.sh file placed there.
Thanx.
Serebryakoff Alexey
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to
freebsd-ports-unsubscr...@freebsd.org
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Stop in /usr/ports/graphics/aalib
On Tue, Aug 11, 2009 at 09:44:11PM +0200, Jörgen Nilsson wrote:
bastion# uname -a
FreeBSD bastion.mordvap.net 7.2-RELEASE-p3 FreeBSD 7.2-RELEASE-p3 #1: Tue
Aug 11 19:19:21 CEST 2009
u...@bastion.host.net:/usr/obj/usr/src/sys/BASTION i386
checking whether ln -s works... (cached) yes
ltconfig: `/usr/local/share/libtool/config/ltmain.sh' does not exist
Try `ltconfig --help' for more information.
configure: error: libtool configure failed
=== Script configure failed unexpectedly.
[snip]
isc-dhcp30-server-3.0.7_4 libtool-1.5.26 pftop-0.7_1
^^
yasm-0.8.0
#
On Wed, Aug 12, 2009 at 07:45:53PM +0700, karfagen wrote:
Hi!
There is /usr/ports/graphics/aalib installation process log:
# make
=== Vulnerability check disabled, database not found
=== Extracting for aalib-1.4.r5_4
= MD5 Checksum OK for aalib-1.4rc5.tar.gz.
= SHA256 Checksum OK for aalib-1.4rc5.tar.gz.
=== Patching for aalib-1.4.r5_4
=== Applying FreeBSD patches for aalib-1.4.r5_4
=== aalib-1.4.r5_4 depends on file: /usr/local/libdata/pkgconfig/x11.pc -
found
=== aalib-1.4.r5_4 depends on file: /usr/local/bin/libtool - found
=== Configuring for aalib-1.4.r5_4
creating cache ./config.cache
checking for a BSD compatible install... /usr/bin/install -c -o root -g
wheel
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... yes
checking for working aclocal... found
checking for working autoconf... found
checking for working automake... found
checking for working autoheader... found
checking for working makeinfo... found
checking host system type... i386-portbld-freebsd7.2
checking target system type... i386-portbld-freebsd7.2
checking for gcc... cc
checking whether the C compiler (cc -O2 -fno-strict-aliasing -pipe )
works... yes
checking whether the C compiler (cc -O2 -fno-strict-aliasing -pipe ) is a
cross-compiler... no
checking whether we are using GNU C... yes
checking whether cc accepts -g... yes
checking build system type... i386-portbld-freebsd7.2
checking for ranlib... ranlib
checking for ld used by GCC... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
updating cache ./config.cache
ltconfig: `/usr/local/share/libtool/config/ltmain.sh' does not exist
Try `ltconfig --help' for more information.
configure: error: libtool configure failed
=== Script configure failed unexpectedly.
[snip]
Have you guys read entry 20090802 in /usr/ports/UPDATING?
HTH,
Alexey.
___
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: SourceForge changing file distribution scheme!
On Wed, Aug 12, 2009 at 10:03 AM, Dmitry Marakasovamd...@amdmi3.ru wrote: * Glen Barber (glen.j.bar...@gmail.com) wrote: So, what do we do? May I commit the patch (+portmgr)? I believe this to be the best solution (even if a temporary one if we'll be able to resolve things with SF) as it will be clear which port uses the new scheme and there will be no variety of workarounds. Perhaps I've lost it in this thread, but is it only a certain amount of ports affected? It appears the two SF ports I maintain hiccup a bit, but are able to eventually find the distfile. This should only affect updating SF ports to new versions. I've checked your ports, they seem to fetch just fine. In that case, do you have GNATS access to close the PR I recently filed because of SF fetch errors[1]? If not, I will post a followup to have it closed. Regards, [1] - http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/137597 -- Glen Barber ___ 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: SourceForge changing file distribution scheme!
* Glen Barber (glen.j.bar...@gmail.com) wrote: In that case, do you have GNATS access to close the PR I recently filed because of SF fetch errors[1]? If not, I will post a followup to have it closed. [1] - http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/137597 That one is the case, it was updated in Aug, so it needs to switch to the new scheme. Also, additional mirror is never a bad thing. I'll watch that PR and commit it if danfe@ timeouts. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amd...@amdmi3.ru ..: jabber: amd...@jabber.ruhttp://www.amdmi3.ru ___ 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: SourceForge changing file distribution scheme!
On Wed, Aug 12, 2009 at 12:01 PM, Dmitry Marakasovamd...@amdmi3.ru wrote: * Glen Barber (glen.j.bar...@gmail.com) wrote: In that case, do you have GNATS access to close the PR I recently filed because of SF fetch errors[1]? If not, I will post a followup to have it closed. [1] - http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/137597 That one is the case, it was updated in Aug, so it needs to switch to the new scheme. Also, additional mirror is never a bad thing. I'll watch that PR and commit it if danfe@ timeouts. Even better. :-) Thanks! -- Glen Barber ___ 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: apr-gdbm-db42 upgrade conflicting with libtool
On Tuesday 04 August 2009 08:10:53 N.J. Mann wrote:
In message 20090803155055.ga31...@titania.njm.me.uk,
N.J. Mann (n...@njm.me.uk) wrote:
In message 20090803125519.ga60...@twisted.net,
Troy (t...@twisted.net) wrote:
I was trying to upgrade apr-gdbm-db42-1.3.6.1.3.8 to 1.3.7.1.3.8 and
ran into the following error. My libtool was just upgraded to
libtool-2.2.6a so there may be a conflict there. Anyone have ideas?
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking for library containing strerror... none required
checking whether system uses EBCDIC... no
performing libtool configuration...
./configure: 9753: Syntax error: word unexpected (expecting ))
*** Error code 2
Stop in /usr/ports/devel/apr.
*** Error code 1
Stop in /usr/ports/devel/apr.
I am also having problems updating devel/apr. In my case it gets past
the configure stage and fails during the compile stage:
%
=== Building for apr-gdbm-db43-1.3.7.1.3.8
cd /usr/ports.workdir/usr/ports/devel/apr/work/apr-1.3.7; /usr/bin/env
TMPDIR=/home/njm/tmp TMPDIR=/home/njm/tmp SHELL=/bin/sh NO_LINT=YES
ACLOCAL=/usr/local/bin/aclocal-1.9 AUTOMAKE=/usr/local/bin/automake-1.9
AUTOMAKE_VERSION=19 AUTOCONF=/usr/local/bin/autoconf-2.62
AUTOHEADER=/usr/local/bin/autoheader-2.62
AUTOIFNAMES=/usr/local/bin/ifnames-2.62
AUTOM4TE=/usr/local/bin/autom4te-2.62
AUTORECONF=/usr/local/bin/autoreconf-2.62
AUTOSCAN=/usr/local/bin/autoscan-2.62
AUTOUPDATE=/usr/local/bin/autoupdate-2.62 AUTOCONF_VERSION=262
LIBTOOL=/usr/local/bin/libtool LIBTOOLIZE=/usr/local/bin/libtoolize
LIBTOOL_M4=/usr/local/share/aclocal/libtool.m4 PREFIX=/usr/local
LOCALBASE=/usr/local X11BASE=/usr/local MOTIFLIB=-L/usr/local/lib -lXm
-lXp LIBDIR=/usr/lib CC=cc CFLAGS=-O2 -fno-strict-aliasing -pipe
CXX=c++ CXXFLAGS=-O2 -fno-strict-aliasing -pipe
MANPREFIX=/usr/local BSD_INSTALL_PROGRAM=install -s -m 555
BSD_INSTALL_SCRIPT=install -m 555 BSD_INSTALL_DATA=install -m
444 BSD_INSTALL_ MAN=install -m 444 /usr/bin/make
/bin/sh /libtool --silent --mode=compile cc -O2 -fno-strict-aliasing
-pipe -DHAVE_CONFIG_H-I./include
-I/usr/ports.workdir/usr/ports/devel/apr/work/apr-1.3.7/include/arch/unix
-I./include/arch/unix
-I/usr/ports.workdir/usr/ports/devel/apr/work/apr-1.3.7/include/arch/unix
-I/usr/ports.workdir/usr/ports/devel/apr/work/apr-1.3.7/include -o
passwd/apr_getpass.lo -c passwd/apr_getpass.c touch
passwd/apr_getpass.lo
^
This is the why it fails. In the relevant makefile this is actually:
./build/apr_rules.mk:38:LIBTOOL=$(SHELL) $(top_builddir)/libtool
but top_buildir is not defined anywhere in the makefiles. If I set it
then everything works. If I change the line above to use top_blddir
instead of top_builddir it works.
So, why isn't it defined? I looked through the config files - I know
nothing about autoconf, automake, c., and found:
./config.log:17410:LIBTOOL='$(SHELL) $(top_builddir)/libtool'
./config.log:17611:top_builddir='/usr/ports.workdir/usr/ports/devel/apr/wor
k/apr-1.3.7'
Just got bitten by this too, amd64, 6.x in a jail, clean environment. I traced
it to building as normal user, root works. The tell tale is this:
buildconf: Using libtool.m4 at /usr/local/share/aclocal/libtool.m4.
./buildconf: cannot create build/libtool.m4: Permission denied
As a result, configure works with the provided libtool.m4 and things go
downhill from there.
The provided libtool.m4 is installed by libtoolize with 444 permissions. Thus:
cat $ltfile | sed -e 's/LIBTOOL=\(.*\)top_build/LIBTOOL=\1apr_build/' \
build/libtool.m4
fails for a normal user. The patch below sig fixes the issue.
--
Mel
--- /dev/null 2009-08-12 08:33:00.0 -0800
+++ devel/apr/files/patch-buildconf 2009-08-12 08:32:46.0 -0800
@@ -0,0 +1,11 @@
+--- apr-1.3.8/buildconf.orig2009-08-12 08:28:47.0 -0800
apr-1.3.8/buildconf 2009-08-12 08:31:45.0 -0800
+@@ -71,6 +71,7 @@
+
+ echo buildconf: Using libtool.m4 at ${ltfile}.
+
++rm -f build/libtool.m4
+ cat $ltfile | sed -e 's/LIBTOOL=\(.*\)top_build/LIBTOOL=\1apr_build/'
build/libtool.m4
+
+ # libtool.m4 from 1.6 requires ltsugar.m4
+
___
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: apr-gdbm-db42 upgrade conflicting with libtool
In message 200908120851.14642.mel.flynn+fbsd.po...@mailing.thruhere.net, Mel Flynn (mel.flynn+fbsd.po...@mailing.thruhere.net) wrote: Just got bitten by this too, amd64, 6.x in a jail, clean environment. I traced it to building as normal user, root works. The tell tale is this: buildconf: Using libtool.m4 at /usr/local/share/aclocal/libtool.m4. ./buildconf: cannot create build/libtool.m4: Permission denied As a result, configure works with the provided libtool.m4 and things go downhill from there. The provided libtool.m4 is installed by libtoolize with 444 permissions. Thus: cat $ltfile | sed -e 's/LIBTOOL=\(.*\)top_build/LIBTOOL=\1apr_build/' \ build/libtool.m4 fails for a normal user. The patch below sig fixes the issue. Your patch fixes it for me. Many thanks. Cheers, Nick. -- ___ 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
Multiple instances of Mailman on FreeBSD
I'm posting this to both the mailman-users list and the freebsd-ports list. I realize that not all follow-up will make it to both lists. I would like to set up multiple instances of Mailman on a FreeBSD 7- STABLE system with using Postfix. Looking at the ports Makefile, it appears that if I set MM_DIR=mailman/vhosts/domain-for-this-instance everything should work file (plus add FORCE_PACKAGE_REGISTER allow this second instance to be installed.) But when I do % cd /usr/ports/mail/mailman % sudo make -DMM_DIR=mailman/vhosts/lists.wilson-pta.org - DFORCE_PKG_REGISTER install It just installs in the default location, /usr/local/mailman And this paradoxical report of various settings $ sudo make MM_DIR=mailman/vhosts/lists.wilson-pta.org - DFORCE_PKG_REGISTER install === Found saved configuration for mailman-2.1.12 You may change the following build options: MM_USERNAME=mailman The username of the Mailman user. MM_USERID=91The user ID of the Mailman user. MM_GROUPNAME=mailmanThe group to which the Mailman user will belong. MM_GROUPID=MM_USERIDThe group ID for the Mailman user. MM_DIR=mailman Mailman will be installed in /usr/local/mailman/vhosts/ lists.wilson-pta.org. CGI_GID=www The group name or id under which your web server executes CGI scripts. IMGDIR=www/iconsIcon images will be installed in /usr/local/www/icons. Notice the conflicting information on the line telling me about MM_DIR. Background on the issue As is well known to mailman users, mailman 2.X does not fully deal with virtual mail domains in that, say pta-bo...@lists.shepard-families.org And pta-bo...@lists.wilson-pta.org would have to be the same list. That is mailman does not provide a separate namespace for lists in different domains. The Wiki/FAQ at http://wiki.list.org/pages/viewpage.action?pageId=4030604 hints at patches (which I can't seem to locate) and mailing list discussion mentions an alternative of having a separate instance of Mailman for each virtual domain. This later approach seems easier if you don't anticipate having loads of domains. So that is what I intend to do. Cheers, -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ ___ 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: SourceForge changing file distribution scheme!
On Tue, Aug 11, 2009 at 07:55:00PM +0400, Dmitry Marakasov wrote: * Erwin Lansing (er...@freebsd.org) wrote: I've noticed that SF is changing file distribution scheme significantly, and I guess that will affect many ports and maybe infrastructure. I fear the same, unfortunately. However, I haven't as yet been able to identify a consistency in the new scheme. There can also be very weird subdir names: :-( http://downloads.sourceforge.net/project/tvbrowser/TV-Browser (Java 5 and higher)/2.7.4/tvbrowser-2.7.4.tar.gz pgpqr87M1qoC7.pgp Description: PGP signature
Re: [Mailman-Users] Multiple instances of Mailman on FreeBSD
Jeffrey Goldberg wrote: I'm posting this to both the mailman-users list and the freebsd-ports list. I realize that not all follow-up will make it to both lists. I would like to set up multiple instances of Mailman on a FreeBSD 7-STABLE system with using Postfix. Looking at the ports Makefile, it appears that if I set MM_DIR=mailman/vhosts/domain-for-this-instance everything should work file (plus add FORCE_PACKAGE_REGISTER allow this second instance to be installed.) Personally, I wouldn't use the ports version if you want to do multiple instances of Mailman. I would install each version from our official source tarballs that you can download from www.list.org and ftp.gnu.org. Alternatively, if you want to use the ports version, then I would keep it simple and serve only one domain. Otherwise, I would recommend that you find the port maintainer for Mailman, and discuss this subject with them. Hopefully, they would know enough about both sides of the problem to be able to recommend a solution or patch for you. -- Brad Knowles b...@shub-internet.org LinkedIn Profile: http://tinyurl.com/y8kpxu ___ 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: SourceForge changing file distribution scheme!
On Wed, Aug 12, 2009 at 3:16 PM, Lars Engelslars.eng...@0x20.net wrote: On Tue, Aug 11, 2009 at 07:55:00PM +0400, Dmitry Marakasov wrote: * Erwin Lansing (er...@freebsd.org) wrote: I've noticed that SF is changing file distribution scheme significantly, and I guess that will affect many ports and maybe infrastructure. I fear the same, unfortunately. However, I haven't as yet been able to identify a consistency in the new scheme. There can also be very weird subdir names: :-( http://downloads.sourceforge.net/project/tvbrowser/TV-Browser (Java 5 and higher)/2.7.4/tvbrowser-2.7.4.tar.gz If it helps any, I can host the weird-named distfiles on my site. Let me know if you would like me to do so. -- Glen Barber ___ 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: [Mailman-Users] Multiple instances of Mailman on FreeBSD
On Aug 12, 2009, at 2:12 PM, Brad Knowles wrote: Jeffrey Goldberg wrote: I would like to set up multiple instances of Mailman on a FreeBSD 7- STABLE system with using Postfix. Personally, I wouldn't use the [FreeBSD] ports version if you want to do multiple instances of Mailman. I would install each version from our official source tarballs that you can download from www.list.org and ftp.gnu.org. The FreeBSD Ports version contains a couple of patches which might be useful, though some are merely cosmetic. It also knows how to find the right gid and uid for working with various MTAs. Postfix, as we know, is finicky, and this port really does help people get it right. Otherwise, I would recommend that you find the port maintainer for Mailman, and discuss this subject with them. Already on the cc-line Anyway, what I have found is that if I manually edit the ports/mail/ mailman/Makefile to change #MM_DIR?= mailman MM_DIR?=mailman/vhosts/lists.wilson-pta.org The install works as expected, even though when I specified -DMM_DIR on the command line it worked for some purposes (built files contained the correct string in them) but not for other purposes (the files installed in the wrong place). So I suspect that the install stage must re-read the Makefile. So I do now have this other instance installed. One thing that I (and others doing things this way) will have to take care of is the startup script, /usr/local/etc/rc.d/mailman, for the queue runner. This installation did overwrite the original. So I'm either going to have to manually combine these in one startup script or set up a separate script for each instance. I'm sure that there will be other things to watch out for as well. I hope to contribute to the Wiki on this once I've got everything running. Let me just say that I am eagerly looking forward to Mailman 3. Cheers, -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ ___ 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: SourceForge changing file distribution scheme!
On Tue, Aug 11, 2009 at 05:56:49PM +0200, Hans F. Nordhaug wrote: Hi Hans, I guess many of you have projects on SF and know this already, but the changes is part of the new easy-to-use File Release System. Read more http://sourceforge.net/apps/trac/sourceforge/wiki/Release%20files%20for%20download Regarding the structure of existing packages/releases - quoting http://sourceforge.net/apps/wordpress/sourceforge/2009/07/22/file-release-system-frs-update-complete-2009-07-22/ We have also converted existing FRS data into a simple hierarchy based on existing package and release names. If you contact Daniel Hinojosa (Sr. Manager, SourceForge.net) he will probably tell you how the conversion is done for existing packages. For new packages/releases there is no pattern - it's up to every package maintainer to decide the directory structure. In other words, the project/whatever/whatever/ must be set in each port - not just the filename. Excellent, that explains a lot! Thanks. -erwin -- Erwin Lansing http://droso.org Prediction is very difficult especially about the futureer...@freebsd.org pgpirAc9YqWZE.pgp Description: PGP signature
Re: SourceForge changing file distribution scheme!
On Tue, Aug 11, 2009 at 07:41:03PM +0400, Dmitry Marakasov wrote: * Dmitry Marakasov (amd...@amdmi3.ru) wrote: Here's the patch I propose. Unfortunately, there's no way to guess MASTER_SITE_SUBDIR (examples: http://sunet.dl.sourceforge.net/project/maxima/Maxima-source/5.19.0-source/maxima-5.19.0.tar.gz http://sunet.dl.sourceforge.net/project/lam/LAM/2.7.0/ldap-account-manager-2.7.0.tar.gz ) so for SFNEW it should be always set in the port. I've just committed a slightly modified version based on a combination of your and Sylvio Cesar's patch I received. The SFP (SourceForge Project) name for the macro is a bit more descriptive than just new. It also readds the garr mirror. Looking at the link Hans send earlier in this thread, it is clear that the subdirectory under /project/ is now individual to each project, so you're right that it has to be set explicitly for every port now, unfortunately, although I've kept the default value. Thanks to all for working on this! -erwin -- Erwin Lansing http://droso.org Prediction is very difficult especially about the futureer...@freebsd.org pgpx75Qw82CRr.pgp Description: PGP signature
Re: Multiple instances of Mailman on FreeBSD
In response to Jeffrey Goldberg jeff...@goldmark.org: I'm posting this to both the mailman-users list and the freebsd-ports list. I realize that not all follow-up will make it to both lists. I would like to set up multiple instances of Mailman on a FreeBSD 7- STABLE system with using Postfix. Looking at the ports Makefile, it appears that if I set MM_DIR=mailman/vhosts/domain-for-this-instance everything should work file (plus add FORCE_PACKAGE_REGISTER allow this second instance to be installed.) Were it me, I'd add jails to the system. Then you can install a separate copy of mailman in each jail. This will keep them happily independent of each other. That's obviously not the only way to get what you want, just my suggestion. -- Bill Moran http://www.potentialtech.com http://people.collaborativefusion.com/~wmoran/ ___ 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: SourceForge changing file distribution scheme!
Thank you Edwin for considering a some of my patch, I am pleased to contribute to FreeBSD and especially when the contribution is well accepted and applied. Regards, Sylvio César. 2009/8/12 Erwin Lansing er...@freebsd.org: On Tue, Aug 11, 2009 at 07:41:03PM +0400, Dmitry Marakasov wrote: * Dmitry Marakasov (amd...@amdmi3.ru) wrote: Here's the patch I propose. Unfortunately, there's no way to guess MASTER_SITE_SUBDIR (examples: http://sunet.dl.sourceforge.net/project/maxima/Maxima-source/5.19.0-source/maxima-5.19.0.tar.gz http://sunet.dl.sourceforge.net/project/lam/LAM/2.7.0/ldap-account-manager-2.7.0.tar.gz ) so for SFNEW it should be always set in the port. I've just committed a slightly modified version based on a combination of your and Sylvio Cesar's patch I received. The SFP (SourceForge Project) name for the macro is a bit more descriptive than just new. It also readds the garr mirror. Looking at the link Hans send earlier in this thread, it is clear that the subdirectory under /project/ is now individual to each project, so you're right that it has to be set explicitly for every port now, unfortunately, although I've kept the default value. Thanks to all for working on this! -erwin -- Erwin Lansing http://droso.org Prediction is very difficult especially about the future er...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Multiple instances of Mailman on FreeBSD
On Wednesday 12 August 2009 11:40:47 Bill Moran wrote: In response to Jeffrey Goldberg jeff...@goldmark.org: I'm posting this to both the mailman-users list and the freebsd-ports list. I realize that not all follow-up will make it to both lists. I would like to set up multiple instances of Mailman on a FreeBSD 7- STABLE system with using Postfix. Looking at the ports Makefile, it appears that if I set MM_DIR=mailman/vhosts/domain-for-this-instance everything should work file (plus add FORCE_PACKAGE_REGISTER allow this second instance to be installed.) Were it me, I'd add jails to the system. Then you can install a separate copy of mailman in each jail. This will keep them happily independent of each other. That's obviously not the only way to get what you want, just my suggestion. And mine. FORCE_PKG_REGISTER abuse will hurt you sooner or later. If you must, then set PKG_DBDIR, PORT_DBDIR and PREFIX correctly. But things get much easier if you use seperate jails and a postfix in mailhub mode on the main IP if you have only one incoming IP. -- Mel ___ 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: Multiple instances of Mailman on FreeBSD
On Aug 12, 2009, at 3:21 PM, Paul Schmehl wrote:
--On Wednesday, August 12, 2009 13:55:18 -0500 Jeffrey Goldberg jeff...@goldmark.org
wrote:
I'm posting this to both the mailman-users list and the freebsd-ports
list. I realize that not all follow-up will make it to both lists.
But when I do
% cd /usr/ports/mail/mailman
% sudo make -DMM_DIR=mailman/vhosts/lists.wilson-pta.org -
DFORCE_PKG_REGISTER install
It just installs in the default location, /usr/local/mailman
This could be a really stupid question (because I've never tried to
do what you're doing), but shouldn't the above line be:
$ sudo make MM_DIR=/mailman/vhosts/lists.wilson-pta.org
In other words, don't you have to provide the *absolute* patch to
the install location?
No. Reading the Makefile it is clear that MM_DIR is relative to $PREFIX
The default setting in the Makefile is
MM_DIR?= mailman
And later on there is a
MAILMANDIR= ${PREFIX}/${MM_DIR}
With MAILMANDIR being the absolute install directory.
The problem is, I'm not exactly sure *where* you want mailman to
install, so it's hard to be correct without more information.
Mailman (under normal defaults) installs in various directories under
/usr/local/mailman
The python for all of the CGIs lives in
/usr/local/mailman/Mailman
and the programs that an administrator might run on the command line
live in
/usr/local/mailmain/bin
And there are various other directories for queues and logs and data
and per list configurations and such
I want to have instances installed in
/usr/local/mailman/vhosts/site1
/usr/local/mailman/vhosts/site2
/usr/local/mailman/vhosts/site3
Cheers,
-j
--
Jeffrey Goldberghttp://www.goldmark.org/jeff/
___
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: Multiple instances of Mailman on FreeBSD
--On Wednesday, August 12, 2009 13:55:18 -0500 Jeffrey Goldberg jeff...@goldmark.org wrote: I'm posting this to both the mailman-users list and the freebsd-ports list. I realize that not all follow-up will make it to both lists. I would like to set up multiple instances of Mailman on a FreeBSD 7- STABLE system with using Postfix. Looking at the ports Makefile, it appears that if I set MM_DIR=mailman/vhosts/domain-for-this-instance everything should work file (plus add FORCE_PACKAGE_REGISTER allow this second instance to be installed.) But when I do % cd /usr/ports/mail/mailman % sudo make -DMM_DIR=mailman/vhosts/lists.wilson-pta.org - DFORCE_PKG_REGISTER install It just installs in the default location, /usr/local/mailman And this paradoxical report of various settings $ sudo make MM_DIR=mailman/vhosts/lists.wilson-pta.org - This could be a really stupid question (because I've never tried to do what you're doing), but shouldn't the above line be: $ sudo make MM_DIR=/mailman/vhosts/lists.wilson-pta.org In other words, don't you have to provide the *absolute* patch to the install location? In addition, I would think you would need to change PREFIX as well for the port to install where you want it to. So, ISTM, you should be doing this: $ sudo make PREFIX=/usr/local/mailman/vhost/lists.wilson-pta.org -DFORCE_PKG_REGISTER install rather than trying to set MM_DIR. Note you may *also* have to set MM_DIR, but I'm almost certain you need to set PREFIX if you want the port to install there instead of /usr/local/mailman. The problem is, I'm not exactly sure *where* you want mailman to install, so it's hard to be correct without more information. -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead. Thomas Jefferson ___ 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: Multiple instances of Mailman on FreeBSD
On Aug 12, 2009, at 3:38 PM, Mel Flynn wrote: On Wednesday 12 August 2009 11:40:47 Bill Moran wrote: Were it me, I'd add jails to the system. [...] That's obviously not the only way to get what you want, just my suggestion. And mine. Thank you and Bill for the jail suggestion. I've never played with jails, as I really only have one public IP address available. FORCE_PKG_REGISTER abuse will hurt you sooner or later. I am living in fear of that. If you must, then set PKG_DBDIR, PORT_DBDIR and PREFIX correctly. I don't understand the Package and Port databases well enough to actually set them correctly, so I do suspect that I am causing trouble for myself this way. But things get much easier if you use seperate jails and a postfix in mailhub mode on the main IP if you have only one incoming IP. Ah. I hadn't thought of that. I do only have one IP. I hadn't realized that I could set up private addresses on the same host. Would the postfix on the main IP be able to run scripts that are on individual jails? If not, I'd have to set up a listening postfix in each jail which would accept mail forwarded to it only from the main IP. For outgoing mail, mailman can talk SMTP to a remote mail server. Another point of confusion with jails is that the HTTP interface for mailman would need to be on the public IP, but would need to access the appropriate mailman data that live within jails. So I really think that unless I can do full jails, each with their own SMTP and HTTP daemons on their own public IPs, this would be very complicated to maintain. But I am only guessing here as I don't really know what can and can't be done easily with jails. Cheers, -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ ___ 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: ImageMagick-6.5.4.10
I updated my ports today, but ImageMagick has a build break... ___ 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: ImageMagick-6.5.4.10
I updated my ports today, but I experienced a build break in the new version of ImageMagick... ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD Port: ImageMagick-6.5.4.10
On Wednesday 12 August 2009 16:29:50 Steven Friedrich wrote: I updated my ports today, but I experienced a build break in the new version of ImageMagick... ___ 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 Yes, you are right and I have a problem at this momemnt ): -- Mitja - http://starikarp.redbubble.com ___ 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: Multiple instances of Mailman on FreeBSD
On Wed, 12 Aug 2009 15:41:19 -0500
Jeffrey Goldberg jeff...@goldmark.org wrote:
On Aug 12, 2009, at 3:21 PM, Paul Schmehl wrote:
--On Wednesday, August 12, 2009 13:55:18 -0500 Jeffrey Goldberg
jeff...@goldmark.org
wrote:
I'm posting this to both the mailman-users list and the freebsd-ports
list. I realize that not all follow-up will make it to both lists.
But when I do
% cd /usr/ports/mail/mailman
% sudo make -DMM_DIR=mailman/vhosts/lists.wilson-pta.org -
DFORCE_PKG_REGISTER install
It just installs in the default location, /usr/local/mailman
This could be a really stupid question (because I've never tried to
do what you're doing), but shouldn't the above line be:
$ sudo make MM_DIR=/mailman/vhosts/lists.wilson-pta.org
In other words, don't you have to provide the *absolute* patch to
the install location?
No. Reading the Makefile it is clear that MM_DIR is relative to $PREFIX
The default setting in the Makefile is
MM_DIR?= mailman
And later on there is a
MAILMANDIR= ${PREFIX}/${MM_DIR}
With MAILMANDIR being the absolute install directory.
The problem is, I'm not exactly sure *where* you want mailman to
install, so it's hard to be correct without more information.
Mailman (under normal defaults) installs in various directories under
/usr/local/mailman
The python for all of the CGIs lives in
/usr/local/mailman/Mailman
and the programs that an administrator might run on the command line
live in
/usr/local/mailmain/bin
And there are various other directories for queues and logs and data
and per list configurations and such
I want to have instances installed in
/usr/local/mailman/vhosts/site1
/usr/local/mailman/vhosts/site2
/usr/local/mailman/vhosts/site3
Cheers,
-j
--
Jeffrey Goldberghttp://www.goldmark.org/jeff/
Can you not just ( cp -r /usr/local/mailman /path/to/vhost/staging ) edit some
of the paths and then just host it. How many of the files are you actually
required to edit ?. If this will be a continual process it might be better off
to rsync your master mailman directory to all the separate vhosts obviously
skipping configs and list directories and then scripting out the exact changes
you need to make up creation of a new vhost.
Best regards.
:wq
--
Jason J. Hellenthal
+1.616.403.8065
jas...@dataix.net
___
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: Multiple instances of Mailman on FreeBSD
Jeffrey Goldberg wrote: On Aug 12, 2009, at 3:38 PM, Mel Flynn wrote: On Wednesday 12 August 2009 11:40:47 Bill Moran wrote: Were it me, I'd add jails to the system. [...] That's obviously not the only way to get what you want, just my suggestion. And mine. Thank you and Bill for the jail suggestion. I've never played with jails, as I really only have one public IP address available. You could assign each jail an RFC 1918 private address and perform NAT for them on the host system. I do this with PF and it works like a charm. -Boris FORCE_PKG_REGISTER abuse will hurt you sooner or later. I am living in fear of that. If you must, then set PKG_DBDIR, PORT_DBDIR and PREFIX correctly. I don't understand the Package and Port databases well enough to actually set them correctly, so I do suspect that I am causing trouble for myself this way. But things get much easier if you use seperate jails and a postfix in mailhub mode on the main IP if you have only one incoming IP. Ah. I hadn't thought of that. I do only have one IP. I hadn't realized that I could set up private addresses on the same host. Would the postfix on the main IP be able to run scripts that are on individual jails? If not, I'd have to set up a listening postfix in each jail which would accept mail forwarded to it only from the main IP. For outgoing mail, mailman can talk SMTP to a remote mail server. Another point of confusion with jails is that the HTTP interface for mailman would need to be on the public IP, but would need to access the appropriate mailman data that live within jails. So I really think that unless I can do full jails, each with their own SMTP and HTTP daemons on their own public IPs, this would be very complicated to maintain. But I am only guessing here as I don't really know what can and can't be done easily with jails. Cheers, -j ___ 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
ImageMagick 6.5.4.10
Update to 6.5.4.10 on FreeBSD 7.2 magick/.libs/libMagickCore.so: undefined reference to `carg' *** Error code 1 magick/.libs/libMagickCore.so: undefined reference to `carg' *** Error code 1 2 errors *** Error code 2 1 error *** Error code 1 Stop in /usr/ports/graphics/ImageMagick. *** Error code 1 Stop in /usr/ports/graphics/ImageMagick. === make failed for graphics/ImageMagick === Aborting update -- Mitja - http://starikarp.redbubble.com ___ 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
SpamAssassin - reinstall removes GPG keys
Every time SpamAssassin is upgraded or rebuilt, the sa-learn keyring directory gets removed during the pkg_delete. Is there a good reason for this? Is there a workaround? Specifying an alternate directory as an option to sa-learn seems a bit clumsy. ___ 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: ImageMagick 6.5.4.10
On Wed, 12 Aug 2009 20:11:20 -0500 ajtiM lum...@gmail.com wrote: Update to 6.5.4.10 on FreeBSD 7.2 magick/.libs/libMagickCore.so: undefined reference to `carg' *** Error code 1 magick/.libs/libMagickCore.so: undefined reference to `carg' *** Error code 1 2 errors *** Error code 2 1 error *** Error code 1 Stop in /usr/ports/graphics/ImageMagick. *** Error code 1 Stop in /usr/ports/graphics/ImageMagick. === make failed for graphics/ImageMagick === Aborting update -- Mitja - http://starikarp.redbubble.com I have just built this as of the last 5 minutes with no problems. I am using all but three configure options... [ ] IMAGEMAGICK_TESTSRun bundled self-tests after build [ ] IMAGEMAGICK_OPENMP OpenMP for SMP (needs threads) [ ] IMAGEMAGICK_HDRI High Dynamic Range Images (HDRI) -- Jason J. Hellenthal +1.616.403.8065 jas...@dataix.net ___ 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: ImageMagick 6.5.4.10
On Wed, 12 Aug 2009, Jason J. Hellenthal wrote:
On Wed, 12 Aug 2009 20:11:20 -0500
ajtiM lum...@gmail.com wrote:
Update to 6.5.4.10 on FreeBSD 7.2
magick/.libs/libMagickCore.so: undefined reference to `carg'
*** Error code 1
Try this patch:
diff -u magick/fourier-orig.c magick/fourier.c
--- magick/fourier-orig.c 2009-08-13 02:39:18.0 +
+++ magick/fourier.c2009-08-13 02:40:13.0 +
@@ -515,7 +515,7 @@
for (x=0L; x (long) fourier_info-center; x++)
{
magnitude[i]=cabs(fourier[i]);
-phase[i]=carg(fourier[i]);
+phase[i]=atan2(cimag(fourier[i]),creal(fourier[i]));
i++;
}
else
___
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: ImageMagick 6.5.4.10
On Wed, 12 Aug 2009, Jason J. Hellenthal wrote: On Wed, 12 Aug 2009 20:11:20 -0500 ajtiM lum...@gmail.com wrote: Update to 6.5.4.10 on FreeBSD 7.2 magick/.libs/libMagickCore.so: undefined reference to `carg' *** Error code 1 magick/.libs/libMagickCore.so: undefined reference to `carg' *** Error code 1 2 errors *** Error code 2 1 error *** Error code 1 Stop in /usr/ports/graphics/ImageMagick. *** Error code 1 Stop in /usr/ports/graphics/ImageMagick. === make failed for graphics/ImageMagick === Aborting update -- Mitja - http://starikarp.redbubble.com I have just built this as of the last 5 minutes with no problems. My experience is that it built just fine on FreeBSD-8 with amd64, but failed with the above error under FreeBSD-7.2 with i386. ___ 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: ImageMagick 6.5.4.10
On Wed, 12 Aug 2009 21:44:39 -0500 (CDT)
Stephen Montgomery-Smith step...@missouri.edu wrote:
On Wed, 12 Aug 2009, Jason J. Hellenthal wrote:
On Wed, 12 Aug 2009 20:11:20 -0500
ajtiM lum...@gmail.com wrote:
Update to 6.5.4.10 on FreeBSD 7.2
magick/.libs/libMagickCore.so: undefined reference to `carg'
*** Error code 1
Try this patch:
diff -u magick/fourier-orig.c magick/fourier.c
--- magick/fourier-orig.c 2009-08-13 02:39:18.0 +
+++ magick/fourier.c2009-08-13 02:40:13.0 +
@@ -515,7 +515,7 @@
for (x=0L; x (long) fourier_info-center; x++)
{
magnitude[i]=cabs(fourier[i]);
-phase[i]=carg(fourier[i]);
+phase[i]=atan2(cimag(fourier[i]),creal(fourier[i]));
i++;
}
else
I conclude this fixes the problem on 7.2-RELEASE-p3/i386 Non-SMP
--
Jason J. Hellenthal
+1.616.403.8065
jas...@dataix.net
___
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: ImageMagick 6.5.4.10
On Wed, 12 Aug 2009, Jason J. Hellenthal wrote:
On Wed, 12 Aug 2009 21:44:39 -0500 (CDT)
Stephen Montgomery-Smith step...@missouri.edu wrote:
On Wed, 12 Aug 2009, Jason J. Hellenthal wrote:
On Wed, 12 Aug 2009 20:11:20 -0500
ajtiM lum...@gmail.com wrote:
Update to 6.5.4.10 on FreeBSD 7.2
magick/.libs/libMagickCore.so: undefined reference to `carg'
*** Error code 1
Try this patch:
diff -u magick/fourier-orig.c magick/fourier.c
--- magick/fourier-orig.c 2009-08-13 02:39:18.0 +
+++ magick/fourier.c2009-08-13 02:40:13.0 +
@@ -515,7 +515,7 @@
for (x=0L; x (long) fourier_info-center; x++)
{
magnitude[i]=cabs(fourier[i]);
-phase[i]=carg(fourier[i]);
+phase[i]=atan2(cimag(fourier[i]),creal(fourier[i]));
i++;
}
else
I conclude this fixes the problem on 7.2-RELEASE-p3/i386 Non-SMP
I submitted the fix at ports/137712
The function carg seems to have been introduced in FreeBSD 8. If you look
inside /usr/src/lib/msun/src/s_carg.c (on a machine with FreeBSD 8) you
will see that the replacement I provided provides EXACTLY the same
functionality.
___
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
