Re: ports installation location
On 3/29/07, Vizion [EMAIL PROTECTED] wrote:
How does one specify a non-standard location for installing a port?
For example I want to have multiple instances of www/joomla installed for
multiple virtual hosts. How can I best go about this?
I haven't tried this, but looking at the ports Makefile, it looks like
you can install it to multiple locations as follows:
cd /usr/ports/www/joomla
sed -i'' -e [EMAIL PROTECTED]/[EMAIL PROTECTED]@ pkg-plist
make PKGNAMESUFFIX=_vh1 JOOMLA_DIR=www/joomla_vh1 install
The sed is required to fix the pkg-plist, as it hardcodes the install
directory to www/joomla (PR sent).
How about upgrades?
You would have to upgrade it manually, by first deleting the port, and
then using the same make comand that you used to install it.
To use port management tools (portmaster, portupgrade, ...), you would
need to create a port for each virtual host as following:
- create www/joomla_vh1 directory
- create www/joomla_vh1/Makefile
# port for virtual host: X
#
PKGNAMESUFFIX= _vh1
MASTERDIR= ${.CURDIR}/../joomla
JOOMLA_DIR= www/joomla${PKGNAMESUFFIX}
.include ${MASTERDIR}/Makefile
--
DISCLAIMER:
No electrons were mamed while sending this message. Only slightly bruised.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ClamAV rc.subr problem on 4.9
On 3/27/07, Matt Sealey [EMAIL PROTECTED] wrote: I just noticed that the ClamAV start/stop scripts on FreeBSD 4.9 include /etc/rc.subr which doesn't actually exist. The dependency on 4.9 lives in /usr/local/etc like everything else that isn't part of the base system. The FreeBSD ports collection no longer supports FreeBSD 4.x as of 2007.01.08.00.00.33 due to 4.x has been EOL'd. You'll need to down grade your ports collection to RELEASE_4_EOL which was the last ports collection verified to build on FreeBSD 4.x. cd /usr/ports cvs -q update -P -d -r RELEASE_4_EOL Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsnap and local patches
On 3/14/07, Nate Eldredge [EMAIL PROTECTED] wrote: Hi all, portsnap is a very nice way to keep your ports tree in sync, but it has the disadvantage that it keeps your ports tree in sync :) If you make local changes (e.g. adding a patch) they get clobbered. Does anyone know of a convenient way to keep ports up to date while preserving local patches? One way to keep your local changes is to use cvs to checkout and update the ports tree, you then make your modifications to the port. You will need to fix any conflicts manually between an updated port and your changes. Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: as for f-prot
On 3/8/07, Jordi Moles [EMAIL PROTECTED] wrote: hi. I've been using f-prot for some time. I installed it from the ports tree. I would now like to use it as a daemon service but i just don't get it working. I've found in google many links which talk about f-protd, but there's no such thing as that in my system. I haven't found any site where i could download a version of a f-prot for FreeBSD, bearing in mind that i want it runing as a daemon. Could you just tell me if there is a daemon version of f-prot for freebsd? You need to install F-PROT Antivirus FreeBSD Mail Server 4.6.7 from: http://www.f-prot.com/download/trial/ http://files.f-prot.com/files/bsd-x86/trial/fp-freebsd-ms.trial.tar.gz Or you can use the attached f-protd port, but note that it has a restrictive 60 day evaluation license. Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Python and gramps...
On 2/25/07, Chuck Swiger [EMAIL PROTECTED] wrote: Anders Troback wrote: On Fri, 23 Feb 2007 14:58:21 -0800 Chuck Swiger [EMAIL PROTECTED] wrote: [ ... ] I think you need to choose a particular flavor of BDB which is recent enough to support these log capabilities; try setting something like these in /etc/make.conf: WITH_BERKELEYDB=db42 WITH_BDB_VER=42 ...or choose some other recent 4.x version, and then try reinstalling /usr/ports/databases/py-bsddb. Yes, thanks that did it! Ah, very good. You're welcome. How do I reflect this in my port? Many ports do something like check whether WITH_BDB_VER is defined to something in order to register a properly dependency. If you can figure out which versions of BDB are supported with your software, then you error with a warning if too old a version is chosen, or you can do something like choose a reasonable default value if none is already set All you need to do is add the following to the port: USE_BDB= 42+ INVALID_BDB_VER= 2 3 40 41 And it will give an error if WITH_BDB_VER is set to a value lower than 42. Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD Port: subversion config
On 2/10/07, Marcus Ahlberg [EMAIL PROTECTED] wrote: Yesterday when I upgraded subversion from 1.4.2 to 1.4.3 with portupgrade I noticed that I couldn't restart Apache because the new version was built without mod_dav_svn. This is because I originally built subversion with make -DWITH_MOD_DAV_SVN -DWITHOUT_BDB -DWITH_SVNSERVE_WRAPPER install clean and those options are not remembered by portupgrade. A manual build and reinstall solved the problem. Some other ports use options that can be set when building the port for the first time or by running make config. I would like to se this in the subversion port to so that portupgrade knows how to rebuild it properly. You have 2 options: 1. Submit a diff that adds OPTIONS for all of the WITH_/WITHOUT_* variables in the subversion port. 2. use the sysutils/portsconf port, and then add these settings to the PREFIX/etc/ports.conf file. Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: learning about building ports - please help
On 2/9/07, Csaba Molnar [EMAIL PROTECTED] wrote: The CONFIGURE_ENV sets the CPPFLAGS and the LDFLAGS that are passed to the configure script. The variable PTHREAD_LIBS has a value of -pthread, which should solve your problem with libkdefx.la. Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. Thanks, that seems to have solved the issue with libkdefx.la. Now I ran portlint, fixed whitespace issues, but there is one remaining issue: WARN: Makefile: Consider adding support for a WITHOUT_NLS knob to conditionally disable gettext support. Portlint wants you to add the following to the port: .if !defined(WITHOUT_NLS) USE_GETTEXT=yes PLIST_SUB+= NLS= .else CONFIGURE_ARGS+=--disable-nls PLIST_SUB+= NLS=@comment .endif Then modify the pkg-plist: %%NLS%%share/locale/ca_ES/LC_MESSAGES/aquamarine.mo : %%NLS%%share/locale/zh_TW/LC_MESSAGES/aquamarine.mo Also remove all of the @dirrmtry share/locale*, and only add the ones that are missing from /etc/mtree/BSD.local.mk. [EMAIL PROTECTED] share/locale/zh_TW/LC_MESSAGES [EMAIL PROTECTED] share/locale/zh_TW Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: learning about building ports - please help
On 2/9/07, Csaba Molnar [EMAIL PROTECTED] wrote: Now I'm beginning to understand how this works (I read about it in the porter's handbook, but it makes more sense when trying on a real port). Thanks! Also remove all of the @dirrmtry share/locale*, and only add the ones that are missing from /etc/mtree/BSD.local.mk. [EMAIL PROTECTED] share/locale/zh_TW/LC_MESSAGES [EMAIL PROTECTED] share/locale/zh_TW Scot So, can I assume that anything that mtree -f /etc/mtree/BSD.local.dist outputs in /usr/local need not be included in pkg-plist? Yes, as long as it is in BSD.local.dist you don't need to remove the directory on uninstall of the port. Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: unable to fetch mysql-5.0.33.tar.gz
On 2/9/07, Noah [EMAIL PROTECTED] wrote: any clues how I can find the mysql-5.0.33.tar.gz file so I can build the port? === Extracting for mysql-server-5.0.33 = MD5 Checksum mismatch for mysql-5.0.33.tar.gz. = SHA256 Checksum mismatch for mysql-5.0.33.tar.gz. === Refetch for 1 more times files: mysql-5.0.33.tar.gz mysql-5.0.33.tar.gz Remove the mysql-5.0.33.tar.gz file from /usr/ports/distfiles, then try to build the port again. Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Modifying a port and keeping the mods across updates
On 1/20/07, Paul Hoffman [EMAIL PROTECTED] wrote: At 11:37 PM -0600 1/19/07, Scot Hetzel wrote: On 1/19/07, Paul Hoffman [EMAIL PROTECTED] wrote: Greetings again. I have a two-part question that may be a ports FAQ, but I couldn't find such a beast. (1) For a particular port, I need to change the the MAKE_ENV to make it build the way I want. What is the proper way to do this that will live beyond the next time I do a cvsup? That is, editing the Makefile works just fine, but I want something that will live if the Makefile gets reverted. Use the sysutils/portconf port and define the apporiate variable in PREFIX/etc/ports.conf. This isn't working for me. I installed the port and created /usr/local/etc/ports.conf. I added the line: security/nss: NSS_ENABLE_ECC=1 | BUILD_OPT=1 But building security/nss still builds without those in the make environment. If I add NSS_ENABLE_ECC=1 in the Makefile, I can see it reflected in the cc lines during make; if I try to just ue the /usr/local/etc/ports.conf, I don't. Clues? Are you trying to add NSS_ENABLE_ECC to the MAKE_ENV? Normally you would put it in ports.conf as: security/nss: MAKE_ENV+= NSS_ENABLE_ECC=1 But this doesn't work. I tried setting CFLAGS+= NSS_ENABLE_ECC=1, and that removed the default CFLAGS. Instead you need to use: cd /usr/ports echo security/nss: CFLAGS= `make -V CFLAGS` -DNSS_ENABLE_ECC /usr/local/etc/ports.conf Scot ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Modifying a port and keeping the mods across updates
On 1/19/07, Paul Hoffman [EMAIL PROTECTED] wrote: Greetings again. I have a two-part question that may be a ports FAQ, but I couldn't find such a beast. (1) For a particular port, I need to change the the MAKE_ENV to make it build the way I want. What is the proper way to do this that will live beyond the next time I do a cvsup? That is, editing the Makefile works just fine, but I want something that will live if the Makefile gets reverted. Use the sysutils/portconf port and define the apporiate variable in PREFIX/etc/ports.conf. (2) For a particular port, I need to patch a particular source file. This is a patch that will probably be in a future release. Same question as above: what's the proper way to do this that will live beyond the next cvsup? I know how to use 'patch' to apply patches, but not yet to create them. To create a patch you first need to create a backup of the original file, then create the diff. cp file.c file.c-orig make changes to file.c diff -u file.c-orig file.c patch-file.c Then place the patch file into /usr/ports/category/portname/files. Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rcorder doesn't apply to ports startup scripts in 6.0?
On 1/12/07, Jo Rhett [EMAIL PROTECTED] wrote: I'd just like to confirm that rcorder wasn't implemented until 6.1, right? rcorder was implemented for the base system scripts in 5.0-RELEASE, support for the ports rc.d scripts was implemented in 6.0-STABLE (/etc/rc 1.336.2.1 on 2005/12/21 07:11:33) and available in 6.1-RELEASE (/etc/rc 1.336.2.2 on 2006/02/24 21:42:43). So all of the ports which are being updated to use rcorder are now breaking on all of the existing 6.0 systems... It shouldn't break existing systems, as the scripts are still run in alphabetical order on the 6.0 systems before revision 1.336.2.1 of /etc/rc. Which scripts are breaking? Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mysql41-server's rc.d script broken?
On 12/19/06, Frank Steinborn [EMAIL PROTECTED] wrote: If I run mysqld_safe directly mysqld starts as expected. I had a look into the script but could not find the source of the problem. I'm not sure if that's a misconfiguration just on my site - anyone else seeing this? OK - I just edited the script so that it won't send mysqld_safe's output to /dev/null and got the following: Starting mysql. Starting mysqld daemon with databases from /var/db/mysql STOPPING server from pid file /var/db/mysql/shodan.nognu.de.pid 061220 04:05:50 mysqld ended /var/db/mysql/shodan.nognu.de.err says this: 061220 04:04:03 mysqld started 061220 4:04:03 [ERROR] Can't find messagefile '/usr/local/share/mysql/english/errmsg.sys' 061220 4:04:03 [ERROR] Aborting Strange. /usr/local/share/mysql/english/errmsg.sys is there and mysqld just starts fine if I start it manually. Any clues are welcome. When you run the script, mysqld_safe is run as the mysql user. What happens when you run mysqld_safe as the mysql user? Does the mysql user have read access to this file (including sub directories leading to the file)? Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: proftpd syntax error
On 12/14/06, Beech Rintoul [EMAIL PROTECTED] wrote:
I'm in the process of updating this port. I'm getting this on a test build:
support.c: In function `sreplace':
support.c:862: error: syntax error at end of input
gmake[1]: *** [support.o] Error 1
gmake[1]: Leaving directory
`/usr/ports/ftp/proftpd.test/work/proftpd-1.3.1rc1/src'
gmake: *** [src] Error 2
*** Error code 2
And here's the code in question:
const char *pr_strtime(time_t t) {
Doesn't look like there is a problem in the pr_strtime function, but
you do have an error in the sreplace function. The problem most
likely is a missing }, or possibly a missing ;.
Scot
--
DISCLAIMER:
No electrons were mamed while sending this message. Only slightly bruised.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Patch for 'expect'
On 12/14/06, Eric Brunson [EMAIL PROTECTED] wrote: Hi Ports Maintainers, I just spent the last few days sorting out a problem with expect on my 6.1 box. I have a patch to the expect interpreter on this platform that I'd like to offer for your review. There's a problem with the way expect searches for available ptys that makes it only capable of utilizing the first 64 device nodes rather than the full 256 available. I'm brand new to the FreeBSD community coming from years on Solaris and AIX, so I don't know the channels through which to push this. It's a very simple patch, 3 lines of code change, context diff drops right into /usr/ports/lang/expect/files. I also have test cases that show the behavior before and after the patch. To send changes/file a problem report for a port, you can use either send-pr: send-pr -a patch-file or the web send-pr form: http://www.freebsd.org/send-pr.html to submit an update for the port. Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sysutils/xbattbar for !i386
On 12/12/06, Scot Hetzel [EMAIL PROTECTED] wrote:
On 12/12/06, Rong-En Fan [EMAIL PROTECTED] wrote:
Recently, I installed a FreeBSD/amd64 laptop. I found this port
uses apm (i386 only) interface to get battery information. The
patch below changes it to use sysctl(3). Thus, it is usable on
amd64.
http://people.freebsd.org/~rafan/xbattbar.diff
It works on my ThinkPad X60 (-CURRENT). If you are running this
port, please have a test.
Works on my HP dv8135nr (-CURRENT) system.
I have updated the patch so that it can be compiled for systems that
have either an APM or ACPI interface for battery status.
The Makefile has been changed to always use the ACPI interface when
not being built on the i386 arch (i.e. amd64, ...). On the i386 arch
it defaults to ACPI, but can be changed via the options menu to use
APM.
Scot
--
DISCLAIMER:
No electrons were mamed while sending this message. Only slightly bruised.
Index: Makefile
===
RCS file: /home/ncvs/ports/sysutils/xbattbar/Makefile,v
retrieving revision 1.14
diff -u -r1.14 Makefile
--- Makefile 6 Feb 2004 13:12:34 - 1.14
+++ Makefile 12 Dec 2006 08:50:09 -
@@ -7,7 +7,7 @@
PORTNAME= xbattbar
PORTVERSION= 1.4.2
-PORTREVISION= 2
+PORTREVISION= 3
CATEGORIES= sysutils
MASTER_SITES= http://iplab.aist-nara.ac.jp/member/suguru/
DISTNAME= ${PORTNAME}_${PORTVERSION}
@@ -15,12 +15,24 @@
MAINTAINER= [EMAIL PROTECTED]
COMMENT= Simple battery meter
-ONLY_FOR_ARCHS= i386
-
USE_IMAKE= yes
USE_X_PREFIX= yes
WRKSRC= ${WRKDIR}/xbattbar-${PORTVERSION}
MAN1= xbattbar.1
PLIST_FILES= bin/xbattbar
-.include bsd.port.mk
+OPTIONS= APM Use APM Interface for Battery Status OFF \
+ ACPI Use ACPI Interface for Battery Status ON
+
+.include bsd.port.pre.mk
+.if defined(WITHOUT_APM) || ${ARCH} != i386
+CFLAGS+= -DACPI_INTERFACE
+.endif
+
+.if defined(WITH_APM) defined(WITH_ACPI)
+pre-everything::
+ @${ECHO_MSG} WITH_APM and WITH_ACPI both defined, choose one.
+ @${FALSE}
+.endif
+
+.include bsd.port.post.mk
Index: files/patch-ab
===
RCS file: files/patch-ab
diff -N files/patch-ab
--- files/patch-ab 31 Dec 2001 09:47:58 - 1.1
+++ /dev/null 1 Jan 1970 00:00:00 -
@@ -1,13 +0,0 @@
xbattbar.c.old Mon Dec 31 03:32:04 2001
-+++ xbattbar.c Mon Dec 31 03:32:08 2001
-@@ -522,8 +522,8 @@
- int fd, r, p;
- struct apm_info info;
-
-- if ((fd = open(APMDEV21, O_RDWR)) == -1
-- (fd = open(APMDEV22, O_RDWR)) == -1) {
-+ if ((fd = open(APMDEV21, O_RDONLY)) == -1
-+ (fd = open(APMDEV22, O_RDONLY)) == -1) {
- fprintf(stderr, xbattbar: cannot open apm device\n);
- exit(1);
- }
Index: files/patch-xbattbar.c
===
RCS file: files/patch-xbattbar.c
diff -N files/patch-xbattbar.c
--- /dev/null 1 Jan 1970 00:00:00 -
+++ files/patch-xbattbar.c 12 Dec 2006 08:06:50 -
@@ -0,0 +1,66 @@
+--- xbattbar.c.orig Thu Feb 1 23:25:29 2001
xbattbar.c Tue Dec 12 02:05:59 2006
+@@ -501,6 +501,43 @@
+
+ #ifdef __FreeBSD__
+
++#ifdef ACPI_INTERFACE
++
++#include sys/types.h
++#include sys/sysctl.h
++
++int first = 1;
++void battery_check(void)
++{
++ int r, p;
++ size_t r_size, p_size;
++
++ ++elapsed_time;
++
++ /* get current status */
++ r_size = sizeof(r);
++ if (sysctlbyname(hw.acpi.battery.life, r, r_size, NULL, 0) == -1) {
++fprintf(stderr, xbattbar: can not get battery status\n);
++exit(1);
++ }
++
++ /* get AC-line status */
++ p_size = sizeof(p);
++ if (sysctlbyname(hw.acpi.acline, p, p_size, NULL, 0) == -1) {
++fprintf(stderr, xbattbar: can not get AC-line status\n);
++exit(1);
++ }
++
++ if (first || ac_line != p || battery_level != r) {
++first = 0;
++ac_line = p;
++battery_level = r;
++redraw();
++ }
++ signal(SIGALRM, (void *)(battery_check));
++}
++#else /* ACPI_INTERFACE */
++
+ #include machine/apm_bios.h
+
+ #define APMDEV21 /dev/apm0
+@@ -522,8 +559,8 @@
+ int fd, r, p;
+ struct apm_info info;
+
+- if ((fd = open(APMDEV21, O_RDWR)) == -1
+- (fd = open(APMDEV22, O_RDWR)) == -1) {
++ if ((fd = open(APMDEV21, O_RDONLY)) == -1
++ (fd = open(APMDEV22, O_RDONLY)) == -1) {
+ fprintf(stderr, xbattbar: cannot open apm device\n);
+ exit(1);
+ }
+@@ -572,6 +609,8 @@
+ }
+ signal(SIGALRM, (void *)(battery_check));
+ }
++
++#endif /* APM INTERFACE */
+
+ #endif /* __FreeBSD__ */
+
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sysutils/xbattbar for !i386
On 12/12/06, Rong-En Fan [EMAIL PROTECTED] wrote: Recently, I installed a FreeBSD/amd64 laptop. I found this port uses apm (i386 only) interface to get battery information. The patch below changes it to use sysctl(3). Thus, it is usable on amd64. http://people.freebsd.org/~rafan/xbattbar.diff It works on my ThinkPad X60 (-CURRENT). If you are running this port, please have a test. Works on my HP dv8135nr (-CURRENT) system. Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: VMware Workstation does not run on 2.0.x SMP Linux kernels. Please update to a 2.2.x or later SMP Linux kernel
On 11/6/06, Lane [EMAIL PROTECTED] wrote: Hello, I've recently installed emulators/vmware3, purchased a linux license on ebay, and ran into this message: VMware Workstation does not run on 2.0.x SMP Linux kernels. Please update to a 2.2.x or later SMP Linux kernel What is the output of 'sysctl compat.linux.osrelase'? It shoud give you 2.4.2. See the following post from a user who had the same problem: http://lists.freebsd.org/pipermail/freebsd-emulation/2003-July/000103.html Make sure your not setting compat.linux.osrelease in your /etc/sysctl.conf file. Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD Port: WebCalendar-1.0.4
On 11/1/06, Eric [EMAIL PROTECTED] wrote: sounds good. thanks for taking care of that so fast. i think its the ports standard to install to www and not the data directory in order to prevent people from drilling into directories of uninitiated apps and whatnot before the administrator is ready. perhaps someone else knows the exact details? Kris? Thats one of the reasons. I believe another reason is so that the port doesn't overwrite the files in the www/data directory and then causing damage to the website. Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make ports depending on sysutils/cdrtools* USE_GNOME=cdrools
On 10/31/06, Chuck Swiger [EMAIL PROTECTED] wrote:
On Oct 31, 2006, at 8:59 AM, Norikatsu Shigemura wrote:
[ ... ]
Description:
Some ports depending on sysutils/cdrtools and some ports dependeing
on sysutils/cdrtools-cjk are conflicted. So I want to integrate to
USE_GNOME= cdrtools and OPTIONify WITH_CJK.
How-To-Repeat:
cd /usr/ports/sysutils/gnomebaker; make install WITH_CJK
And, after portupgrade GNOME applications.
[ ... ]
Index: sysutils/dvd+rw-tools/Makefile
===
RCS file: /home/ncvs/ports/sysutils/dvd+rw-tools/Makefile,v
retrieving revision 1.22
diff -u -r1.22 Makefile
--- sysutils/dvd+rw-tools/Makefile10 May 2006 19:16:18 - 1.22
+++ sysutils/dvd+rw-tools/Makefile31 Oct 2006 13:34:29 -
@@ -14,7 +14,7 @@
MAINTAINER= [EMAIL PROTECTED]
COMMENT= DVD burning software
-RUN_DEPENDS= ${LOCALBASE}/bin/mkisofs:${PORTSDIR}/sysutils/cdrtools
+USE_GNOME= cdrtools
With respect to this, I don't want dvd+rw-tools to depend on X11 or
GNOME.
Does cdrtools have a dependenacy on GNOME?
If it doesn't then it would be better to add a USE_CDRTOOLS knob to bsd.port.mk
that would allow the selection of either the cdrtools or cdrtools-cjk ports.
.if defined(USE_CDRTOOLS)
.if exists(${DOCSDIR}/cdrtools-cjk/README) || defined(WITH_CJK) ||
${USE_CDRTOOLS} == CJK
WANT_CDRTOOLS_CJK= yes
.endif
.if defined(WANT_CDRTOOLS_CJK)
RUN_DEPENDS+= cdrecord:${PORTSDIR}/sysutils/cdrtools-cjk
.else
RUN_DEPENDS+= cdrecord:${PORTSDIR}/sysutils/cdrtools
.endif
.endif
--
DISCLAIMER:
No electrons were mamed while sending this message. Only slightly bruised.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD Port: libpreludedb-0.9.10
On 10/25/06, Robin Gruyters [EMAIL PROTECTED] wrote:
Quoting David Naylor [EMAIL PROTECTED]:
Hi,
I have recently tried a make index for the ports dir, it failed with a
complaint about libpreludedb, when I tried to make libpreludedb I got the
same error. (My make.conf includes WITH_PYTHON=yes)
From the build command:
make WITH_PYTHON=yes
Makefile, line 43: Could not find /Mk/bsd.python.mk
make: fatal errors encountered -- cannot continue
I have tried make -V PORTSDIR on different ports and the output
is: /usr/ports Which is correct. The problematic line, for interest sake
is:
.include ${PORTSDIR}/Mk/bsd.python.mk
I have have a current copy of ports from cvsup2.za.freebsd.org
Hi David,e
Hmm, that's weird... Looks like you are missing bsd.python.mk.
Can you check if it exists in the /usr/ports/Mk dir?
The problem is that PORTSDIR is not defined before the attempt to
include bsd.python.mk due to make doesn't included bsd.port.mk until
it gets to the end of the Makefile.
Have a look at how the security/ftimes handles the include for
bsd.openssl.mk using bsd.ports.pre.mk and bsd.ports.post.mk.
Scot
--
DISCLAIMER:
No electrons were mamed while sending this message. Only slightly bruised.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pdflib fetch error
On 10/13/06, lveax [EMAIL PROTECTED] wrote: hey all,i can't fetch the distfile when i update pdflib,would anyone fix it? Looks like the file is no longer on the web site. Instead there is a new version: http://www.pdflib.com/binaries/PDFlib/700/PDFlib-Lite-7.0.0p1.tar.gz From the changes.txt = PDFlib 7.0.0p1 (October 11, 2006) = - 2006-10-10 Preparations and minor changes for iSeries builds. - 2006-10-10 (bug #900) Contrary to the documentation, the SearchPath resource category was not implemented with case-insensitive handling of the category name. - 2006-10-09 (bug #899) PDFlib Lite could crash or create invalid PDF output due to a problem in preparing the source code packages. - 2006-10-09 (bug #891) Fixed a problem with varargs handling which showed up in some 64-bit builds. Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: php5-5.1.6 5.1.6_1
On 10/13/06, Bill Blue [EMAIL PROTECTED] wrote: Hi - I'm running 6.2 PRERELEASE #2 with my ports tree current to this morning (around 9am GMT-8). i386 with a Pentium 4 3.2Ghz It took some massaging, but I was finally able to get all the ports re-compiled except one, that in the subject line. php5-5.1.6 refuses to build because of Known Vulnerabilities: php -- _ecalloc integer overflow vulnerability, php5-5.1.6_1 refuses to build also because of Known Vulnerabilities: php -- open_basedir race condition vulnerabilities. Any suggestions? You can install the port by defining DISABLE_VULNERABILITIES when building/installing the port. But you must understand that the installed port will have a security vulnerability. Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: p5-Apache-DBI 'make package' dependency strangeness
I know there's magic that almost gets it right, because it was finding
my apache-2.2.3 dependency before (when I didn't specify APACHE_PORT),
but was trying to add an apache20 or apache13 dependency as well.
Speaking of APACHE_PORT... Is it documented somewhere that that's the
variable needed for this stuff? It's not in the hints in
/usr/ports/Mk/bsd.apache.mk, and what I do see implies that
setting APACHE_VERSION to 22 should DTRT.
The reason why Apache 2.0 port is appearing in your dependancy list is
because of the way the p5-Apache-DBI Makefile is written. If you look
at bsd.apache.mk, and look at this section of code:
.elif ${USE_APACHE:C/\.//:C/\+//:M[12][3210]} !=
AP_PORT_IS_MODULE= YES
for backward compatibility
.elif ${USE_APACHE:L} == yes
. if defined(WITH_APACHE2)
APACHE_PORT?= www/apache20
. else
APACHE_PORT?= www/apache13
. endif
APXS?= ${LOCALBASE}/sbin/apxs
.if !defined(APACHE_COMPAT)
BUILD_DEPENDS+= ${APXS}:${PORTSDIR}/${APACHE_PORT}
RUN_DEPENDS+= ${APXS}:${PORTSDIR}/${APACHE_PORT}
.endif
End of backward compatibility
When WITH_APACHE2 is defined, it sets the dependancy to the
www/apache20 port, because it has defined APACHE_PORT, even though the
APACHE_PORT variable gets overriden latter in bsd.apache.mk by the
check for the currently installed apache port.
To solve the problem in the p5-APACHE-DBI, you need to take a hint
from the mod_perl2 port to define USE_APACHE=2.0+.
If the current code in the p5-Apache-DBI port is changed to:
.if defined(WITH_MODPERL2)
USE_APACHE= 2.0+
RUN_DEPENDS+= ${SITE_PERL}/${PERL_ARCH}/mod_perl2.pm:${PORTSDIR}/www/mod_perl2
.else
USE_APACHE= yes
RUN_DEPENDS+= ${SITE_PERL}/${PERL_ARCH}/mod_perl.pm:${PORTSDIR}/www/mod_perl
.endif
.include bsd.port.pre.mk
Then to build the port for mod_perl2, you just build it as:
make -DWITH_MODPERL2
Also setting APACHE_VERSION=22 does nothing, as it gets overriden in
bsd.apache.mk.
Scot
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
x11/kde3: LANG=C: not found error
When the x11/kde3/scripts/configure.kde script is
run it displays the following error:
LANG=C: not found
Looking for installd modules.LANG=C: not found
This causes the script to display a dialog box with
all options not checked.
The cause of the problem is that the TR variable
is being defined as LANG=C /usr/bin/tr in bsd.port.mk
and then passed to the script in SCRIPTS_ENV. Which
causes this code to fail with the error:
for i in `${ECHO} ${ALL_MODULES} | ${TR} '[:upper:]' '[:lower:]'`
do
eval status_$i=ON
done
NOTE: to see the error you need to add a 'read var'
before the script displays the dialog box.
I checked my system, and have the /usr/share/nls/C
directory, and it contains one file (ee.cat).
I also looked at the /usr/share/locale directory,
and didn't find a C directory in there.
Is there something wrong on my system, or is there
a bug in this configure script.
Scot
PS. There is also another bug in the do-install
target of the port. If you do a make install
without first doing a make build the kde-meta.conf
file is not installed. This is caused by the ports
Makefile looking for Makefile.inc before it is created.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Samba and FAM
On 9/14/06, Peter Jeremy [EMAIL PROTECTED] wrote: On Wed, 2006-Sep-13 11:42:06 -0500, Thomas T. Veldhouse wrote: The catch 22 is that Courier-Imap attempts to use FAM even when it is not configured to do so. So, I have to have FAM installed. I could get it all working by deinstalling and reinstalling in the right order ... until portmanager comes along and upgrades samba sometime in the future. I don't have the samba configure script to hand but if it's a typical GNU configure script, you should be able to specify something like '--without-fam' to stop samba looking for FAM. This would mean tweaking the FreeBSD Makefile but that's a lot easier than remembering to deinstall/reinstall various ports. I had a look at the configure script, and it doesn't have that option to exclude FAM when FAM is installed. Instead it will automatically add FAM support when it finds it. Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Samba and FAM
On 9/13/06, Thomas T. Veldhouse [EMAIL PROTECTED] wrote:
I considered uninstalling FAM and rebuilding Samba, but, as it turns
out, Courier-IMAP requires FAM as a dependency even though it is not a
declared dependency in the Makefile.
Even though FAM was not selected when building Samba, I am getting the
above errors. Is there a way to avoid these filling my log files?
Uninstall Courier-IMAP, and FAM. Then rebuild Samba. Finally
reinstall Courier-IMAP.
The problem is that the net/samba3/Makefile automatically detects
fam/gam on the system, and sets WITH_FAM_SUPPORT, even if FAM_SUPPORT
is off in OPTIONS.
.if exists(${LOCALBASE}/libexec/gam_server)
WANT_FAM_SYSTEM=gamin
WITH_FAM_SUPPORT= on
. undef WITHOUT_FAM_SUPPORT
.elif exists(${LOCALBASE}/bin/fam)
WANT_FAM_SYSTEM=fam
WITH_FAM_SUPPORT= on
. undef WITHOUT_FAM_SUPPORT
.endif
.if defined(WITH_FAM_SUPPORT) || defined(WANT_FAM_SYSTEM)
USE_FAM=yes
.endif
It should only detect which FAM_SYSTEM is installed, and should only
test if WITH_FAM_SUPPORT is set.
Also, if the samba configure script has an option to disable fam
support, it should be added as:
.if defined(WITH_FAM_SUPPORT)
USE_FAM= yes
.else
CONFIGURE_ARGS+= --disable-fam
.endif
This would then prevent the configure script from detecting and using
fam/gam on a system that has it installed.
NOTE: The detection of the FAM_SYSTEM, may not be needed.
Scot
--
DISCLAIMER:
No electrons were mamed while sending this message. Only slightly bruised.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Samba and FAM
On 9/13/06, Scot Hetzel [EMAIL PROTECTED] wrote:
The problem is that the net/samba3/Makefile automatically detects
fam/gam on the system, and sets WITH_FAM_SUPPORT, even if FAM_SUPPORT
is off in OPTIONS.
:
Also, if the samba configure script has an option to disable fam
support, it should be added as:
.if defined(WITH_FAM_SUPPORT)
USE_FAM= yes
.else
CONFIGURE_ARGS+= --disable-fam
.endif
This would then prevent the configure script from detecting and using
fam/gam on a system that has it installed.
Had a look at the samba configure script, and it doesn't have an
option to disable fam/gamin support.
So your only option is to uninstall all ports that require fam/gamin.
Install samba w/FAM_SUPPORT off, then reinstall the ports that were
removed.
OPTIONS=LDAPWith LDAP support on \
:
AIO_SUPPORT With experimental AIO support off
.if exists(${LOCALBASE}/libexec/gam_server) || exists(${LOCALBASE}/bin/fam)
OPTIONS+= FAM_SUPPORT With File Alteration Monitor off
.else
FORCE_FAM_SUPPORT= yes
.endif
OPTIONS+= SYSLOG With Syslog support off \
QUOTAS With Disk quota support off \
:
POPTWith system-wide POPT library on
Then in pre-everything, a test for FORCE_FAM_SUPPORT:
.if defined(FORCE_FAM_SUPPORT)
pre-everything::
@${ECHO} Samba will be compiled with File Monitor Support
(${WANT_FAM_SYSTEM})
@${ECHO}
@${ECHO} If this is not what you want, then you need to
uninstall all ports depending on ${WANT_FAM_SYSTEM}. Install Samba,
and then reinstall all the ${WANT_FAM_SYSTEM} depending ports.
.endif
Scot
--
DISCLAIMER:
No electrons were mamed while sending this message. Only slightly bruised.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Samba and FAM
On 9/13/06, Timur I. Bakeyev [EMAIL PROTECTED] wrote: Hi guys! Can you please explain me, what is all that fight about? No fight, just trying to help Thomas out by finding a way to disable fam support. On 9/13/06, Timur I. Bakeyev [EMAIL PROTECTED] wrote: Hi Tom! On Wed, Sep 13, 2006 at 11:42:06AM -0500, Thomas T. Veldhouse wrote: Scot Hetzel wrote: Had a look at the samba configure script, and it doesn't have an option to disable fam/gamin support. So your only option is to uninstall all ports that require fam/gamin. Install samba w/FAM_SUPPORT off, then reinstall the ports that were removed. The catch 22 is that Courier-Imap attempts to use FAM even when it is not configured to do so. So, I have to have FAM installed. I could get it all working by deinstalling and reinstalling in the right order ... until portmanager comes along and upgrades samba sometime in the future. I don't see what portmanager have to do here. Also I don't see how Samba port could be upgraded regarding this problem. The only solution I see is to alter Samba configure script so it'll be possible to disable linkage against FAM library. The problem is that if you install samba x.y.z without fam support, then use portmanager to upgrade to samba x.y.z+1, the port built by portmanager would have fam support built in. The only way around it would be to uninstall all FAM dependant ports, before upgrading samba. Don't dwell on this problem too much, a note to indicate that fam support had been forced is enough. Re-write the warning as you see fit, or you could use: FAM_SUPPORT forced due to braindead linux configure script :) Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: no /usr/ports
On 9/6/06, KAYVEN RIESE [EMAIL PROTECTED] wrote: my ports directory is gone. how'd that happen? What were you doing before it disapeared? There are several ways to make /usr/ports disapear: 1. rm -rf /usr/ports/* 2. cvs update -R RELENG_6 3. cvsup with an branch tag in the supfile for ports. Problem 2 3 are similar, as the ports tree is not branched. This causes cvs or cvsup to delete the ports since there is no branch with that tag (i.e. RELENG_6). Instead you need to specify a release tag (i.e. RELEASE_6_1_0) or no tag (gets you the latest ports changes). If your using cvsup, post your supfile and someone will help you fix it. Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /usr/ports/databases/clip - error after instalation
On 8/29/06, Dario Cardoso [EMAIL PROTECTED] wrote:
I use FreeBSD and i install clip
When i try running the little example i receive this message
blackthorne# pwd
/usr/local/clip/doc/example
blackthorne# ./mouse
/libexec/ld-elf.so.1: Shared object libclip.so not found, required by
mouse
blackthorne# ./tcpserv
/libexec/ld-elf.so.1: Shared object libclip.so not found, required by
tcpserv
blackthorne#
How i resolv this?
Does ldconfig -r | grep clip find the libclip.so file?
It should find the file in ${PREFIX}/clip/lib/libclip.so. If it
doesn't, then you need to add ${PREFIX}/clip/lib to the library path.
ldconfig -n ${PREFIX}/clip/lib
Scot
--
DISCLAIMER:
No electrons were mamed while sending this message. Only slightly bruised.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: port tk84 won't upgrade properly on AMD64 system
On 8/26/06, Dino Vliet [EMAIL PROTECTED] wrote: Hi all, I'm having problems upgrading my port tk84 on a amd64 machine. I'm using cvsup and portupgrade to accomplish that and it fails with: Stop in /usr/ports/x11-toolkits/tk84/work/tk8.4.13/unix. *** Error code 1 Stop in /usr/ports/x11-toolkits/tk84. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade4543.1 env PORT_UPGRADE=yes make ** Fix the problem and try again. --- Skipping 'math/R' (R-2.2.1_1) because a requisite package 'tk-8.4.11,2' (x11-toolkits/tk84) failed (specify -k to force) ** Listing the failed packages (*:skipped / !:failed) ! x11-toolkits/tk84 (tk-8.4.11,2) (linker error) * math/R (R-2.2.1_1) --- Packages processed: 0 done, 16 ignored, 1 skipped and 1 failed What can I do to solve this? cd /usr/ports/x11-toolkits/tk84/ make clean make build Then report the error your getting with the build, as we can't tell what is failing from the above information. Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: the best port update tool
On 8/23/06, Helge Oldach [EMAIL PROTECTED] wrote:
Scot Hetzel:
While the portmanager, portupgrade, and portmaster tools allow you to
keep your specific port options in a file, they are incompatible with
each other and when building directly from /usr/ports, as the port
options in these seperate files are not available to the other tools
or to /usr/ports. This deficiency has been fixed with the
sysutils/portconf port, where you can specify your port options in
PREFIX/etc/ports.conf file, and these tools and direct building from
/usr/ports will use these port options.
Hmm... What is wrong with directly amending /etc/make.conf with, for
example:
Nothing wrong with doing it this way, just that a newbie has to find
this syntax, and edit their make.conf accordingly. Where with a
newbie using the ports.conf file, they just add each option on one
line, and let the magic added by the sysutils/portconf to
/etc/make.conf do all the work for them.
An additional benifit is that you don't clutter your make.conf file
with all of these .if ... .endif statements when you have more than 10
ports that you set with custom options.
-
WRKDIRPREFIX=/usr/obj
.if ${.CURDIR:M*/devel/gmake}
WITHOUT_NLS=yes
.endif
.if ${.CURDIR:M*/mail/fetchmail}
.MAKEFLAGS: -DWITH_NTLM
.endif
:
Note specifically the .MAKEFLAGS trick above that IMHO won't easily
work with portconf.
That will work with portconf, without using .MAKEFLAGS:
devel/gmake: WITHOUT_NLS
mail/fetchmail: WITH_NTLM
You could have also used WITH_NTLM=YES instead of .MAKEFLAGS in your
make.conf and the fetchmail port would be built with NTLM support.
.if ${.CURDIR:M*/sysutils/uptimed}
post-install-script:
-${RM} ${PREFIX}/www/cgi-bin/uprecords.conf
-${RM} ${PREFIX}/www/cgi-bin/uprecords.cgi
-${RM} ${PREFIX}/www/cgi-bin/uprecords.header
-${RM} ${PREFIX}/www/cgi-bin/uprecords.footer
-${RMDIR} ${PREFIX}/www/cgi-bin
-${RMDIR} ${PREFIX}/www
.endif
-
This portconf can't do.
Scot
--
DISCLAIMER:
No electrons were mamed while sending this message. Only slightly bruised.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD Port: virtualmin-2.611
On 8/22/06, Ruud Boon [EMAIL PROTECTED] wrote: Hi There, On the website of webmin/virtualmin they reported that the current version is 3.201. Do you know when the new release will be available trough the ports? Since the port is unmaintained ([EMAIL PROTECTED]), your could try updating the port, and submitting the changes using send-pr. See the Porters Handbook for further details: http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/index.html and more specifically: http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/port-upgrading.html Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading to tcl-8.4.13_1,1 fails
I ran into the same problem where the tests were failing. I didn't
wait for the tests to complete, instead I just killed tcltest and the
port finished installing.
This was on FreeBSD/amd64 6.1-STABLE.
You could also try removing the test target from the ALL_TARGET
variable in the ports Makefile. If your in a hurry to get the port
installed.
Scot
On 8/12/06, Janos Dohanics [EMAIL PROTECTED] wrote:
I'm trying to portupgrade tcl on a FreeBSD 5.5-STABLE system but the
build fails. During the build a bunch of tests fail, finally the build
hangs altogether.
These are the tests which failed:
http-3.3 http::geturl FAILED
http-3.3 FAILED
http-3.4 http::geturl FAILED
http-3.4 FAILED
http-3.5 http::geturl FAILED
http-3.5 FAILED
http-3.6 http::geturl FAILED
http-3.6 FAILED
http-3.7 http::geturl FAILED
http-3.7 FAILED
http-3.8 http::geturl FAILED
http-3.8 FAILED
http-3.9 http::geturl FAILED
http-3.9 FAILED
http-3.10 http::geturl queryprogress FAILED
http-3.10 FAILED
http-3.11 http::geturl querychannel with -command FAILED
http-3.11 FAILED
http-3.14 http::geturl
http://user:[EMAIL PROTECTED]:60980/a/b/c FAILED
http-3.14 FAILED http-4.1 http::Event FAILED
http-4.1 FAILED
http-4.2 http::Event FAILED
http-4.2 FAILED
http-4.3 http::Event FAILED
http-4.3 FAILED
http-4.4 http::Event FAILED
http-4.4 FAILED
http-4.5 http::Event FAILED
http-4.5 FAILED
http-4.6 http::Event FAILED
http-4.6 FAILED
http-4.7 http::Event FAILED
http-4.7 FAILED
http-4.8 http::Event FAILED
http-4.8 FAILED
http-4.9 http::Event FAILED
http-4.9 FAILED
http-4.10 http::Event FAILED
http-4.10 FAILED
http-4.11 http::Event FAILED
http-4.11 FAILED
http-4.12 http::Event FAILED
http-4.12 FAILED
http-4.13 http::Event FAILED
http-4.13 FAILED
http-6.1 http::ProxyRequired FAILED
http-6.1 FAILED
httpold-3.3 http_get FAILED
httpold-3.3 FAILED
httpold-3.4 http_get FAILED
httpold-3.4 FAILED
httpold-3.5 http_get FAILED
httpold-3.5 FAILED
httpold-3.6 http_get FAILED
httpold-3.6 FAILED
httpold-3.7 http_get FAILED
httpold-3.7 FAILED
httpold-3.8 http_get FAILED
httpold-3.8 FAILED
httpold-3.9 http_get FAILED
httpold-3.9 FAILED
httpold-4.1 httpEvent FAILED
httpold-4.1 FAILED
httpold-4.2 httpEvent FAILED
httpold-4.2 FAILED
httpold-4.3 httpEvent FAILED
httpold-4.3 FAILED
httpold-4.4 httpEvent FAILED
httpold-4.4 FAILED
httpold-4.5 httpEvent FAILED
httpold-4.5 FAILED
httpold-4.6 httpEvent FAILED
httpold-4.6 FAILED
httpold-4.7 httpEvent FAILED
httpold-4.7 FAILED
httpold-4.8 httpEvent FAILED
httpold-4.8 FAILED
httpold-4.9 httpEvent FAILED
httpold-4.9 FAILED
httpold-4.10 httpEvent FAILED
httpold-4.10 FAILED
httpold-4.11 httpEvent FAILED
httpold-4.11 FAILED
httpold-4.12 httpEvent FAILED
httpold-4.12 FAILED
httpold-6.1 httpProxyRequired FAILED
httpold-6.1 FAILED
io-29.34 Tcl_Close, async flush on close, using sockets FAILED
io-29.34 FAILED
io-29.35 Tcl_Close vs fileevent vs multiple interpreters FAILED
io-29.35 FAILED
io-51.1 Test old socket deletion on Macintosh FAILED
io-51.1 FAILED
io-54.1 Recursive channel events FAILED
io-54.1 FAILED
socket-2.10 close on accept, accepted socket lives FAILED
socket-2.10 FAILED
socket-7.4 testing socket specific options FAILED
socket-7.4 FAILED
The last test, where the build hangs is this:
Contents of test case:
set s [socket -server accept 0]
proc accept {s a p} {
global x
set x [fconfigure $s -sockname]
close $s
}
set listen [lindex [fconfigure $s -sockname] 2]
set s1 [socket [info hostname] $listen]
set timer [after 1 set x timed_out]
vwait x
after cancel $timer
close $s
close $s1
set l
lappend l [expr {[lindex $x 2] == $listen}] [llength $x]
Test generated error; Return code was: 1
Return code should have been one of: 0 2
errorInfo: couldn't open socket: connection refused
while executing
socket [info hostname] $listen
invoked from within
set s1 [socket [info hostname] $listen]
(uplevel body line 9)
invoked from within
uplevel 1 $script
errorCode: POSIX ECONNREFUSED {connection refused}
socket-7.4 FAILED
I'd appreciate your suggestions...
--
Janos Dohanics
3D RESEARCH
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
--
DISCLAIMER:
No electrons were mamed while sending this message. Only slightly bruised.
___
Re: ports without configure do not receive CC
On 8/10/06, Scot Hetzel [EMAIL PROTECTED] wrote: Or use the sysutils/portconf port, and then place your port specific variables in the /usr/local/etc/port.conf file, no need to clutter /etc/make.conf. CATEGORY/PORTNAME*: CC=XXX editors/openoffice*: WITH_TTF_BYTECODE_ENABLED Forgot to mention you can also have global variables defined in port.conf */*: WRKDIRPREFIX=/usr/obj Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Makefile problem
On 8/3/06, Beech Rintoul [EMAIL PROTECTED] wrote:
I have an ongoing problem with the makefile for ftp/proftpd. This problem
existed when I took over maintainership of the port and I'd like to fix it if
possible before the next update.
When I run portlint, I get the following:
FATAL: Makefile: [131]: USE_OPENSSL is set after including bsd.port.pre.mk.
I can cheat by adding a space instead of a tab after the line and turn it into
a warning, but I'd really like to fix this properly. I've tried moving
bsd.port.pre.mk to various places, but all I accomplish is changing the
error.
Can someone take a look at this and maybe give me a suggestion?
Since you include bsd.openssl.mk in the ports Makefile after the
include for bsd.port.pre.mk, you don't need to set the USE_OPENSSL
variable.
.include ${PORTSDIR}/Mk/bsd.port.pre.mk
:
.if defined(WITH_OPENSSL)
CFLAGS+=-DHAVE_OPENSSL
-USE_OPENSSL= YES
.include ${PORTSDIR}/Mk/bsd.openssl.mk
PROFTPD_LIBS+= -lssl -lcrypto -L${LOCALBASE}/lib
MODULES:=${MODULES}:mod_tls
.if defined(WITH_LDAP_TLS)
EXTRA_PATCHES+= ${FILESDIR}/extra_patch-ldap-tls-mod_ldap.c
.endif
.endif
The same thing can be done to the ftp/curl port:
1. Get rid of USE_OPENSSL before bsd.port.pre.mk
-.if defined(WITHOUT_SSL)
-USE_OPENSSL= YES
-.endif
.include bsd.port.pre.mk
2. add a new option for OpenSSL that defaults to on
OPTIONS=CARES Asynchronous DNS resolution via c-ares off \
CURL_DEBUG Enable curl diagnostic output off \
+ SSL OpenSSL Support on \
+ GNUTLS Use GNU TLS if OpenSSL is OFF off \
- GNUTLS Use GNU TLS if WITHOUT_SSL is specified off \
IPV6 IPv6 support on \
KERBEROS4 Kerberos 4 authentication off \
LIBIDN Internationalized Domain Names via libidn off \
NTLM NTLM authentication off
3. Change:
.if !defined(WITHOUT_SSL)
CONFIGURE_ARGS+=--with-ssl=${OPENSSLBASE}
.else
CONFIGURE_ARGS+=--without-ssl
.endif
to
.if !defined(WITHOUT_SSL)
.include ${PORTSDIR}/Mk/bsd.openssl.mk
.include bsd.openssl.mk
CONFIGURE_ARGS+=--with-ssl=${OPENSSLBASE}
.else
CONFIGURE_ARGS+=--without-ssl
.endif
Do we need to specify the full patch to bsd.openssl.mk, or can we
getaway with just:
.include bsd.openssl.mk
in the ports Makefile.
This should fix the ports that have an optional dependancy on OpenSSL.
Scot
--
DISCLAIMER:
No electrons were mamed while sending this message. Only slightly bruised.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: some ports are not been started
On 8/3/06, Rodrigo Graeff [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Since a few days ago I have noted that for some strange reason some ports are not been initialized at the boot, for example: mysql-server I have at my rc.conf the line mysql_enable=YES and I also have /usr/local/etc/rc.d/mysql-server.sh without any touch of mine, is not permission and this file has not .sample at the end, during the boot process to start the services, mysql doesn't start but If I login and execute: sh /usr/local/etc/rc.d/mysql-server.sh start it works. : Any clues ? What version of FreeBSD are you running? If you recently upgraded to FreeBSD 6.1, did you run mergemaster to update your /etc/rc.d/ directory, as there was a change in rc scripts procesing to allow the /usr/local/etc/rc.d scripts t be ordered with the less critical startup scripts in /etc/rc.d. Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portmaster, bison, java/jdk15
On 8/1/06, Jiawei Ye [EMAIL PROTECTED] wrote: 2. I just made a java/jdk15 yesterday, and the port gets updated today, resulting in portmaster wanting to upgrade the port, but portmaster will also try to install linux-sun-jdk15 as a dependancy on JDK15. The normal situation is that when there is a native JDK/Diablo present in the system, JDK15 port shouldn't depend on linux-sun-jdk for bootstrapping. I am not sure if this is a problem with the jdk15 port itself or not. doing make clean in java/jdk15 does list linux-sun-jdk as a dependancy, but simple 'make install' will not pull it in, is this contradictory? No it's not contradictory, linux-sun-jdk is a build time dependance and is only needed to build java/jdk15. It is not need for JDK15 to run, this is why it is not listed as a dependancy during a 'make install'. Scot Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: conflicting dependency
On 7/19/06, John E Hein [EMAIL PROTECTED] wrote:
Let's say there are two ports A B.
They both provide libfoo.so.1 (and so register CONFLICTS with each other).
Now port C wants to use libfoo (and doesn't care if it gets it
from A or B).
What does port C list in it's LIB_DEPENDS?
What if it lists A and someone installs B... does A get registered as
the dependency when C is installed even though A is not installed?
In the port Cs Makefile, you add:
.if exists(${PREFIX}/bin/file found only in Port B)
PORTA_STAT= OFF
PORTB_STAT= ON
.else
PORTA_STAT= ON
PORTB_STAT= OFF
.endif
OPTIONS = PORTA Depends on libfoo from port A ${PORTA_STAT} \
PORTB Depends on libfoo from port B ${PORTB_STAT}
.if defined(WITH_PORTA) || !defined(WITHOUT_PORTA)
LIB_DEPENDS+= foo.1:${PORTSDIR}/dependancy on Port A
.elif defined(WITH_PORTB)
LIB_DEPENDS+= foo.1:${PORTSDIR}/dependancy on Port B
.else
IGNORE= Must choose either port A or B
.endif
This allows the admin to install either port A or B, and port C will
automatically detect which port is installed, as well as allowing the
admin to choose which to install.
Scot
--
DISCLAIMER:
No electrons were mamed while sending this message. Only slightly bruised.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
