Hi,
I got this error trying to install fvwm-themes
checking for fvwm-config... /usr/local/bin/fvwm-config
checking for FvwmM4... /usr/local/libexec/fvwm/2.4.20/FvwmM4
configure: error:
You have fvwm-2.4.20, which is not up to
in message [EMAIL PROTECTED],
wrote Siju George thusly...
I got this error trying to install fvwm-themes
checking for fvwm-config... /usr/local/bin/fvwm-config
checking for FvwmM4... /usr/local/libexec/fvwm/2.4.20/FvwmM4
Hi,
according to the ports tree you need to install fvwm2-devel, which is
currently at 2.5.24_1
HTH
Christian
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL
Garrett Cooper wrote:
We're rehashing the discussion made last year around June - July.
Indeed.
We came to the conclusion that BDB should be used, as no other DB
backend / API exists in the base system (currently), and porting
SQLLite (while nice) appeared to be non-trivial to port
Doug Barton [EMAIL PROTECTED] 2008-03-26:
Willy Picard wrote:
portupgrade simply ignores BROKEN ports during a portupgrade -a. I
am not even asking about a similar behaviour for portmaster. I wanted
just to ask if an option allows to do the same. If no such an option
exists, I think that its
Referencing old entries in ports/UPDATING that contain the commands,
options, etc. isn't completely safe because those options may change.
In the case of portupgrade(1), at the following options changed between
pkgtools-2.0.1 and pkgtools-2.4.3:
2.0.1:
-c
--clean Do ``make
:-) I love FreeBSD and its community!!!
Thank you for being so responsive!
Paul Pathiakis
From: Koopmann, Jan-Peter [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 27, 2008 10:14 AM
To: Paul Pathiakis
Cc: [EMAIL PROTECTED]
Subject: RE: FreeBSD
New version was committed today. Update your port tree please.
Mit freundlichen Grüßen
Jan-Peter Koopmann
Dipl.-Wirtschaftsinformatiker
Geschäftsführer
From: Paul Pathiakis [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 27, 2008 2:44 PM
To: Koopmann, Jan-Peter
Cc: [EMAIL
Daniel Roethlisberger wrote:
Of course the user wants to be notified of all ports which cannot be
upgraded for some reason (broken, marked BROKEN, removed/missing origin,
etc.), but forcing the upgrade to abort because of a problem with a
single port does not make sense.
It may not make
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm using pkgdb because I wanted to try portupgrade, and it required it. My
problem is that it's doing procedures, asking for a decision on my part, but I
can't make any guess how to answer it, because the prompt is fairly meaningless
to me. Here
Portupgrade -a -r -p took care of everything after my cvsup.
Ports were about 3-4 months out of date. Once updated and restarted,
everything worked fine. (portupgrade loaded or upgraded all the
requirements you mention below.)
How can people not love this OS?
I can't wait to migrate some of
Dear Puchar!
Here is what you should did before:
a) if you 're installing from ports:
http://www.cupovoip.com/docs/asterisk-installation-freebsd-english.html
b) from source
http://wiki.sangoma.com/wanpipe-linux-asterisk-install
cheers!!
Tracy
Wojciech Puchar [EMAIL PROTECTED] a écrit
On Wed, Mar 26, 2008 at 03:22:52PM +0100, Pav Lucistnik wrote:
Wesley Shields p??e v st 26. 03. 2008 v 10:18 -0400:
Sounds to me like you are thinking of including the description in the
dialog. This sounds like a good idea to me and is something I can look
into doing instead of my
Hi,
The dbmail port has not been updated in a while. There are now two
stable version after the one in the port - 2.2.9 and 2.2.10, which fix
important bugs.
I'm sending you attache modified Makefile and distinfo files if you'll
be kind enough to upgrade that port.
Thanks very much in
Sorry for the late reply, catching up on emails ...
On Thu, 20.03.2008 at 23:32:49 +0100, Pav Lucistnik wrote:
Doug Barton píše v čt 20. 03. 2008 v 13:12 -0700:
Pav Lucistnik wrote:
Doug Barton píše v c(t 20. 03. 2008 v 01:05 -0700:
On Thu, 20 Mar 2008, Michel Talon wrote:
i would
Synopsis: security/fwtk fails to build with X11=off option setting
Responsible-Changed-From-To: pirzyk-freebsd-ports
Responsible-Changed-By: pirzyk
Responsible-Changed-When: Thu Mar 27 22:13:47 UTC 2008
Responsible-Changed-Why:
Patch looks good to me, please commit at your convience. Thanks.
Hi Frank,
On Wed, Mar 26, 2008 at 06:17:58AM -0700, Frank Mayhar wrote:
pthread functions. I fixed it by putting LIBS=-lpthread in my
environment before rebuilding the port. This is a kludge, though; the
port maintainer needs to fix this.
Worked well here, thanks!
Regards
Raphael Becker
Wesley Shields píše v čt 27. 03. 2008 v 15:58 -0400:
I can see it already! :) Can you code it?
As a first pass I've got an almost working skeleton which uses --hfile
and pulls the descriptions from OPTIONS variable (using a 4th field).
It also adds --hline Please use ? for a detailed
Roman Divacky wrote:
On Wed, Mar 26, 2008 at 05:18:29PM +0100, Pav Lucistnik wrote:
You might have noticed a thread on the mailing list called ports system
woes. The submitter pointed out an inefficiency in pkg_delete routine,
that parses the whole /var/db/pkg over and over again for every
Abstract:
Ports 2.0 is designed to be a drop in replacement for the FreeBSD
ports system that incorporates the lesson learned from Peter Miller's
Recursive Make Considered Harmful,
http://aegis.sourceforge.net/auug97.pdf. The SoC portion of the
project will be to create the engine and
20 matches
Mail list logo
