pdnsd leaking udp sockets

[Marius Nünnerich]

Hi Ashish, all,

I'm currently using pdnsd as a local dns cache. It seems to leak udp
sockets. After an uptime of about 7 days it looks like this:

% sockstat -46 | grep pdnsd
nobody   pdnsd  19655 3  tcp4   127.0.0.1:53  *:*
nobody   pdnsd  19655 4  udp4   127.0.0.1:53  *:*
nobody   pdnsd  19655 6  udp4   *:*   *:*
nobody   pdnsd  19655 7  udp4   *:*   *:*
[...]
nobody   pdnsd  19655 140 udp4  *:*   *:*
nobody   pdnsd  19655 141 udp4  *:*   *:*
nobody   pdnsd  19655 142 udp4  *:*   *:*
%

It doesn't seem to do this on linux so I guess there is something
different how we have to close a udp socket on freebsd?
Any idea how to debug this? Anybody else seeing this?

Kind regards,
Marius
___
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: pdnsd leaking udp sockets

[Marius Nünnerich]

Hi Ashish,

On Tue, Feb 15, 2011 at 10:23, Ashish SHUKLA  wrote:
> Hi Marius,
>
> Marius Nünnerich writes:
>> Hi Ashish, all,
>
>> I'm currently using pdnsd as a local dns cache. It seems to leak udp
>> sockets. After an uptime of about 7 days it looks like this:
>
>> % sockstat -46 | grep pdnsd
>> nobody   pdnsd      19655 3  tcp4   127.0.0.1:53          *:*
>> nobody   pdnsd      19655 4  udp4   127.0.0.1:53          *:*
>> nobody   pdnsd      19655 6  udp4   *:*                   *:*
>> nobody   pdnsd      19655 7  udp4   *:*                   *:*
>> [...]
>> nobody   pdnsd      19655 140 udp4  *:*                   *:*
>> nobody   pdnsd      19655 141 udp4  *:*                   *:*
>> nobody   pdnsd      19655 142 udp4  *:*                   *:*
>> %
>
>> It doesn't seem to do this on linux so I guess there is something
>> different how we have to close a udp socket on freebsd?
>> Any idea how to debug this? Anybody else seeing this?
>
> Thanks for reporting this. ATM, I'm not sure how to debug this, I've to look
> at its code base. Any details about the version of FreeBSD you're using,
> related log messages (from dmesg or /var/log/messages) are welcome.

dmesg and messages are clean. My FreeBSD ist 8.0-RELEASE/amd64.
I took a look at the code too but couldn't see anything suspicious. I
don't have time right now but one idea would be to add some dtrace
probes to the source.

>
> I'll get back to you soon with my findings.
>
> Thanks
> --
> Ashish SHUKLA
>
> “I think I can safely say that nobody understands quantum mechanics.”
> (Richard Feynman, 1965)
>
___
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: pdnsd leaking udp sockets

[Marius Nünnerich]

On Tue, Feb 15, 2011 at 12:56, Ashish SHUKLA  wrote:
> Marius Nünnerich writes:
>> Hi Ashish,
>
> [...]
>
>> dmesg and messages are clean. My FreeBSD ist 8.0-RELEASE/amd64.
>> I took a look at the code too but couldn't see anything suspicious. I
>> don't have time right now but one idea would be to add some dtrace
>> probes to the source.
>
> I looked at the source code, and found a place where it's leaking socket
> descriptors, but I'm not sure if this is the major source of impact. I fixed
> that. You can test the diff[1] to see if it fixes issue you're experiencing.
>
> To reproduce this at my end, I switched to 'resolv.conf' server method and
> commented 'server_ip' in the pdnsd.conf(5). Following are the contents of the
> resolv.conf(5):
>
> #v+
> chateau.d.if!abbe:~ % cat /etc/resolv.conf
> nameserver 127.0.0.1
> nameserver 4.2.2.2
> #v-
>
> Before applying the diff, it is leaking following socket descriptor:
>
> #v+
> chateau.d.if!abbe:~ % sockstat -64  |fgrep pdns
> nobody   pdnsd      38434 3  tcp4   *:53                  *:*
> nobody   pdnsd      38434 4  udp4   *:*                   *:*
> nobody   pdnsd      38434 5  udp4   *:53                  *:*
> #v-
>
> And with the diff applied:
>
> #v+
> chateau.d.if!abbe:~ % sockstat -64  |fgrep pdns
> nobody   pdnsd      43666 3  tcp4   *:53                  *:*
> nobody   pdnsd      43666 4  udp4   *:53                  *:*
> #v-
>
> References:
> [1]  http://people.freebsd.org/~ashish/diffs/pdnsd-sockets-leak.diff

