Synopsis: new port: net/libunp
Responsible-Changed-From-To: freebsd-ports-freebsd-doc
Responsible-Changed-By: remko
Responsible-Changed-When: Wed Nov 11 08:44:10 UTC 2009
Responsible-Changed-Why:
Over to maintainer.
http://www.freebsd.org/cgi/query-pr.cgi?pr=14057
Synopsis: new port: net/libunpipc
Responsible-Changed-From-To: freebsd-ports-freebsd-doc
Responsible-Changed-By: remko
Responsible-Changed-When: Wed Nov 11 08:44:15 UTC 2009
Responsible-Changed-Why:
Over to maintainer.
http://www.freebsd.org/cgi/query-pr.cgi?pr=14058
Synopsis: New port: roottail-0.0.4B
Responsible-Changed-From-To: freebsd-ports-freebsd-doc
Responsible-Changed-By: remko
Responsible-Changed-When: Wed Nov 11 08:44:21 UTC 2009
Responsible-Changed-Why:
Over to maintainer.
http://www.freebsd.org/cgi/query-pr.cgi?pr=14059
Synopsis: new port: net/libunp
Responsible-Changed-From-To: freebsd-doc-freebsd-ports
Responsible-Changed-By: remko
Responsible-Changed-When: Wed Nov 11 08:45:03 UTC 2009
Responsible-Changed-Why:
Reassign to ports.
http://www.freebsd.org/cgi/query-pr.cgi?pr=14057
Synopsis: new port: net/libunpipc
Responsible-Changed-From-To: freebsd-doc-freebsd-ports
Responsible-Changed-By: remko
Responsible-Changed-When: Wed Nov 11 08:45:31 UTC 2009
Responsible-Changed-Why:
Reassign to ports, typo.
http://www.freebsd.org/cgi/query-pr.cgi?pr=14058
Synopsis: New port: roottail-0.0.4B
Responsible-Changed-From-To: freebsd-doc-freebsd-ports
Responsible-Changed-By: remko
Responsible-Changed-When: Wed Nov 11 08:45:46 UTC 2009
Responsible-Changed-Why:
Reassign to ports, typo
http://www.freebsd.org/cgi/query-pr.cgi?pr=14059
INDEX build failed with errors:
Generating INDEX-6 - please wait..pkg_info: not found
pkg_info: not found
Done.
make_index: p5-Net-EPP-Proxy-0.03: no entry for /usr/ports/net/p5-Net-EPP-Client
make_index: p5-Net-EPP-Proxy-0.03: no entry for /usr/ports/net/p5-Net-EPP-Frame
make_index:
The Restless Daemon identified a depend_object error while trying to build:
p5-Net-EPP-Proxy-0.03 maintained by po...@freebsd.org
Makefile ident: $FreeBSD: ports/net/p5-Net-EPP-Proxy/Makefile,v 1.7 2009/11/11
10:10:15 wen Exp $
Excerpt from
The Restless Daemon identified a depend_object error while trying to build:
p5-Net-EPP-Proxy-0.03 maintained by po...@freebsd.org
Makefile ident: $FreeBSD: ports/net/p5-Net-EPP-Proxy/Makefile,v 1.7 2009/11/11
10:10:15 wen Exp $
Excerpt from
Hi,
When trying to install or upgrade ports using current
portupgrade-devel, I get this:
$ sudo portinstall cowsay
[Gathering depends for games/cowsay
./usr/local/sbin/portinstall:878:in `get_all_depends': private method
`scan' called for #Set: {} (NoMethodError)
from
Jakob Breivik Grimstveit writes:
When trying to install or upgrade ports using current
portupgrade-devel, I get this:
I have seen something which I believe is the same. I sent mail
to the portupgrade maintainer - ruby@ - a couple of days ago but
have had no reply.
___
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
Thanks for your help Miroslav,
In fact a portupgrade did this to me. I'll try rebuilding the extensions. The last time I tried to re-build the extensions was after the upgrade which was the cause of the broken pear module in the first place.
ok new updated ports tree (just this morning)
On Tue, Nov 10, 2009 at 11:46:17PM +0100, Dominic Fandrey wrote:
If you want to work without a ports tree use pkg_upgrade
(sysutils/bsdadminscripts), it only requires an INDEX file.
The next version will also require the MOVED file (as is now
provided by Pointyhead).
Very nice, your program
On Tue, Nov 10, 2009 at 01:06:26PM -0500, Sean McAfee wrote:
What's the ports@ policy for things like this? I know I'm pretty peeved
that openntpd was pushed to 4.x, which requires 7.
In a perfect world, I'd prefer for someone to fix the newer port on 6.
However, it's fair to note that 6 is
On 2009-11-08 00:06:16, Daniel Eischen wrote:
Patches for amd64 support are also welcome. I thought you were
going to do a port for GNAT-gpl amd64?
'Lo.
I just tried to compile the vanilla GNAT-GPL 2009 sources today and
came across the following error:
Stefan Bethke wrote:
Am 28.07.2009 um 08:44:
[...]
Sorry for the noise, nagios-devel is release 3.1.2. I had falsely
assumed it would build a CVS snapshot.
Stefan
Hi Portslist, dear Nagios-port Maintainer
How about cleaning the Nagios Core Ports a bit?
1) The actual stable Nagios
Wed, Nov 11, 2009 at 07:55:09PM +0100, Achim Hut wrote:
Hi Portslist, dear Nagios-port Maintainer
How about cleaning the Nagios Core Ports a bit?
1) The actual stable Nagios Realease is 3.2.0 dated 2009/08/12
What do we have in ports:
a) nagios-2.12_5
b) nagios-3.0.6_3
c)
Category: ports
Responsible:freebsd-ports-bugs
Synopsis: New port: Python language bindings for Cloud Files API -
Rackspace
Arrival-Date: Sat Oct 24 20:50:01 UTC 2009
___
freebsd-ports@freebsd.org mailing list
On Wed, 11 Nov 2009, freebsd-po...@coreland.ath.cx wrote:
On 2009-11-08 00:06:16, Daniel Eischen wrote:
Patches for amd64 support are also welcome. I thought you were
going to do a port for GNAT-gpl amd64?
'Lo.
I just tried to compile the vanilla GNAT-GPL 2009 sources today and
came
On 2009-11-11 14:48:35, Daniel Eischen wrote:
/gnat/gpl-2009/src/GNAT/obj/./gcc/xgcc -B/gnat/gpl-2009/src/GNAT/obj/./gcc/
-B/usr/local/x86_64-unknown-freebsd7.2/bin/
-B/usr/local/x86_64-unknown-freebsd7.2/lib/ -isystem
/usr/local/x86_64-unknown-freebsd7.2/include -isystem
Folks,
It seems that I have found a workaround. It is to store the address of
the variable in a register and then issue the CAS instruction, which
only accepts register for an address. I am currently testing it.
Alexander Churanov
___
On Wed, 11 Nov 2009, freebsd-po...@coreland.ath.cx wrote:
On 2009-11-11 14:48:35, Daniel Eischen wrote:
/gnat/gpl-2009/src/GNAT/obj/./gcc/xgcc -B/gnat/gpl-2009/src/GNAT/obj/./gcc/
-B/usr/local/x86_64-unknown-freebsd7.2/bin/
-B/usr/local/x86_64-unknown-freebsd7.2/lib/ -isystem
On 2009-11-11 15:07:36, Daniel Eischen wrote:
Oh, I see. Did you configure it with host=i386-unknown-freebsd
and target=amd64-unknown-freebsd (or is it x86_64?)?
It looks like libgcc might not have support for x86_64
FreeBSD??
Full configure line was:
../src/configure \
On Wed, 11 Nov 2009, freebsd-po...@coreland.ath.cx wrote:
On 2009-11-11 15:07:36, Daniel Eischen wrote:
Oh, I see. Did you configure it with host=i386-unknown-freebsd
and target=amd64-unknown-freebsd (or is it x86_64?)?
It looks like libgcc might not have support for x86_64
FreeBSD??
Full
25 matches
Mail list logo