Ok, I applied the patch and reinstalled the port. I will leave it
running for a few days and report back. So far it's looking good.
Thank you very much! :)
___
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: pdnsd leaking udp sockets

[Marius Nünnerich]

On Sun, Feb 20, 2011 at 21:34, Ashish SHUKLA  wrote:
> Hi Marius,
>
> Marius Nünnerich writes:
>
> [...]
>
>> Ok, I applied the patch and reinstalled the port. I will leave it
>> running for a few days and report back. So far it's looking good.
>> Thank you very much! :)
>

OK, I had it running for a while now with your fix. It's not leaking anymore.
There is still one close() missing before a return in that same function.

> I talked to Paul (the upstream author of pdnsd), and he suggested running
> dns/pdnsd with following command-line (requires devel/valgrind port):
>
> % valgrind --tool=memcheck --leak-check=yes --track-fds==yes pdnsd --nodaemon

I'll try this too if I can find the time, but so far it doesn't seem
to leak memory.
___
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: New portmgr secretary: Thomas Abthorpe

[Marius Nünnerich]

On Thu, Mar 18, 2010 at 17:35, FreeBSD portmgr secretary
 wrote:
> On Thu, 18 Mar 2010 13:26:14 -0300
> Renato Botelho  wrote:
>
>> Congratulations Thomas and Thanks Erwin for all the work in last years.
>
> Thanks Renato!
>
> Next year at BSDCan, I will invoke my new found hat and you can buy the first
> round :)
>
> Likewise I too would like to express my thanks to Erwin for his time as
> -secretary, he will be my "mentor" as I get the feel for my new job!

Thank you both very much! :)
___
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: audio/mumble needs devel/protobuf as lib depend.

[Marius Nünnerich]

On Wed, May 5, 2010 at 20:04, Demelier David  wrote:
> The problem was an other missing dependency : databases/qt4-sql-sqlite3 so the
> fix would be to add sql-sqlite4 to in QT_COMPONENTS too.

Thanks for your patch and investigation. Do you know which component
uses sqlite3? I didn't see mumble using it directly.
___
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: GPLv3-licensed ports

[Marius Nünnerich]

On Wed, May 19, 2010 at 00:41, Charlie Kester  wrote:
> Will someone with edit privileges for the wiki please add the following to
> the
> list of GPLv3-licensed ports (http://wiki.freebsd.org/PortsAndGPLv3)?
>
>        math/ised       misc/xsw        sysutils/rdup

Done, thanks for reporting.
___
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: Call for potential ports maintainers

[Marius Nünnerich]

On Thu, Feb 12, 2009 at 6:32 PM, Thomas Abthorpe  wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> This topic came up in IRC, and I was encouraged to go out, and find some new
> maintainers.
>
> At any given time, approximately 20 - 25% of all ports are unmaintained. Not
> all unmaintained ports need updating, but some do. That is where you folks
> come in.
>
> There are a bunch of you out there who are subscribers to this list (and other
> FreeBSD related lists too, I am sure), you have FreeBSD installed and likely
> have quite an array of ports installed on this system of yours. You are
> subscribed as a means of keeping up with the world of FreeBSD.
>
> But you have been holding back, thinking "I really would like to do something
> to contribute to the success of FreeBSD, but I am not sure what."
>
> How do I know this? I was one, a silent observer on the mailing lists, and in
> on IRC. Then one day, I answered a similar plea,
> http://lists.freebsd.org/pipermail/freebsd-announce/2006-May/001065.html.
>
> I have summarised some details on the wiki on Adopting Ports,
> http://wiki.freebsd.org/PortsTasks#head-f018f566bce2ff96ec13fabd536d7cc6dc6f4275.
>
> The gauntlet has been thrown down, who among you is prepared to pick it up?

Ok, I'll take www/libwww, x11/xlockmore, graphics/libexif and
graphics/libexif-gtk. None of those needs updating right now so could
you simply put my name in as the maintainer?

Thanks for _your_ contribution to FreeBSD :)

 - Marius
___
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: Wine and CURRENT

[Marius Nünnerich]

On Mon, Mar 9, 2009 at 09:51, Guy Brand  wrote:
> Hello,
>
>
> Am I the only one unable to start wine on CURRENT?
>
>  bug ~# wine progman
>  Assertion failed: (heap_base != (void *)-1), function virtual_init,
>  file virtual.c, line 1314.
>  [1]    2797 abort (core dumped)  wine progman
>
> It's been that way for a few months now and it's still the same with
> wine-1.1.15 port.

I do not run wine on current but I think I saw this error when I
increased KVA_PAGES on 7-stable. Did you do that? What architecture
are you using?
___
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: audio/teamspeak_client ARCH -amd64 ONLY_FOR_ARCHS= i386

[Marius Nünnerich]

On Thu, Apr 16, 2009 at 08:19, Joseph King  wrote:
> After trying for about 12 hours straight I gave up trying to get this client
> working on the amd64 arch. As far as I can tell it is only for i386.
>
> I downgraded from amd64 to i386 because of this.
>
> Figured you might want to remove the amd64 from the ONLY_FOR_ARCHS=
>
> This might also be the case with the audio/teamspeak_server.

This won't help you with teamspeak but maybe you can use audio/mumble.
It is open source.
___
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: [Call For Testing] VirtualBox for FreeBSD! take2

[Marius Nünnerich]

On Sun, May 17, 2009 at 20:09, Martin Wilke  wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> We rolled a new tarball with the patch from Juergen Lock [1]
> with a posible fix for AMD64 users, tested on 3 machines
> which now works without problems. Many Thanks to him for
> his nice work!
>
> http://people.freebsd.org/~miwi/vbox/virtualbox_2.tgz
>
> Martin

I'm impressed, everything I tried worked ootb. Thank you all!

(FreeBSD/i386 7.2-STABLE)
___
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: Dropping maintainership for sysutils/zfs-snapshot-mgmt

[Marius Nünnerich]

2009/7/28 Marcin Simonides :
> Hello,
>
> I am the maintainer and author of zfs-snaphot-mgmt port - a crude (and a bit
> buggy) script for automatic snapshot creation and removal on ZFS.
> Since I am no longer using FreeBSD I cannot keep neither the port nor the
> script itself up-to-date.
>
> If someone, preferably one of the users, would like to take over the script
> and/or the port please contact me off the list.
> --
> Marcin Simonides

I'll take it. Thanks for your good work so far! I'm using it hourly ;)
___
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: xlockmore-5.29: "BadWindow (invalid Window parameter)" using virtual wm

[Marius Nünnerich]

Hi David,

On Sun, Oct 11, 2009 at 20:54, David Wolfskill  wrote:
> This is running FreeBSD 6.4-STABLE r197725; I'm in the habit of
> updating installed ports on my laptop daily (after updating the
> stable/6 slice).
>
> The xlockmore port is at 5.29, updating 01 Oct 2009.
>
> I normally use the piewm Window Manager (I got used to tvtwm back in
> '93, and piewm is based on it and is very similar).
>
> If I try to issue "xlock -mode random" using either piewm or tvtwm, I
> now get:
>
> X Error of failed request:  BadWindow (invalid Window parameter)
>  Major opcode of failed request:  3 (X_GetWindowAttributes)
>  Resource id in failed request:  0x45
>  Serial number of failed request:  82
>  Current serial number in output stream:  83
>
> If I exit either of those Window Managers and fire up twm, xlock does
> not issue that message, and seems to run normally (at least in most
> modes).
>
> I believe that this change in behavior coincided with the update to
> xlockmore (01 Oct); I didn't mention it earlier because something odd
> also appears to have happened with DRI support recently, and I wasn't
> clear enough on the interrelationships to be reasonably confident that I
> was reporting things properly.
>
> I also run stable/7 and head slices (each with the misc/compat6x port
> installed, so I'm using a shared /usr/local among all slices).
> xlockmore appears to run OK in 7.2-STABLE r197901 and head r197928,
> though I'm unable to run X with DRI enabled in those environments.
>
> In checking the Net for other reports of similarissues, I see that
> xlockmore has had issues in the past with virtual window managers (ref.
> , from Thu, 19
> May 2005 11:18:03 UTC).
>
> Would it make more sense (for getting the issue resolved) for me to try
> reverting xlockmore to the previous version or some other approach?
> While I'm OK hacking code, I certainly don't claim much in-depth
> understanding of much X-related code; on the other hand, I do have local
> mirrors of the FreeBSD CVS & SVN repositories handy.
>
> Thanks!
>
> Peace,
> david
> --
> David H. Wolfskill                              da...@catwhisker.org
> Depriving a girl or boy of an opportunity for education is evil.
>
> See http://www.catwhisker.org/~david/publickey.gpg for my public key.
>

Could you please write to David A. Bagley  and
explain this problem to him? He is the current maintainer of
xlockmore.
___
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: compile a port with debugging symbols?

[Marius Nünnerich]

On Sat, Nov 28, 2009 at 15:07, Michael W. Lucas
 wrote:
> On Thu, Nov 26, 2009 at 07:12:43PM +0200, Andrew W. Nosenko wrote:
>> On Thu, Nov 26, 2009 at 18:10, Michael W. Lucas
>>  wrote:
>> > Hi,
>> >
>> > Is there an approved/offical way to compile a port with debugging
>> > symbols?
>> >
>> > Habitually I've just run "make configure" and then edited Makefiles.
>> > But I'm sure that's not what you folks recommend users do...
>>
>> IIRC, the
>>   WITH_DEBUG=yes
>> knob is what you looking for.
>
> Hi,
>
> WITH_DEBUG builds with -g, but strips net-mgmt/flowd upon install.
> Haven't tried others.
>
> I can run and debug the binary in the port working directory, however.
>

# make WITH_DEBUG=yes STRIP= install
___
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: [HEADS UP] Experimental 3D HW accel support for Radeon HD 2xxx, 3xxx and 4xxx.

[Marius Nünnerich]

On Sun, Dec 6, 2009 at 15:03, Robert Noland  wrote:
> On Sat, 2009-12-05 at 10:01 +0200, Alex Kozlov wrote:
>> On Sat, Dec 05, 2009 at 10:42:43AM +0900, Norikatsu Shigemura wrote:
>> > Hi Radeon HD 2xxx, 3xxx and 4xxx users!
>> >
>> >     I'm ready to update ports related Mesa3D to 7.6 base, graphics/dri,
>> >     graphics/libGL*, graphics/libglut, graphics/mesa-demos and
>> >     graphics/libdrm.  Please see also my attached patch file.  I'll
>> >     update these as soon as tomorrow.
>> >
>> >     Mesa3D 7.6 supports experimental r600 driver, as known as AMD
>> >     R6xx/R7xx architecture.  I confirmed that it's good works, but
>> >     buggy on my Radeon HD 4850 environment with 9-current/amd64 and
>> >     xf86-video-radeonhd-devel.  Please see also [I known problem]
>> >     section.
>> I use similiar setup(but with mesa git master) for more than a month
>> without a problem. HD 3650 AGP. glxgear, other demos and even some old
>> games in wine like deusex work fine.
>
> Openarena, UT, vdrift, nexuiz, etc... should all work fairly well also.
> There are still features that are not yet implemented on r600, but I
> tend to run all of the above all video options enabled on highest
> settings.  Really large textures are slow and it seems like I found one
> option that really hurt performance (bloom maybe), but otherwise they
> are all more than playable on my HD4650 core2duo e7400.
>
> Disclaimer: I'm not a gamer... but I do use them for testing.
>
> robert.

One thing I know is interesting for many people is playing World of
Warcraft under wine. Last time I checked it wasn't even possible under
linux with catalyst. Do you know anything about this or have tried it?
___
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: nvidia-driver 64bit version

[Marius Nünnerich]

On Fri, Dec 4, 2009 at 19:56, Sam Fourman Jr.  wrote:
> On Fri, Dec 4, 2009 at 10:20 AM, Robert Noland  wrote:
>> On Fri, 2009-12-04 at 15:18 +, Alexey Dokuchaev wrote:
>>> On Fri, Dec 04, 2009 at 03:47:24PM +0100, Emanuel Haupt wrote:
>>> > Hi
>>> >
>>> > I was wondering if you're working on a port for the 64bit version of
>>> > the new beta state nvidia driver [1].
>>>
>>> Yup, thanks for the pointer.  I'm considering options right now.
>>>
>>> >
>>> > Since it's a completely different version it should IMO be separate from
>>> > x11/nvidia-driver. Maybe x11/nvidia-driver-amd64 and x11/nvidia-driver
>>> > could be renamed to x11/nvidia-driver-i386.
>>>
>>> This would be the easiest route, but I'm not sure this is the best thing
>>> to do.  From user's perspective, one should be able to "cd
>>> category/port" and "make install".  The rest (including taking care of
>>> architecture-dependent things) should be handled by underlying
>>> infrastructure.  Right now I believe our bpm is capable of the task, and
>>> my pmake/bpm-fu is strong enough, we'll see.
>>
>> I've never actually used the blob, but is the new driver only amd64?  I
>> presume that it does need at least 8.0-RELEASE to work, but I can't
>
> it also works with RELENG_7 (but not 7.2R)
> as a side note, I installed wine in a 32bit chroot and installed the
> 32bit version of the new nvidia driver
> and I can Play World of Warcraft without any issues, so I guess it
> works Just like linux does.

OK, I try to do the same, except on 8.0-RELEASE. How did you do that?
I followed 
http://wiki.freebsd.org/Wine#head-6963d527c173e57b1567e881305b544d33435b6d
but whenever I execute
% wine32
ELF interpreter /libexec/ld-elf.so.1 not found
zsh: abort  LD_32_LIBRARY_PATH=/compat/i386/usr/local/lib PATH=

% alias wine32
wine32='LD_32_LIBRARY_PATH=/compat/i386/usr/local/lib
PATH=/compat/i386/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/home/marius/bin:/usr/local/kde4/bin
/compat/i386/usr/local/bin/wine'


btw. glxgears works not chrooted.
___
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: nvidia-driver 64bit version

[Marius Nünnerich]

On Mon, Dec 7, 2009 at 19:55, Marius Nünnerich  wrote:
> On Fri, Dec 4, 2009 at 19:56, Sam Fourman Jr.  wrote:
>> On Fri, Dec 4, 2009 at 10:20 AM, Robert Noland  wrote:
>>> On Fri, 2009-12-04 at 15:18 +, Alexey Dokuchaev wrote:
>>>> On Fri, Dec 04, 2009 at 03:47:24PM +0100, Emanuel Haupt wrote:
>>>> > Hi
>>>> >
>>>> > I was wondering if you're working on a port for the 64bit version of
>>>> > the new beta state nvidia driver [1].
>>>>
>>>> Yup, thanks for the pointer.  I'm considering options right now.
>>>>
>>>> >
>>>> > Since it's a completely different version it should IMO be separate from
>>>> > x11/nvidia-driver. Maybe x11/nvidia-driver-amd64 and x11/nvidia-driver
>>>> > could be renamed to x11/nvidia-driver-i386.
>>>>
>>>> This would be the easiest route, but I'm not sure this is the best thing
>>>> to do.  From user's perspective, one should be able to "cd
>>>> category/port" and "make install".  The rest (including taking care of
>>>> architecture-dependent things) should be handled by underlying
>>>> infrastructure.  Right now I believe our bpm is capable of the task, and
>>>> my pmake/bpm-fu is strong enough, we'll see.
>>>
>>> I've never actually used the blob, but is the new driver only amd64?  I
>>> presume that it does need at least 8.0-RELEASE to work, but I can't
>>
>> it also works with RELENG_7 (but not 7.2R)
>> as a side note, I installed wine in a 32bit chroot and installed the
>> 32bit version of the new nvidia driver
>> and I can Play World of Warcraft without any issues, so I guess it
>> works Just like linux does.
>
> OK, I try to do the same, except on 8.0-RELEASE. How did you do that?
> I followed 
> http://wiki.freebsd.org/Wine#head-6963d527c173e57b1567e881305b544d33435b6d
> but whenever I execute
> % wine32
> ELF interpreter /libexec/ld-elf.so.1 not found
> zsh: abort      LD_32_LIBRARY_PATH=/compat/i386/usr/local/lib PATH=
>
> % alias wine32
> wine32='LD_32_LIBRARY_PATH=/compat/i386/usr/local/lib
> PATH=/compat/i386/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/home/marius/bin:/usr/local/kde4/bin
> /compat/i386/usr/local/bin/wine'
>
>
> btw. glxgears works not chrooted.
>

OK, wine is working. I did a minimal install so lib32 was missing. I
installed nvidia-driver 32bit into the chroot and now World of
Warcraft is working! 32bit glxgears is working too.
___
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: memcached-1.4.1

[Marius Nünnerich]

On Wed, Dec 9, 2009 at 21:49, David P. Discher  wrote:
>
> erwin/mnag -
>
> $FreeBSD: ports/databases/memcached/Makefile,v 1.36 2009/11/08 19:42:13 erwin 
> Exp $
>
> is marked as "broken" on 8.x on Nov 8th because it won't link.  However,  
> just linked and tested memcached, on 8-stable (amd64) from about Dec 1st, svn 
> r200012.  Works fine for me.
>
> It's unclear to me if there ever was a valid linking problem.  Can one of 
> your verify this, and remove the broken tag ?
>
> Thanks !

I just built, installed and ran memcached on 8.0-RELEASE/amd64 with
-DTRYBROKEN, worked fine.
___
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"

Help update audio/mumble to 1.2.0

[Marius Nünnerich]

Hi all,

I could use some help updating audio/mumble to version 1.2.0. The
current 1.1.8 worked for a while but after upgrading some other ports
(Qt related I guess) others can't here me anymore. Upgrading the port
to 1.2.0 doesn't help with this problem. I can't even hear others with
this version. With the following patch it builds, installs and
deinstalls fine.
http://nuenneri.ch/freebsd/mumble-1.2.0.patch

Anyone has an idea what to try? Anyone can test this against the
8.0-RELEASE set of the ports?
Thanks
Marius
___
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"